Discuss this help topic in SecureBlackbox Forum

Deal with typical OpenPGP issues

There are not too many typical issues when it comes to OpenPGP. Still, we aim to give the best advice we have about those that you may come across.

  1. The resulting OpenPGP file appears to be encrypted/signed with several keys where there only should be one. Most likely the key used for encryption has a subkey and encryption is done for both key and subkey. To disable the subkey (i.e. exclude it from encryption process), set it's Enabled property to false. Note that a key might have multiple subkeys with different purposes, so you need to assess carefully which exactly subkeys (or the main key itself) are to be disabled.
  2. 'No keys for decryption found' error is returned when processing a protected file. This means that the component was unable to find an appropriate decryption key. This may happen if the needed key is missing from the keyring, or if the key itself is present but its passphrase has been provided incorrectly.
  3. The decrypting third party displays the message in 'secure viewer' and doesn't allow to save it to file. Remember to set ElPGPWriter.Filename to the name of the original file when encrypting the data. If the name is omitted, a special '_CONSOLE' name is used, which forces the decrypting party to treat the message as 'for your eyes only' and display it in its secure viewer.

How To articles about common OpenPGP tasks

Discuss this help topic in SecureBlackbox Forum