2.5 years ago, I migrated all my services hosted on a cloud provider to a homeserver.
This homeserver is also my workstation/gaming/dev/everything. I use QubesOS (an operating system based on the Xen hypervisor), and wrote some document about it: https://neowutran.ovh/qubes/articles/homeserver.pdf
Basically, I am hosting:
- DNS
- Matrix
- Jitsi
- Mumble
- Peertube
- Screego
- Nextcloud
- Searxng
- Tor
- Wireguard VPN
- Copy of wikipedia
- Personal website And others.
And for TLS, to have better security, and to avoid relying on third party company/providers, I am using DANE.
https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities
https://sr.ht/~yukikoo/dane_without_root/
https://github.com/buffrr/letsdane
The “dane_without_root” is one of my projects and I am welcoming review / feedback on it
( I also posted about it on the QubesOS forum: https://forum.qubes-os.org/t/highlighting-neowutrans-technical-doc-about-qubes )
Hi, the sourcehut seems to be pretty interesting. If I understand it correctly, this DANE-without-root provides a TOFU model as an alternative to the normal case of verifying up all the parts of the domain levels, right? If feasible, maybe that could be nice to extend with other methods for OOB verification and key rollover
Indeed. (This part is not in any RFC or DANE standard, it is my idea to improve the system further). If you want to check the current implementation, you can search for ‘tofu’ string in this file: https://git.sr.ht/~yukikoo/dane_without_root/tree/master/item/src/core/dane.rs
This is a case that I didn’t cover, good idea. Probably something like ‘if successfully validated with tofu, then add all the valid dnskey to the valid tofu key list and remove the old ones’. It would still be problematic if a user doesn’t connect for a very long time to a website with tofu support and miss the key rollover, but that still a good improvement over the current tofu implementation. Will do that later.
Something more specific in mind?