Not every user will have a hardware token. This adds instructions
for setting up multi-factor with TOTP. This was inspired / based on
work by @kennethrrosen [1].
Everything about the YubiKey guide is kept but moved to a lower
heading level to acommodate for the two MFA options: YubiKey or TOTP.
[1]: https://forum.qubes-os.org/t/otp-for-xscreensaver-guide/23988
Add cmd option to command alternative of standalone creation to reflect better the "alternative" part of the GUI version given its option msg "Standalone qube copied from a template".
Whonix 16 will reach EOL before Qubes 4.1 reaches EOL, at which point
the table will be inaccurate. Since the Whonix support cycle does not
match the Qubes support cycle, and since whonix templates are not
official templates, it is better to remove from them from the table and
direct users to the Whonix website for official information about
support status.
These announcements contain outdated information, and they mostly just
duplicate information that is already on each vendor's website. By
removing these links, we refrain from directing users to read
out-of-date information when they can instead get the latest information
from each vendor. Moreover, we don't have to worry about our duplicate
information becoming desynchronized from each vendor, which would create
confusion for users.
At noted by Marek [1] GPG keyrings for verifying 4.1+ packages only
started being available in 4.1 templates. Telling people to fetch
the keyrings through another method would make instructions too
complicated. For this reason it seems simpler to just tell people to
use the new templates instead.
[1]: https://github.com/QubesOS/qubes-doc/pull/1345#issuecomment-1803517947
Tell users to upgrade the software sources. Otherwise they may miss
on critical integrations for 4.2 like VMExec (for the updater to work)
and most importantly, after 4.1 is EOL, it'll silently stop resolving
qubes package upgrades even though the template is not yet EOL.
