For example, if you want to do some extra editing to the key, which can't be done with EGPG due to its limited set of functionality, you can do it like this:
egpg gpg --edit-key 562AC309C01D2DBD
Running gpg as a subcommand of egpg will ensure
that it uses the same environment (GNUPGHOME) as egpg.
egpg init), you
can migrate all the data from an existing GPG or EGPG environment
(with egpg migrate).For example:
egpg key fetch -k 01D532A283DC1CBF egpg contact fetch 01D532A283DC1CBF
The commands for working with files are these:
egpg seal <file> [<recipient>...]
Sign and encrypt a file. The resulting file will have the
extension '.sealed'. The original file will be erased.
egpg open <file.sealed>
Decrypt and verify the signature of the given file.
The file has to end with '.sealed' and the output will have
that extension stripped.
egpg sign <file>
Sign a file. The signature will be saved to <file.signature>.
egpg verify <file.signature>
Verify the signature. The signed file must be present as well.
This is done with the external command:
egpg key2dongle
EGPG manages all this with simple commands:
egpg key split [-d,--dongle <dir>] [-b,--backup <dir>]
Split the key into 3 partial keys and store one of them on the
dongle (removable device, usb), keep the other one locally,
and use the third one as a backup. Afterwards, whenever the
key needs to be used, the dongle has to be present.
egpg key join
Join two partial keys into a full key and delete the partials.
egpg key recover <backup-partial.key.xyz>
Recover the key from the backup partial key and from the
partial key of the home or the dongle. This is useful when
either the dongle or the home partial key is lost.
For an external command the script will look:
The first that is found is loaded and used.