Message was not integrity protected.

Wolff, Alex awolff at newbreed.com
Fri Aug 6 19:26:04 CEST 2010


Hi.

 

I know this has been dicussed before...but I have yet to see a
resolution:

A vendor encrypts data with our public key.  We receive the file and we
attempt to decrypt it.  Although the file does get decrypted we receive
the warning below.  How do we avoid the warning..we think it is messing
up our automated integration software we use to encrypt/exchange/decrypt
files.

 

Thank you!

 

$ gpg --force-mdc --output testkey.txt --decrypt
return-100806-06-06173908.txt.gpg

 

You need a passphrase to unlock the secret key for

user: "Lawson Admin (New Breed Corp) <lawsonadmin at newbd.com>"

2048-bit ELG-E key, ID CCE12B6F, created 2010-07-21 (main key ID
23A60DF6)

 

gpg: encrypted with 2048-bit ELG-E key, ID 48FD7CE5, created 2003-07-23

      "CFT BatchOps <batchops at solspark.com>"

gpg: encrypted with 2048-bit ELG-E key, ID CCE12B6F, created 2010-07-21

      "Lawson Admin (New Breed Corp) <lawsonadmin at newbd.com>"

File `testkey.txt' exists. Overwrite? (y/N) y

gpg: WARNING: message was not integrity protected

 

$

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20100806/bfce7b5b/attachment-0001.htm>


More information about the Gnupg-users mailing list