To view the list of links, please access this site using Tor Browser.
If you’re seeing this message, access is restricted for regular browsers.
Already using Tor? If you are sure you’re currently in Tor Browser, proceed to our .onion version:
shell in terminal.
pubs: gpg --export --armor
secs: gpg --export-secret-keys --armor
subs: gpg --export-secret-subkeys --armor
if you give no keynames then you will get all keys by default.
secrets contain pubs (or can be regained).
consider symmetrically encrypting the asymmetric secrets with a strong password during transport though:
gpg --armor --export-secret-keys | gpg --armor -c --cipher-algo AES256 > secrets.enc.asc.txt
then copy the file and import it on the other host:
gpg -d secrets.enc.asc.txt | gpg --import
the piping should prevent the files from ever being stored in unencrypted form on a harddisk.
so you are protected from incorrectly / shallowly wiping files after transport, because transport is still securely encrypted symmetrically with strong password, even if recovered.
bonus points for seeing how ssd wear leveling might likely not overwrite / shred / wipe the file which is an opsec failure if the file were copied / stored in unencrypted form.
multiple passwords will be asked, for each secret and for the symmetric encryption transport password (possibly twice for added security).