Call now to talk to an automation expert — (512) 345-2211

Knowledge Base

Enter search queries below or use the tag links to the right to browse the knowledge base by category (Show All Tags).

Unable to decrypt PGP encrypted file after upgrading to version 3.6

The most common error in this situation is:

*No appropriate OpenPGP secret key for decryption found
*Key cannot be found in your keyring. [1280]

However, you may see other error messages depending on the circumstances.

The PGP implementation in version 3.6 is not fully backward compatible with previous versions of Robo-FTP.

This break in compatibility was necessary in order to add some new highly requested features such as the ability to manage multiple private keys.

When you upgrade an existing installation with the version 3.6 installer, it displays a Migration Guide. It does not allow you to proceed with the installation without signifying that you have read this migration guide.

In most cases, you can resolve this issue by following the instructions of the migration guide. This guide is reproduced below.

Robo-FTP 3.6 Migration Guide

(If you are not using PGP you can skip this document)

What's new?

Robo-FTP 3.6 includes a new and improved PGP implementation. Here are some highlights:

  • Standards-compliant encryption/decryption based on OpenPGP
  • Store multiple private keys and their passphrases

How does this affect me?

The new version has been made backward compatible as much as possible, so most scripts should "just work." However, there are a few important differences:

Specifying keyring file location with PGPENCRYPT and PGPDECRYPT script commands

This has been deprecated and will be removed in a future release. If the location you are specifying is the default location (usually C:\Program Files\Robo-FTP) then you can simply remove this argument from the command line. If your script specifies a different location, you should import that keyring with the Robo-FTP Configurator and then remove this argument from the command line.

Signature verification

Signature verification options are now managed by using the /signature option with the PGPDECRYPT command. Change references like this: /gpgopt="-skip-verify" to this: /signature=ignore.

Using /gpgopt to change encryption/decryption behavior

This option is no longer used and will be ignored by Robo-FTP. Contact Technical Support if you are using this option and have questions about how this change will affect your script.

Compatibility with old versions of PGP Desktop

Recipients using very old versions of PGP Desktop may not be able to decrypt files encrypted with Robo-FTP. If you encounter this problem you can use the /compat option with PGPENCRYPT to create PGP Desktop 2.x compatible files (2 Gb file size limit).

Signing files

If you are using a single private key you should not need to make any changes to your script. If you had been signing with multiple private keys by specifying keyrings from the command line, you must import those keyrings using the Robo-FTP Configurator as described above and specify which key to use with the /sign= options (see Help file for details).

Article last updated: 2016-11-22

Tags: PGP, GPG

Need help figuring out where to start?

Our sales staff is available to answer product questions and help you determine if Robo-FTP is a good match for your project.

Call Now: (512) 345-2211