Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.7.0
Description
Users have requested the capability to paste the ASCII-armored key contents into an EncryptContent processor property in order to decouple from from an external keyring (for both encryption and decryption).
The private key would be protected as a sensitive property (encrypted in the flow.xml.gz the same as a password field). The public key can either be protected in the same way, or treated as a plaintext value (it is not sensitive). There should be an additional field to record the unique identifier of the respective key (i.e. key ID or fingerprint + description).
Specifying all of this information may be confusing on the default processor property dialog, and so an "Advanced"/"PGP" custom UI should be provided which organizes this information in a helpful way.
Obviously, encrypting with a literal public key or decrypting with a literal private key should be easily interoperable with another encryption/decryption operation (either with another instance of EncryptContent within NiFi referencing an external keyring or using an external tool like GnuPG).
Attachments
Issue Links
- is depended upon by
-
NIFI-7322 Add SignContentPGP and VerifyContentPGP Processors
- Resolved
-
NIFI-7396 Add encryption metadata attributes for PGP encryption
- Resolved
- is fixed by
-
NIFI-8251 Add Encrypt and Decrypt PGP Processors and Services
- Resolved
- is related to
-
NIFI-5335 PGP processor cannot handle multiple passworded keys in a pgp keyring.
- Resolved
-
NIFI-6708 Improve DSA/El Gamal PGP compatibility issues
- Resolved
-
NIFI-1694 EncryptContent processor should accept keyring file or individual key file for PGP encryption/decryption
- Resolved
- relates to
-
NIFI-7836 Add Encrypt and Decrypt CMS Processors and Services
- Resolved
- links to