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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Hi everyone
I posted before here. I'll try once more but don't want to get over bearing.
I'm trying to self host all my contacts and my calendar.
I've managed to install radicale but there very little ui and I'm not actually sure how to import my contacts and calendar, or how to start using it with a client.
This is all I see
I've set up the calendar and contacts server but I can't find any security settings to password protect it
Any guidance would be awesome, thank you
The options to password protect it are in the (usually
/etc/radicale/)configfile under[auth].For proper security you could use
type = htpasswdhtpasswd_filename = /etc/radicale/usershtpasswd_encryption = bcryptthen create a users file with apache tools (
htpasswd -c -B users User1) or one of the million online htpasswd file creators.Please note that to use "bcrypt" for
htpasswd_encryptionyou need the bcrypt python module installed. Some distributions of radicale (eg. some docker images) don't have it.It's fairly safe to set it to "md5" instead. It does not mean plain MD5 (one iteration), it does several hundred rounds of MD5 plus a salt.
For the curious, the advantage of bcrypt over a single-iteration, fast hash like MD5 is that bcrypt lets you set the hashing effort, while MD5's goal is to do it as fast as possible.
This becomes relevant when someone steals your password file and tries to brute force it by hashing a bunch of dictionary words and random strings (plus a bunch of salts) until something matches. A fast single-iteration hash like MD5 will let them do that much faster than a bcrypt hash set to a higher effort; it can mean the difference between finding a password in one week vs finding one in 100 years. That's what the hundreds-of-iterations MD5 is trying to achieve, it's a "poor man's bcrypt".
Don't generate password files online,...
... because? ... or, instead, do...?
Because if I wanted to harvest a bunch of passwords I would offer a online password generator.
Do use apache utils locally.
While you are right in general, you are just creating a file with a : line without any identifying context. So have fun searching the world for where I might have actually used it. Sounds like a really bad use of ressources to create list of passwords.
PS: Yes, as an Arch user I am still pissed that this tool is not available in the repos beside installing the complete Apache server...
Your browser also sends all kinds of fingerprintable information.
The password is also hashed....