Running tests with a modified keybox, so that the the keybox has only the meta data and the actual keyblocks are stored in separate files improved --list-keys by a factor of 10. This can be explained by reducing the size of pubring.kbx (which is sequentially scanned) from 95 to 2.5 MIB.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 1 2018
I added "futuredefault" as an alias and also made the matching case-insensitiv. Changing the rendering is not easy because using a non-breaking hyphen in @code{} would not look very nice.
Dec 31 2017
The conformance problem may (only) happen between PGP 2.6 and OpenPGPcard, because PGP 2.6 uses old format not compatible to PKCS#1, but OpenPGPcard requires PKCS#1.
that solved the problem, by updating libassuan
When i read the manpage, nroff-formatted against an 80-column terminal, it says, literally:
Dec 30 2017
Enabled Logging, and here the results with some Errors inside...
It is
future-default
and not
futuredefault
Ok - thats good news.
Thank you very much for your analysis.
Dec 29 2017
Any fix for this should be included in the test suite to avoid a regression :)
Using an external process as an option is fine. However adding more dependencies to gnupg should be avoided.
So… Is there any interest in the approach I drafted in D442?
I can see the case for encryption subkeys. Signing subkeys are still useful after their expiration.
OK, I got the picture, now.
Well, my speculation of SERIALNO undefined may be wrong.
Thanks, I received the log file.
Dec 28 2017
If you are encountering the problem, please
- Check that you have updated your Windows operation system to the latest version and you've got all security updates. (As some necessary certificates may have come later with an update.)
- Does the behaviour change if you "investigate the certificate chain" through -> Properties -> Digital Signatures?
Thank you for your efforts. Logfiles is in the mail
We recieved another mail by a customer about this issue today:
Thanks a lot for your testing. Here are my keys:
Dec 27 2017
All right - that was quicker.
I deinstalled pcscd (apt remove pcscd)
I changed .gnupg/scdaemon.conf as you proposed.
I tried again to decrypt the message (in the meantime I have a file) which works decrypting withoutl SmartCard when I use it on a pc with the key.
Still failed. Can I send you the Logfile encrypted ? If so - what is you eMail / key.
As said - it took me a while. Sorry for the delay.
I could dig out the Key in some archives. So I was able to test the decryption of the message on a computer without smartcard.
It worked.
Thanks for your report. This is because GnuPG 2.2.4 now requires newer libassuan (in order to fix a race condition).
Thanks a lot. I'm going to push the fix to 2.2 (and then master).
In short, it was the bug in ccid-driver of scdaemon, which was introduced last year when I enhanced it to support multiple card readers at once.
Dec 26 2017
Yes, thank you, the smartcard is being recognized now.
Thanks (again). According to the status code (bStatus), the card reader said no card is available.
Could you please remove the card and re-insert it, and do 'gpg --card-status'?
After
patch -i scdaemon-fix-for-inactive-start.diff scd/ccid-driver.c
the following log obtains.
Dec 25 2017
Thanks a lot for your testing. Please test this patch:
After installing libusb-devel, and configure and make, this is the new log.
Thanks. I think that you configured GnuPG without libusb, thus, ccid-driver is not enabled, and you don't have pcscd installed. In this situation, no way to access any smartcard reader.
Dec 24 2017
Please enable all debug information in scdaemon.conf, like:
verbose verbose debug-level guru debug-all debug-ccid-driver log-file /run/user/1000/scdaemon-verbose.log
The file scdaemon.log is short and contains only:
2017-12-24 12:32:53 scdaemon[4347] écoute sur la socket « /run/user/1000/gnupg/S.scdaemon » 2017-12-24 12:32:53 scdaemon[4347] gestionnaire pour le descripteur -1 démarré 2017-12-24 12:32:53 scdaemon[4347] pcsc_establish_context failed: no service (0x8010001d)
Thanks for your testing. please give me scdaemon.log with updated scdaemon.
Dec 23 2017
With latestes master, there still appears:
--- ~ » gpg --card-status 2 ↵ gpg: NOTE: THIS IS A DEVELOPMENT VERSION! gpg: It is only intended for test purposes and should NOT be gpg: used in a production environment or with production keys! gpg: selecting openpgp failed: Aucun périphérique de ce type gpg: la carte OpenPGP n'est pas disponible : Aucun périphérique de ce type
im on devuan jessie
Dec 22 2017
Dec 21 2017
Dec 20 2017
Werner, what you mean "Exactly 20 years ago..." ? Dec 20, 8:33 PM
Dec 19 2017
All fixed (or marked fuzzy) except for master which will be done with the next merge from 2.2.
Sample Keys are now openly available at https://wiki.gnupg.org/SampleKeys
As answered in the forum: https://wald.intevation.org/forum/forum.php?thread_id=1837&forum_id=21&group_id=11 :
Unsupported Protocol means that GpgOL can't find your GnuPG installation. Maybe something went wrong during the install of Gpg4win?
OK. I realized that msgfmt -c only works when #, c-format exist.
To check all problems, I did something like following for 1.4, 2.0, 2.2, and master:
Dec 18 2017
Thanks for the report. It seems there has been this bug for four years.
I don't know the reason why msgfmt -c doen't show us the error.
Fixed in repos of GnuPG 1.4, 2.2, 2.0 and master.
Dec 17 2017
It also happens with gpg1.4.22 with --gen-key option.