Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments for GnuPG: list all recipients of a message #807

Open
phinjensen opened this issue Nov 11, 2017 · 5 comments
Open

Comments for GnuPG: list all recipients of a message #807

phinjensen opened this issue Nov 11, 2017 · 5 comments

Comments

@phinjensen
Copy link
Contributor

phinjensen commented Nov 11, 2017

Comments for https://www.endpointdev.com/blog/2013/05/gnupg-list-all-recipients-of-message/
By Jon Jensen

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
@phinjensen
Copy link
Contributor Author

original author: Greg Sabino Mullane
date: 2013-05-24T10:39:51-04:00

That is annoying; I've not found an easier solution either. I find myself using --no-default-keyring and --dry-run way too often to work around quirks in gnupg.

@neilmayhew
Copy link

For me, using gpg2, the --no-default-keyring technique no longer works. However, -v/--verbose does what I need:

$ gpg --list-only -v -d FILE.gpg
gpg: public key is 310D4243BAC51B24
gpg: public key is C09F593D04C1E593

I can then do gpg --list-secret-keys ... to find the full details of the keys.

Everyone agrees that the GPG UI is quirky, but maybe it's getting better.

@neilmayhew
Copy link

This might be better as a Stack Overflow question.

@NBrouard
Copy link

For me gpg --list-only foo.gpg works and lists all recipients the file was crypted for. I am using gpg 2.2.5 version. But there is still a warning
$ LC_ALL=C gpg --list-only foo.gpg
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 1792-bit ELG key, ID XXXXXXXXXX, created 2005-03-29
name@foo
gpg: encrypted with 2048-bit RSA key, ID YYYYYYYYY , created 2018-02-05
name2@foo2

@neilmayhew
Copy link

@NBrouard That's why I used -d which is the command for decryption. However, --list-only stops it from actually decrypting the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants