Exporting Non‑Expiring PGP Public Keys Fails with Error or No Response

In MOVEit Automation, non‑expiring PGP public keys import successfully but fail during export—either producing no UI response or a NullReferenceException—while PGP keys with an expiration date export without issue.

Mar 3, 2026
Knowledge

Title

URL Name

exporting-non-expiring-pgp-public-keys-fails-with-error-or-no-response

Article Number

000297918

Environment

MOVEit-MOVEit Automation 2025.1.2

Question/Problem Description

When working with PGP public keys in MOVEit Automation, users may observe the following behavior:

* A public PGP key imports successfully into MOVEit Automation.
* Attempting to export the same key results in one of the following:
* No response when clicking Export in the UI.
* Automation export fails with a System.NullReferenceException.
* The issue occurs consistently with PGP public keys that do not have an expiration date.
* Public keys with an expiration date export successfully.

Steps to Reproduce

1. Import a valid RSA public PGP key (2048‑bit) **without an expiration date** into MOVEit Automation. 2. Verify the key is present and usable. 3. Attempt to export the public key via: * MOVEit Automation UI, or * Automation workflows invoking key export. 4. Observe that the export fails or produces no output. Keys configured with an expiration date do not exhibit this behavior under the same conditions.

Clarifying Information

Error Message

When the failure occurs during Automation processing or logging is enabled, the following exception may be recorded: System.NullReferenceException: Object reference not set to an instance of an object. at DidX.BouncyCastle.Bcpg.OpenPgp.PgpSignature.Encode(...) at DidX.BouncyCastle.Bcpg.OpenPgp.PgpPublicKey.Encode(...) at DidX.BouncyCastle.Bcpg.OpenPgp.PgpPublicKeyRing.Encode(...) at DidiSoft.Pgp.KeyStore.ExportPublicKeyRing(...) at DidiSoft.Pgp.KeyStore.ExportPublicKey(...) at IPSP.DidiPgp.KeyExport(...) This exception is thrown during the public key export operation and may not always surface visibly in the UI.

Defect Number

100650

Enhancement Number

Cause

MOVEit Automation relies on a third‑party PGP implementation (DidiSoft / BouncyCastle) for key handling. When a public PGP key does not include an expiration date, certain expected metadata is not populated during the export process.

As a result:

The export logic attempts to encode signature or key properties that are null or unset.
This leads to a null reference exception during the export operation.
The failure does not prevent import, as expiration metadata is not required at import time.

Resolution

At this time, there is no product‑level fix available in MOVEit Automation 2025.1.2.

Progress Engineering has identified the issue as occurring within the third‑party PGP export logic, and the behavior has been escalated for further investigation.

Workaround

Regenerate or modify the public PGP key to include an expiration date before importing it into MOVEit Automation.
Export the public key from the **original key source** (outside of MOVEit Automation) rather than relying on Automation export.
Avoid Automation workflows that require exporting non‑expiring public keys.

Notes

* This issue does **not** affect encryption, decryption, or import functionality.
* Only the **export operation** is impacted.

Keyword Phrase

Last Modified Date

3/3/2026 12:18 PM

Exporting Non‑Expiring PGP Public Keys Fails with Error or No Response

Files(0)

Was this article helpful?

Was this article helpful?

Exporting Non‑Expiring PGP Public Keys Fails with Error or No Response

Information

Related Articles