Fri, May 17
Wed, May 15
Tue, May 14
I removed this specialized error message. Thanks for reporting.
Thu, May 2
Users keep showing up in our support, confused by this inconsistency. here's the most recent: https://gpgtools.tenderapp.com/discussions/feedback/14701-where-is-the-passphrase
Thu, Apr 25
Tue, Apr 23
Apr 19 2019
Paul Wouters writes to me:
Apr 10 2019
One of the things that dirmngr has going for it is that it tracks the current network state, and it would be nice to be able to reuse that state across sessions. If an ephemeral keyring can't use a shared dirmngr, there are fewer arguments for having dirmngr in the first place, and people might be more justified in replacing it with things like https://gitlab.com/anarcat/scripts/blob/master/openpgp-key-get
Apr 9 2019
I don't anymore think this is a high priority request. BTW, A more real problem than several dirmngr instances is multi-user access to smartcards.
Mar 25 2019
Mar 23 2019
Mar 19 2019
Mar 3 2019
Feb 9 2019
Sure, but lets use that ticket for this. if you have another topic, feel free to open another ticket.
Feb 8 2019
Is a PR to add it to the website welcome? Not sure that I'll get around to it, but in case someone else is interested - I linked here from those stackoverflow pages.
Feb 5 2019
It is in the tarball:
and for example Debian installs it as /usr/share/doc/gnupg/DETAILS.gz. Check out the first section "Format of the colon listings". Or use GPGME which provides C, C++, Python and JSON bindings. Sorry, it never made it to the website.
@werner where is this now documented? I can't find it.
Feb 4 2019
First of all I find PIN a very bad term. "Personal Identification Number" for example for my Gnuk token is confusing. I use a string there,... So let us use PIN only where it really has to be a number. Otherwise it is a Password.
Despite that I created this task, I am still not not convinced that removing the term passphrase is a good idea. If we do this in gnupg we would need to change all strings to make it clear that the passphrase is used to protect one's own key and has nothing to do with encryption etc. In fact the term PIN would be better because it is common knowledge that you use a PIN to get access to something you own. There would be less confusion on the purpose of the passphrase. Sure PIN is usually considered to be a number. However my bank allows a string to be used as, what they call, PIN.
There has been some progress here. At least we no longer use "passphrase" in new code. We still have not yet replaced all old occurances.
Jan 29 2019
Jan 17 2019
T4298: 'make check' with uninstalled library, which is building now (even if rpath doesn't work well) handles related issue, which was fixed for libgcrypt-1.9. Since this issue is for other libraries (libgpg-error, specifically), we could do something similar, but, it may be detecting LD_LIBRARY_PATH to fail with "Please remove LD_LIBRARY_PATH".
Dec 20 2018
Dec 17 2018
It seems it's Ubuntu specific: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1796563
I think that all that we can do is to improve documentation.
Dec 13 2018
yes. that's why i wrote it in '['-brackets.
but usually, in info-documents a synopsis is written about it.
I think that it's not self-evident, that "you can either give a file or let the tool read from stdin or output to stdout" and therefore should be written explicitly.