You Should Run a Certificate Transparency Log
You Should Run a Certificate Transparency Log
Maybe you, yes you, should run a Certificate Transparency log. It’s cheaper, easier, and more important than ever.
You're viewing a single thread.
Servers: one. No need to make the log a distributed system, CT itself is a distributed system.
The uptime target is 99%3 over three months, which allows for nearly 22h of downtime. That’s more than three motherboard failures per month.
CPU and memory: whatever, as long as it’s ECC memory. Four cores and 2 GB will do.
Bandwidth: 2 – 3 Gbps outbound.
Storage:
3 – 5 TB of usable redundant filesystem space on SSD or.
3 – 5 TB of S3-compatible object storage, and 200 GB of cache on SSD.
People: at least two. The Google policy requires two contacts, and generally who wants to carry a pager alone.Seems beyond you typical homelab self hoster, except for the countries that have 5gbps symmetric home broadband.
If anyone can sneak 2-3gbps outbound pass their employer, I imagine the rest is trivial.
Altho... "At least 2 [people]" isn't the typical self hostingEdit:
Tried to fix the copy/paste.Also will add:
https://crt.sh/
Has a list of all certificates issued.
If you are using LE for every subdomain of your homelab (including internal), maybe think about a wildcard cert?
One of those "obscurity isn't security", but why advertise your endpoints? Also increases privacy (IE not advertising porn(dot)example(dot)com)2-3Gbps? Mate, I can only get 40Mbps here. I would kill for that bandwidth!
Thats what I'm on currently, and soon I'll be able to get 1.2gbit symmetric!
Still a far cry from 2-3gbps. I dont know of anyone with home internet service capable of that, but maybe elsewhere there are better options.
In the UK, cityfiber is rolling out 2.3gbps. just not in my area
I live in an area with Google Fiber. I’m on their standard gigabit plan, but apparently 3 and 8 gigabit is available for my address - all speeds symmetrical. Really should be the standard for what’s available across the US, but we wouldn’t want to offend upstanding companies like Comcast, ATT, Verizon, etc.
Thats the problem....
Right now I'm not even served by one of the big companies, and they haven't improved service in.... Years.
Even their fiber lines max at 500 symmetric, and they won't drop to a residence. No other options either.
Comcast is now in the area, and as much as I hate them.... It would be cheaper and faster by a lot (on both counts). Half the price, 25 times the upstream.
Its a sad state of affairs IMO.
Yup...
Uptime is fine, CPU/men is fine. I'd even be fine with grabbing a few ssd's for the task...
But 2-3gbps is a non-starter, not to mention 2 contacts.
But your endpoints are already available to everyone with just a nslookup.
Maybe it's more the permanent history of that, so if you run something like "radarr.example.com" then you wouldn't have plausible deniability if you're sued and the CT logs are presented as proof of your wrongdoing
Not if you use wildcard dns records.
With Encrypted Client Hello you can have some more privacy on obtaining certificates for wildcard domains, IIRC.
Not if you run a wildcard CNAME for your sub domains right ?
Like I have *.mydomain.com point to my server, and there I have a different reverse proxy depending on the domain.
I mean, the very first few lines make it pretty clear he’s not writing for the typical homelab self hoster:
If you are an organization with some spare storage and bandwidth, or an engineer looking to justify an overprovisioned homelab, you should consider running a Certificate Transparency log.