Optionally import the trustdb file as well: gpg -import-ownertrust otrust. Indeed, there are device network discovery problems in the latest releases of Windows 10: you can’t see other computers on network, or your Windows 10 is not showing up in Workgroup. Transfer those files to a place that the new user can read, keeping in mind that it's bad practice to share private keys (e.g., via email or in a world-readable directory like /tmp), despite the fact that they are encrypted and require the passphrase to be usedĪs the new user, execute gpg -import commands against the two asc files and then check for the new keys with gpg -k and gpg -K, e.g.: gpg -import myprivatekeys.asc I received several emails from readers asking me to help solving the problem of displaying computers in a network environment on the latest Windows 10 builds. Optionally export gpg's trustdb to a text file: gpg -export-ownertrust >otrust.txt Use the following command to export all encrypted private keys (which will also include corresponding public keys) to a text file: gpg -a -export-secret-keys >myprivatekeys.asc
Can I just copy the ~/.gnupg directory?Īs the original user, use the following command to export all public keys to a base64-encoded text file: gpg -a -export >mypubkeys.asc I need to make all of the gpg keyrings from one user available to another user on the same system. We need to migrate GPG keys from a user on AIX to a user on RHEL.
0 kommentar(er)
