We suggest that you download and install the GNU Privacy Guard (GnuPG) to generate PGP keys for use with integrator.io. Due to platform restrictions, we are unable to support PGP keys generated with GnuPG version 2.1.0 or later. Celigo uses GnuPG version 2.0.19 on Macintosh and version 2.0.20 on Windows* to generate our test PGP keys. Therefore, we recommend that you use GPG 2.0.19 on Macintosh and 2.0.20 on Windows as well.
In addition, do not generate PGP keys that use the AES cipher. If you encounter an error that says "AES/CFB/NoPadding is not supported", try generating a new PGP key that uses 3DES or IDEA ciphers instead.
Note: If there's no setting to change the cipher type, try downgrading your PGP keytool to a version that doesn't use AES/CFB/NoPadding. For more information, refer your PGP keytool's documentation.
|*To install GnuPG 2.0.20 on Windows, we use Gpg4win version 2.1.1, which can be found here.|
Note: During GnuPG 2.0.20 installation on Windows, if you encounter an error that says "This app has been blocked for your protection.", perform the steps mentioned here.
After installing GnuPG open a command line window (such as PowerShell/Command Prompt on Windows using Run as administrator or the Terminal on Macintosh) and type the following command:
Follow the on-screen prompts to generate a PGP key:
1. On the command line screen, enter 1 (RSA and RSA (default) gets selected) and then press Enter.
2. On the command line screen, enter the keysize.
Note: The keysize number must not be greater than 4096.
3. On the command line screen, specify the expiry duration of the key. For example, enter 0 if you don't want the key to expire and then press Enter.
4. Enter Real name, Email address, and Comment that help you to identify the key being generated.
5. Set a Passphrase for use with your PGP keys.
The PGP key will be added to your GnuPG keyrings. Ensure that you note down the key's fingerprint to identify the keys you just generated. For example, in the below image, the strings starting with 23D0D911B815 are the key's fingerprints.
IMPORTANT: Exercise caution when entering PGP keys into integrator.io. A few Websites and text editors may add extra newlines to the key files because they double space all files, by default. It is very important that the key files do not have any extra newlines. Otherwise, the files cannot be parsed.
You can use the following command to export the private PGP key to a file:
gpg --export-secret-key -a -o <filename> <fingerprint>
You can use the following command to export the public PGP key to a file:
gpg --export -a -o <filename> <fingerprint>
To resolve the error that occurs during GnuPG 2.0.20 installation on Windows:
1. On your Windows machine, click the Windows icon on the bottom left and search for Command Prompt.