FEATURE REQUEST: Do not abort encryption with PGP Command line when disabled key matched in keyring


Article ID: 157896


Updated On:


PGP Command Line


When attempting to encrypt a file with Symantec PGP Command Line and one of the keys matched by recipient pattern is disabled, the encryption operation is aborted.

This feature request demands modification of this rule and assure that encryption will complete successfully, even if matched key is disabled (Symantec PGP Command Line would not include such key to the list of keys used for encryption)

0x12345678:encrypt (3025:key disabled)


Symantec Corporation is committed to product quality and satisfied customers.  This Feature Request is currently being considered by Symantec Corporation to be addressed in a forthcoming version of the product.
Technical Support filed a Feature Request to add this product feature. Note that an feature request is exactly that, a request.
There is no committed date for this request from the Endpoint Encryption Product Management team, nor from the Endpoint Encryption Engineering team at this time.

Please be sure to refer back to this document periodically as any changes to the status of the request will be reflected here.

The following may be used is a temporary workaround for the issue until the version with requested feature is released: This issue can be temporarily resolved by one of the following:

  • Providing more exact patter for recipient USERID or KEYID
  • Validation of the key properties (test if key is disabled prior adding it to recipient list)
  • Removal of disabled key from keyring

Applies To

PGP Command Line 10.x