With which key did I sign my encrypted file?

[helices]

Peter,

Thank you. That suffices.

Notice that I did provide --version in my original post.

~ helices


On Wed, Mar 29, 2017 at 10:40 AM, Peter Lebbing <peter at digitalbrains.com>
wrote:

> Hello,
>
> To solve your problem, could you please also post the commands that you
> used to create the files? The information you gave is really too little
> to go on. And also always include which version of GnuPG you're using
> (gpg --version).
>
> On 28/03/17 15:22, helices wrote:
> > Once in awhile, we get pushback from a recipient that they cannot
> > decrypt our file, and sometimes they claim it is because the encrypted
> > file is signed.
>
> I do not understand why the file being signed would be a problem. I'd
> say it's a good thing it's signed.
>
> > $ /usr/bin/gpg --verify NO-sign.pgp
> > gpg: verify signatures failed: Unexpected error
>
> That's what I see for a file that isn't signed. I'd say it's expected,
> though really terse. You're asking it to verify a signature, but don't
> give it a signature. I'd say the file is unexpected rather than the
> error! ;-)
>
> On 29/03/17 16:46, helices wrote:
> > How can I see if an encrypted file is signed and by whom?
>
> If you don't mind decrypted files being saved to disc, either:
>
> -------------------8<------------->8-------------------
> $ gpg enc.txt.gpg
> gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12
>       "Peter Lebbing <peter at digitalbrains.com>"
> File `enc.txt' exists. Overwrite? (y/N) y
> -------------------8<------------->8-------------------
>
> to invoke the default action on the file, and since this is an
> encrypted file that is not signed no signature information is shown. Or
> explicitly:
>
> -------------------8<------------->8-------------------
> $ gpg -o /dev/null -d enc.txt.gpg
> gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12
>       "Peter Lebbing <peter at digitalbrains.com>"
> -------------------8<------------->8-------------------
>
> Which tells GnuPG to decrypt, but send the result to /dev/null, in
> other words, will not create or attempt to overwrite files on disc.
>
> For an encrypted file with a signature it'll look like this instead:
>
> -------------------8<------------->8-------------------
> $ gpg enc-signed.txt.gpg
> gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12
>       "Peter Lebbing <peter at digitalbrains.com>"
> File `enc-signed.txt' exists. Overwrite? (y/N) y
> gpg: Signature made Wed 29 Mar 2017 17:28:28 CEST using RSA key ID DE6CDCA1
> gpg: Good signature from "Peter Lebbing <peter at digitalbrains.com>"
> -------------------8<------------->8-------------------
>
> -------------------8<------------->8-------------------
> $ gpg -o /dev/null -d enc-signed.txt.gpg
> gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12
>       "Peter Lebbing <peter at digitalbrains.com>"
> gpg: Signature made Wed 29 Mar 2017 17:28:28 CEST using RSA key ID DE6CDCA1
> gpg: Good signature from "Peter Lebbing <peter at digitalbrains.com>"
> -------------------8<------------->8-------------------
>
> There are commands to really dive into the contents of an OpenPGP file,
> but this might overwhelm rather than inform you.
>
> HTH,
>
> Peter.
>
> --
> 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 <http://digitalbrains.com/2012/openpgp-key-peter>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20170329/67b0e52b/attachment.html>