On Mon, 5 Feb 2018 16:41, jlight...@dsservices.com said:
> Basic questions:
> 1) Is the above message in fact an "error"?
Yes. It may either indicate an internal error in gpg or a wrong usage
(see next).
> 2) What exactly does it mean?
When starting the encryption and if possible gpg records t
On 05/02/18 16:41, Lightner, Jeffrey wrote:
> 3) The command line we used to do the encryption without the new flag was:
> /usr/bin/gpg --always-trust --armor --recipient -o
> --encrypt
> Where is the encrypted file and
> is the original unencrypted file.
>
> 4) The command line with the ne
of the original file:
gpg: do_plaintext(): wrote 1210414045 bytes but expected 822504068 bytes
That appeared to me to be an error but it didn't prevent the ascii armored
(encrypted) file from being created (and subsequently uploaded).
The original unencrypted file has nearly the same
