Fri, Aug 23
oops: That was an accidential priority change
The mentioned "strange hangs" would only be solvedwhen using master - in 2.2 we already had proper locking.
Implemented master and 2.2. Note that the comment in the master commit about possible reason for stucked keylisting in gpgsm is only related to master.
I implemented it nearly as suggested. However, the default AKL is used, which is "local,wkd" (local is not used with that command though).
Fixed for 2.2.18. To allow seeing these warnings this change will only have an effect if a listing of all keys is requested.
Done for 2.2.18
This was already fixed with version 2.2.5.
Will be in 2.2.18
I changed the suggestion to read:
The agent is an important part of gnupg and it does not make sense to single out cases when it might not be needed. I can't see any harm from having an agent running. In fact, one of th netxt versions will add yet another daemon which will then be needed in all cases.
Thu, Aug 22
Note that rGd3f5d8544fdb needs to be backported to 2.2 but we will wait until we have better tested it.
Wed, Aug 21
Mon, Aug 19
Tue, Aug 13
Mon, Aug 12
I am in charge of editing the current OpenPGP draft, so I will for sure keep an eye on that issue. If would appreciate if you can post your report also to openpgp at ietf org.
Re-reading the original report from 2001 it seems that PGP and PGP do the same. Back then these were the only OpenPGP implementations (except for that book with the OpenPGP tool based implementation). We did quite some interop testing in the early years by passing OpenPGP data back and forth. So one could assume this is a bug in the specs becuase the specs are for large parts derived from the PGP 5 code base.
- Office work
- Attended Froscon.org on Saturday
Fri, Aug 9
Thanks for reporting.
Please explain in more detail what does not work. Outlook 365 is actually part of our test environment.
Thu, Aug 8
/hex is just a diagnostic helper and not expected to be used to retrieve data.