Page MenuHome GnuPG

Info NeededCommunication
ActivePublic

Members

  • This project does not have any members.
  • View All

Watchers

  • This project does not have any watchers.
  • View All

Recent Activity

May 18 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Glad to hear. I've also now had time to manually apply the patches and have not seen any issues so far! Thank you! If anything does turn up later down the road I'll let you know.

May 18 2022, 2:10 AM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

No, no apologize needed. You did your best for the bug report, and it helped us a lot to identify the issue, and it certainly helped resulting the fixes. Moreover, your report kicked another fix of T5979 (thanks to the valgrind output).
Thank you.

May 18 2022, 1:37 AM · Info Needed, yubikey, scd, Bug Report

May 17 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

I apologize, you seem to be right. Even though the package build log shows that all patches were applied, it seems there are some hunks missing in the generated sources.
I've attached my patches, but those are most likely correct. There seems to be an issue with my distribution's package manager. I will investigate this and report back afterwards. Maybe I'll just build it manually.

May 17 2022, 1:34 PM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

When compiling the package, I can see that all 4 are applied.

May 17 2022, 2:41 AM · Info Needed, yubikey, scd, Bug Report

May 16 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

I think that it means that you only applied the last two patches.

May 16 2022, 4:14 PM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Thanks again for your update.

May 16 2022, 3:08 AM · Info Needed, yubikey, scd, Bug Report

May 13 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Thanks a lot for your cooperation.

May 13 2022, 2:28 PM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

I put more fix for error handling of key algorithm attribute.
The change: rG53eddf9b9ea0: scd: Fail when no good algorithm attribute.

May 13 2022, 3:21 AM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Thanks a lot for your cooperation.

May 13 2022, 3:15 AM · Info Needed, yubikey, scd, Bug Report

May 12 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Contrary to your expectations, all gpg --card-status fail after yubikey insertion:

May 12 2022, 7:48 PM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Please do experiment again and give us the whole log of scdaemon.log for:

  • insert Yubikey initially
  • run gpg --card-status (success is expected)
  • remove Yubikey
  • insert Yubikey second time
  • run gpg --card-status (failure is expected)
May 12 2022, 5:19 PM · Info Needed, yubikey, scd, Bug Report
oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

In case you need any information, be sure to let me know. Maybe we can add some manual loggers to the patches, to confirm that everything is working as you imagine it to?

May 12 2022, 12:36 PM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Umm... The problem is the last bogus octet from Yubikey. In the log, we see:

May 12 2022, 1:43 AM · Info Needed, yubikey, scd, Bug Report

May 11 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

I'm certain I've applied the patches correctly. This is my current patchset:

May 11 2022, 12:49 PM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

Thank you for the logs. It seems that scdaemon didn't detect the removal correctly.

May 11 2022, 1:50 AM · Info Needed, yubikey, scd, Bug Report

May 10 2022

oddlama added a comment to T5971: Yubikey: Removal of device is not detected by PC/SC.

I've uploaded the requested information with triple verbose and debug-all setting in the scdaemon.conf as scdaemon.log:

May 10 2022, 10:17 PM · Info Needed, yubikey, scd, Bug Report
gniibe removed a project from T5971: Yubikey: Removal of device is not detected by PC/SC: gnupg.
May 10 2022, 7:00 AM · Info Needed, yubikey, scd, Bug Report
gniibe added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

I examined all log files you gave us, and I think that scdaemon with PC/SC fails to detect the removal of the USB device.

May 10 2022, 3:48 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe triaged T5971: Yubikey: Removal of device is not detected by PC/SC as Normal priority.
May 10 2022, 2:51 AM · Info Needed, yubikey, scd, Bug Report

May 9 2022

oddlama added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

I've applied the linked patch, but still experience the error. Most of the times, I cannot access my yubikey at all and I am not sure what is blocking it.
I've tried to include as much debugging output as I could below. Please let me know if there is anything else I can do to debug this.

May 9 2022, 12:54 PM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe added a project to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys: backport.
May 9 2022, 6:52 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe added a project to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys: Info Needed.

The patch rG054d14887ef8: scd: Add workaround for ECC attribute on Yubikey. fixes a particular problem of Yubikey implementation where it returns bogus octet for its data object of C1, C2, and C3.

May 9 2022, 4:53 AM · Testing, backport, yubikey, scd, segv, Bug Report

Apr 27 2022

ikloecker placed T5546: Kleopatra: After importing the first pubkey for a card from LDAP the keylistview is not refreshed up for grabs.

The issues mentioned in the previous comment have been fixed.

Apr 27 2022, 1:22 PM · scd, Info Needed, Restricted Project, kleopatra
ikloecker claimed T5546: Kleopatra: After importing the first pubkey for a card from LDAP the keylistview is not refreshed.

I had a look at the file system watcher we use to react on changes in the GnuPG home directory. It doesn't watch the private keys living in private-keys-v1.d. Moreover, it does not handle the removal of files properly.

Apr 27 2022, 11:18 AM · scd, Info Needed, Restricted Project, kleopatra

Apr 14 2022

werner closed T1954: Password too long as Resolved.
Apr 14 2022, 3:05 PM · Info Needed, gnupg (gpg20), Bug Report, gnupg

Mar 28 2022

gniibe closed T5428: PC/SC detecting removal of card as Resolved.

When we will find reproducible test case, please reopen.

Mar 28 2022, 3:51 AM · Info Needed, Windows, scd, Bug Report

Mar 23 2022

gniibe added a comment to T5804: Using empty passphrase key pair, gpg2.3.4 fails to decrypt with error "No passphrase given" on a gpg1.4/2.0 keyring format even though the secret keys migration was successful .

Thank you.

Mar 23 2022, 7:11 AM · Bug Report, gnupg (gpg23)

Mar 22 2022

engel97 added a comment to T5673: Using empty passphrase key pair, gpg2.2.9 fails to decrypt with error "No secret key" on a gpg1.4/2.0 keyring format even though the secret keys migration was successful .

Attached is the keyring package containing both pub and sec ring files. When run into GPG2.2.9, this gets migrated to the newer format but it fails when the the passphrase is empty(which works in older gpg)

Mar 22 2022, 5:14 PM · gnupg (gpg22), Bug Report

Mar 19 2022

engel97 added a comment to T5804: Using empty passphrase key pair, gpg2.3.4 fails to decrypt with error "No passphrase given" on a gpg1.4/2.0 keyring format even though the secret keys migration was successful .

{F3381469}I uploaded the whole homedir containing the keys after they were migrated by the new gnupg2.3.4. It should have all of the keys in there. Don't worry, these keys are just for testing and not used anywhere.

Mar 19 2022, 4:21 AM · Bug Report, gnupg (gpg23)

Mar 17 2022

gniibe added projects to T5673: Using empty passphrase key pair, gpg2.2.9 fails to decrypt with error "No secret key" on a gpg1.4/2.0 keyring format even though the secret keys migration was successful : gnupg (gpg22), Info Needed.
Mar 17 2022, 3:33 AM · gnupg (gpg22), Bug Report
gniibe added a project to T5804: Using empty passphrase key pair, gpg2.3.4 fails to decrypt with error "No passphrase given" on a gpg1.4/2.0 keyring format even though the secret keys migration was successful : Info Needed.
Mar 17 2022, 1:53 AM · Bug Report, gnupg (gpg23)

Jan 10 2022

patrick closed T5763: gpgme-json missing as Invalid.

Oh, I' sorry - my fault. I searched in ...\GnuPG\bin instead of ...\gpg4win\bin

Jan 10 2022, 6:44 PM · Info Needed, Bug Report, gpg4win
aheinecke added a project to T5763: gpgme-json missing: Info Needed.

I have just checked both the installation script, which still installs gpgme-json.exe and the gpg4win-4 installer downloaded from gpg4win.org gpgme-json.exe is properly installed under <instdir>\bin gpgme-json.exe and under bin_64

Jan 10 2022, 9:00 AM · Info Needed, Bug Report, gpg4win

Dec 6 2021

piec added a comment to T5657: dirmngr: libdns sends malformed dns requests.

Hi guys, I just tested the git version (426d82fcf1c133bfc1d5c931109d71db3f3815a9) and it works well thank you.

Dec 6 2021, 11:02 AM · Info Needed, Bug Report, dns, dirmngr
gniibe closed T5657: dirmngr: libdns sends malformed dns requests as Resolved.

Fixed in 2.2.33.

Dec 6 2021, 1:01 AM · Info Needed, Bug Report, dns, dirmngr

Nov 13 2021

werner closed T5607: Fingerprint signing fails with 'gpg: signing failed: No secret key' as Resolved.
Nov 13 2021, 2:42 PM · Support, Info Needed, gnupg (gpg22)

Oct 27 2021

werner triaged T5607: Fingerprint signing fails with 'gpg: signing failed: No secret key' as Low priority.

Sure there are logs, see the options log-file and debug in the man pages.
To sign using specific subkey or the main key, use the fingerprint of the key and append an exclamation mark.
For example

Oct 27 2021, 1:12 PM · Support, Info Needed, gnupg (gpg22)
gniibe added a comment to T5574: Doubled characters in Windows console output.

I think that this is due to support of UTF-8 codepage problem by console.

Oct 27 2021, 4:34 AM · gnupg, Windows, gpgrt, Bug Report

Oct 23 2021

Reiner added a comment to T5574: Doubled characters in Windows console output.

Hello Mr. Koch,

Oct 23 2021, 4:20 AM · gnupg, Windows, gpgrt, Bug Report

Oct 22 2021

werner updated subscribers of T5574: Doubled characters in Windows console output.
Oct 22 2021, 3:04 PM · gnupg, Windows, gpgrt, Bug Report
werner added a project to T5574: Doubled characters in Windows console output: Info Needed.

@Reiner: Any news; were you able to run the the command with redirection to some file?

Oct 22 2021, 3:03 PM · gnupg, Windows, gpgrt, Bug Report

Oct 20 2021

werner lowered the priority of T5546: Kleopatra: After importing the first pubkey for a card from LDAP the keylistview is not refreshed from Normal to Low.

Lets downgrade the priority and keep it open in case we get reports from customers. The other option would be to replicate this here using our AD demo network. But that is a bit time consuming.

Oct 20 2021, 12:26 PM · scd, Info Needed, Restricted Project, kleopatra
ikloecker reassigned T5546: Kleopatra: After importing the first pubkey for a card from LDAP the keylistview is not refreshed from ikloecker to aheinecke.

I tried to reproduce this. Experimentally, I added P15CardWidget::searchPGPFpr() to OpenPGPKeyCardWidget, commented out the code that checks for an LDAP keyserver and called the function with a fixed fingerprint.

Oct 20 2021, 11:20 AM · scd, Info Needed, Restricted Project, kleopatra

Oct 15 2021

gniibe added a comment to T5657: dirmngr: libdns sends malformed dns requests.

I don't know if it's same in your case, but to fix my case, I pushed a change rG48359c723206: dns: Make reading resolv.conf more robust.

Oct 15 2021, 3:52 AM · Info Needed, Bug Report, dns, dirmngr
gniibe added a comment to T5657: dirmngr: libdns sends malformed dns requests.

I managed to create a case. Put a line:

Oct 15 2021, 3:28 AM · Info Needed, Bug Report, dns, dirmngr
gniibe added a comment to T5657: dirmngr: libdns sends malformed dns requests.

BTW, in your screen shot (log is preferred here), it shows 1c00, that must be actually written as AAAA (0x1c). In the bug T3803, we saw byte sequence like that, additional 00 was added then resulted malformed DNS packet.

Oct 15 2021, 2:17 AM · Info Needed, Bug Report, dns, dirmngr

Oct 14 2021

werner triaged T5657: dirmngr: libdns sends malformed dns requests as Normal priority.
Oct 14 2021, 1:26 PM · Info Needed, Bug Report, dns, dirmngr
werner added a comment to T5657: dirmngr: libdns sends malformed dns requests.

dots are not allowed in hostnames.

Oct 14 2021, 1:25 PM · Info Needed, Bug Report, dns, dirmngr
piec added a comment to T5657: dirmngr: libdns sends malformed dns requests.

OK, I'll gdb in there to see what happens. My domain is a classic pgp.domain.com

Oct 14 2021, 11:13 AM · Info Needed, Bug Report, dns, dirmngr
gniibe added a comment to T5657: dirmngr: libdns sends malformed dns requests.

Ah, other possible case is .. in hostname.

Oct 14 2021, 7:50 AM · Info Needed, Bug Report, dns, dirmngr