The idea is that the page can be used as a general overview of topics relating to relay security. As it stands it only features the valuable information that was extracted from the pages that this ticket notes, though I imagine there are likely things located in the wiki / the main doc which might find a suitable home there.
I understand it can quickly become a mess if it goes into OS specifics for every suggestion added, and things like the iptables config are already located elsewhere on the wiki. If there's another way you'd like to see it done I'm open to suggestions.
lets limit the scope to tor in relay mode only (tor clients or tor onion services are not covered) - this is somewhat obvious since the page lifes under /TorRelayGuide
title "Tor Relay Security Best Practices"
have a (small) generic/high level section that applies to all platforms (because we can not cover every possible OS)
this section will not include step-by-step instructions since it is OS independent
the physical security section
OS (hardware vs. virtual, OS level access authentication, pointer to auto-updates)
have a (bigger) section for tor
primarily focuses on the tor daemon itself and its security relevant settings and recommendations
convey the order in which different options are preferred (example: bare metal installations are considered better than VPS installation)
consider the current installation steps as a baseline and tell people what they could do on top of that if they want to do better than that
include no-go's
avoid conflicting statements regarding disk encryption
maybe have something like levels
basic (default install as described per the guide + auto updates)
intermediate
high (runs on hardware, 2FA, offline master keys with signing key lifetime < 30day)
lets remove the following sections:
"Tor-only firewalling with iptables" (because we cover it generically for all platforms in the generic section)
Coldboot attacks (due to new offline master key section that mitigates this attack vector)
Replace section "Restricting SSH access" with a recommendation to use strong authentication (part of the generic section)
Noted! Thank you lots for taking the time to give such a thorough review. I will work on these revisions first thing when I'm at my desk tomorrow, will let you know when it is ready for another look