this post was submitted on 22 Nov 2023
6 points (100.0% liked)

Self-Hosted Main

504 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
6
What service one should NOT self host (alien.top)
submitted 11 months ago by SuperWill5633@alien.top to c/main@selfhosted.forum
116 comments fedilink hide all child comments
 

Like the title says, I'm new to self hosting world. πŸ˜€ while I was researching, I found out that many people dissuaded me to self host email server. Just too complicated and hard to manage. What other services that you think we should just go use the currently available providers in the market and why? πŸ™‚thank you

you are viewing a single comment's thread
view the rest of the comments
[–] KN4MKB@alien.top 1 points 11 months ago (1 children)

I'll leave with this. ANY service exposed publicly or not should not have vulnerabilities. If there is any hint that your NAS webserver has vulnerabilities, it shouldn't even be used internally. So to me, it does not matter. I don't expose my NAS webserver because I have no reason to increase my attack surface that wide.

But I'm comfortable exposing any of my internal services as needed because I've personally checked the source code for vulnerabilities, and have proper checks in place on top of regular security updates. I understand why others wouldn't think the same way, as this takes a high level of confidence in your ability to assess the security posture of your systems and network. I've had penetration tests in my network, conduct them myself for business.

[–] Accomplished-Lack721@alien.top 1 points 11 months ago

It would be nice if we, and apps' developers, always knew what the vulnerabilities are. They generally exist because the developer doesn't know about them yet, or hasn't found a solution yet (though ideally has been transparent about that). Zero-day exploits happen. There's always a first person or group discovering a flaw.

If being up to date and using SSL was all it took, security would be a lot simpler.

No one security measure is ever foolproof, other than taking everything offline. But multiple used in tandem make it somewhere between inconveniently and impractically difficult to breach a system.