FG
💻 Software

gpg: WARNING: message was not integrity protected

Fresh5 days ago
Mar 15, 202619742 views
Confidence Score0%
0%

Problem

I'm a little confused as what this means. What's happened is that someone has encrypted a message for me using my public key, and signed it with their private key - as per usual. Next, I decrypt the message... ...I know the message is verbose and I probably should understand what it is getting at -…

Error Output

-bash-3.2$ gpg --decrypt /tmp/det_prod_cred.txt.asc 
gpg: encrypted with 2048-bit ELG-E key, ID 2E52ED13, created 2001-10-15
      "XXXXXXX1"
gpg: en…

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Unverified Fix
New Fix – Awaiting Verification

Fix for: gpg: WARNING: message was not integrity protected

Low Risk

There are two different warnings here, and I think the other responders are assuming the one is caused by the other. I assume the "message was not integrity protected" warning is your main concern, since that's the title of this question. There seem…

Awaiting Verification

Be the first to verify this fix

Sign in to verify this fix

Environment