Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
view the rest of the comments
True. I would like to add another authentication.
I guess my question is how trustworthy is built-in authentication? I'm not really talking about vulnerabilities, but that's a part of this, but how much trust can I put into a small projects login page being secure?
That's really up to the software again. If you're not technically inclined enough to run through the code, that's fine, but you have to trust that other people are.
Go and search GitHub issues or this project by name for what you're concerned about.
Authentication is also not security, btw. It's just access. If you can be more specific about your concerns in your post, you may get more direct answers.
"authentication is not security," can you elaborate on that?
Your statement doesn't really overlap with my understanding of security, as "just access" seems critically relevant to how secure user data is, for example. Am I missing something?
Authentication is simply identifying a user.
Authorization is securing access to assets.
You can find a lot of reading about this if the distinction is confusing.
Right, thanks.
None. Dashy's authentication was famously literally security theatre even with Keycloak. You could just pause the load in browser and have full access to the config. Because it let you iframe whatever you could now do so with local services to enum. Somehow Jellyfin is unbustable though. So it's a bit of a crapshoot. Look at past vulnerabilities. Stuff like XSS unless stored you don't need to worry about, clickjacking, tab nabbing etc. On the other hand anything that's arbitrary file read, SQLI, RCE, LFI, RFI, SSRF etc. I would look at seriously. E.g. don't make your 13ft public because it can be used to literally enumerate your entire private network.
I'd like to do the same, but atm I use nginx to serve all the web interfaces... And keycloak support is either a plus subscription feature or made to work with hacky Lua scripts.
So for now it's security through obscurity, I got a wildcard cert and the pages are accessed based on subdomain. So afaik nobody has a clue unless they start iterating common subdomain names. (At some point™️ I'm adding proper auth though)
I'm not sure how much you can trust them, but you might want to have a look at Authelia