Selfhosted

61333 readers

557 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

111

What's the real danger of opening ports? (feddit.it)

submitted 10 months ago by dontblink@feddit.it to c/selfhosted@lemmy.world

65 comments fedilink hide all child comments

Some services run really good behind a reverse proxy on 443, but some others can really become an hassle.. And sometimes just opening other ports would be easier than to try configuring everything to work through 443.

An example that comes to my mind is SSH, yeah you can use SSLH to forward requests coming from 443 to 22, but it's so much easier to just leave 22 open..

Now, for SSH, if you have certificate authentication or a strong password, I think you can feel quite safe, but what about other random ports? What risks I'm exposing my server to if I open some of them when needed for a service? Is the effort of trying to pass everything through 443/80 worth it?

you are viewing a single comment's thread
view the rest of the comments

[–] JackbyDev@programming.dev 5 points 10 months ago (1 children)

I think people get too defensive about security by obscurity not being security. It's still better for things to be obscure, it's just not sufficient. A hidden lock to open a door is marginally better than a lock on the door. A hidden button to open a door isn't secure though, of course.

But at the same time, I fully understand why it's stressed so much. People tend to make analogies in their mind to the physical world. The digital world is so different though. An example I use often is you can't jiggle every doorknob in the world to see if it's unlocked, but it's (relatively) easy to check every IPv4 address for an open port to some database with default credentials.

[–] 4am@lemmy.zip 3 points 10 months ago

Security through obscurity is hammered into newbies as being bad because it’s often a “quicker and easier” solution and we don’t want anyone thinking they could just do that and be done with it.

You have to learn the proper way to do it; obscurity only buys you time. Maybe.