I hereby claim:
- I am neo1908 on github.
- I am neo1911 (https://keybase.io/neo1911) on keybase.
- I have a public key whose fingerprint is 4266 38DB 7952 1C61 2EE2 68B7 AD95 0A08 7310 D01C
I hereby claim:
BEGIN MESSAGE. | |
RqU8I9DzFfGl3Bd 8G8rwJqZCf7Dzv8 kRgQzc37c21ENZF zfXbJz9N7XvyoqH | |
ETRSa4fAY5E3ix3 Kz52Fw2Twl4TCKq 6Xr2MZHgg77QYZH gzRA51LPJOs86yr | |
RLBTVnfaHOX7RgS a7yCyo4AwozpWeL RiUBamOUb1W6AH8 ZJyYxIIOIPums52 | |
XOSENEUBffENckJ TeIAlR1mHNIxSwz oeF9u2IP. | |
END MESSAGE. |
Here are some thoughts and ideas on how I have lets encrypt certificates deployed to home infrastructure ...
At a high level , my setup assigns a hostname based subdomain for each internal host.
E.G. If my registered domain is example.com
and my host is host1
then I will generate a cert for host1.example.com
.
Let's encrypt supports wildcards, you could use a wildcard if you wanted to. I didn't like the idea of every internal host using the same keypair.
This page serves as a dumping ground for ideas on preserving access to online ( and offline ) accounts in the event of disaster