this post was submitted on 20 Apr 2024
137 points (98.6% liked)

Selfhosted

40296 readers
213 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
(page 2) 16 comments
sorted by: hot top controversial new old
[–] AnonymousLemming@feddit.de 1 points 5 months ago

Use a hardened-by-default OS like OpenBSD, HardenedBSD, or something similar in Linux.

[–] Lemongrab@lemmy.one 0 points 7 months ago
[–] slazer2au@lemmy.world -4 points 7 months ago (19 children)

Move services away from known ports and don't use ports that end with well known port numbers (22,80,443).

Moving ssh from 22 to 2222 or 443 to 10443 does nothing. You have ~65000 ports. Pick something random like 6744 or 2458

[–] JustEnoughDucks@feddit.nl 0 points 7 months ago

Just don't port forward ssh. There is 0 reason to in 99.99% of home cases

load more comments (18 replies)
load more comments
view more: ‹ prev next ›