gpg: do_plaintext(): wrote 1210414045 bytes but expected 822504068 bytes

Peter Lebbing peter at
Tue Feb 6 10:51:30 CET 2018

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 <RECIPIENT> -o <BASEFILENAME.dat.asc> --encrypt <BASEFILENAME.dat.txfr>
> Where <BASEFILENAME.dat.asc> is the encrypted file and <BASEFILENAME.dat.txfr> is the original unencrypted file.
> 4) The command line with the new flag:
> /usr/bin/gpg --exit-on-status-write-error --always-trust --armor --recipient <RECIPIENT BANK ID> -o <BASEFILENAME.dat.asc> --encrypt <BASEFILENAME.dat.txfr>

While you are waiting for someone who knows what's going on to answer, I
think you should try to add --batch to the command line. Any
non-interactive use of the gpg binary always needs to have --batch. The
same pretty much goes for --with-colons, I don't know whether or how you
interpret output from gpg, but --with-colons gives you the
machine-readable form.

It's possible that it behaves a bit more pleasantly for this problem
with --batch, as it now understands that it's being used as such.



I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Gnupg-users mailing list