💾 Archived View for nicholasjohnson.ch › 2024 › 07 › 04 › journal-update-27 › index.gmi captured on 2024-07-09 at 00:18:00. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
_ _ _ _ _ _ _ | \| (_)__| |_ ___| |__ _ ___ _ | |___| |_ _ _ ___ ___ _ _ | .` | / _| ' \/ _ \ / _` (_-< | || / _ \ ' \| ' \(_-</ _ \ ' \ |_|\_|_\__|_||_\___/_\__,_/__/ \__/\___/_||_|_||_/__/\___/_||_|
📆 July 4, 2024 | ⏱️ 2 minute read | 🏷️ journal updates
This entry does not constitute a return to writing. I'm still taking a step back¹ from writing. I'm only writing this entry because I have to make an important announcement.
If you don't want to read this whole entry, just read the important announcement in the first bullet point of the subheading below.
The new I2P destination private keys are kept offline while the online keys are rotated at regular intervals. This provides compromise recovery. I.e: If my server is hacked and the online keys are stolen, the attacker can only control the I2P destination until the keys expire, and I just keep rotating in new online keys according to schedule as if nothing happened.
Tor doesn't yet support offline keys, so if the server is compromised I'll have to generate a new onion. The good news is there are plans to support offline v3 onion service keys³ in Arti⁴, a project to implement Tor in Rust. As soon as that's implemented, I'll move my onion key offline as well.
🔗 [1]: Journal Update 26: Taking a Step Back
🔗 [3]: prop224: Implement offline keys for v3 onion services
🔗 [5]: Hugo Journal Theme Changelog
Copyright © 2020-2024 Nicholas Johnson. CC BY-SA 4.0.