Page MenuHome GnuPG

segvBugs
ActivePublic

Members

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

Watchers

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

Details

Description

Segmentation violation aka segmentation fault.
Used for all kind of crashes except for failed asserts.

Recent Activity

Wed, May 11

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

The change improve error handling for possible other errors by device: rG53eddf9b9ea0: scd: Fail when no good algorithm attribute.

Wed, May 11, 4:31 AM · Testing, backport, yubikey, scd, segv, Bug Report

Tue, May 10

gniibe edited projects for T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys, added: Testing; removed gnupg.

Applied to 2.2 branch, too.

Tue, May 10, 7:29 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe removed a project from T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys: Info Needed.
Tue, May 10, 3:50 AM · Testing, backport, yubikey, scd, segv, 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.

Tue, May 10, 3:48 AM · Testing, backport, yubikey, scd, segv, Bug Report

Mon, May 9

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.

Mon, May 9, 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.
Mon, May 9, 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.

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

Fri, May 6

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

With the patch and after starting a new gpg-agent, gpg --card-status now works immediately.
But when I re-plug the yubikey, gpg reports gpg: OpenPGP card not available: Card error until either gpg-agent is restarted, or pcscd is restarted.
pcsc-lite in debug mode reports no errors, but one log is obviously much shorter as gpg fails early (I've attached both).

Fri, May 6, 1:42 PM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

I pushed a workaround.

Fri, May 6, 11:28 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe renamed T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys from scdaemon causes libc segfault and clashes with pcsc-lite despite using disable-ccid to Yubikey: scdaemon causes libc segfault and clashes with ECC keys.
Fri, May 6, 11:26 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe added a project to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys: yubikey.
Fri, May 6, 10:07 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe claimed T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.
Fri, May 6, 8:56 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

For my environment, it is not PC/SC-specific. It also occurs when CCID driver is used.

Fri, May 6, 8:42 AM · Testing, backport, yubikey, scd, segv, Bug Report
gniibe added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

For bcdDevice 5.24, I can replicate the symptom, but only once. After second invocation of gpg --card-status, it works well.

Fri, May 6, 8:26 AM · Testing, backport, yubikey, scd, segv, Bug Report

Thu, May 5

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

I've applied the patch and can confirm that the segfault is fixed, but gpg still has severe problems communicating with the Yubikey.

Thu, May 5, 12:10 PM · Testing, backport, yubikey, scd, segv, Bug Report
werner added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

Ours are even newer (5.4.3). Did you the Yubico tools to switch to curve443?
In any case, is it possible that you apply my fix and test again?

Thu, May 5, 10:06 AM · Testing, backport, yubikey, scd, segv, Bug Report
werner added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

Your Yubikey's firmware version is 5.2.7 - let me see what versions we have in stock to test my fix.

Thu, May 5, 9:51 AM · Testing, backport, yubikey, scd, segv, Bug Report

Wed, May 4

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

I've taken the liberty to regenerate the valgrind report including libc and gnupg debugsyms. Maybe it'll help.

Wed, May 4, 4:47 PM · Testing, backport, yubikey, scd, segv, Bug Report
werner updated subscribers of T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

I am not sure about the crash but the unknown curve is
1.3.6.1.4.1.11591.15.1.2 which seems to be a GNU OID for curve448

Wed, May 4, 2:38 PM · Testing, backport, yubikey, scd, segv, Bug Report
oddlama added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

It segfaults on SERIALNO. Here's what valgrind outputs:

Wed, May 4, 12:48 PM · Testing, backport, yubikey, scd, segv, Bug Report
werner added a comment to T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.

What I would do in this case is to stop the gnupg daemon amd anything whiuch might start them and run scdaemon under valgrind.

Wed, May 4, 10:13 AM · Testing, backport, yubikey, scd, segv, Bug Report

Mon, May 2

oddlama created T5963: Yubikey: scdaemon causes libc segfault and clashes with ECC keys.
Mon, May 2, 11:21 PM · Testing, backport, yubikey, scd, segv, Bug Report

Sep 7 2021

werner closed T5577: Null ptr dereference in gpg-agent (gnupg 2.3.2) as Resolved.

Fixed in 2.3 and 2.2

Sep 7 2021, 9:04 AM · segv, gnupg (gpg23), Bug Report
werner reopened T5577: Null ptr dereference in gpg-agent (gnupg 2.3.2) as "Open".

(I closed this by accident)

Sep 7 2021, 7:54 AM · segv, gnupg (gpg23), Bug Report

Aug 30 2021

werner closed T5577: Null ptr dereference in gpg-agent (gnupg 2.3.2) as Resolved.

Aihhh, my fault. seems that a new version it not too far away.

Aug 30 2021, 4:42 PM · segv, gnupg (gpg23), Bug Report

Aug 13 2021

werner changed the edit policy for segv.
Aug 13 2021, 11:14 PM

Dec 1 2020

gniibe closed T5151: GPGME++ : bad passphrase problems as Resolved.
Dec 1 2020, 5:34 AM · segv, gpgme, Bug Report

Nov 26 2020

gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

For ctx->exportPublicKeys returning 0 even when a failure, (with fix of gpg) error handling should be done differently.

Nov 26 2020, 2:22 AM · segv, gpgme, Bug Report

Nov 25 2020

nmset added a comment to T5151: GPGME++ : bad passphrase problems.

Well, I fixed my loopback passphrase provider and the application no longer crashes with a bad passphrase.

Nov 25 2020, 10:16 PM · segv, gpgme, Bug Report
nmset added a comment to T5151: GPGME++ : bad passphrase problems.

relatively new feature

Yes. In the mean time, I'm using a cheap workaround : validate the input passphrase by signing a dummy text before exporting. Not that ugly and can stay for long.

Nov 25 2020, 8:33 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

More specifically, in the situation of multiple calls, ->getPassphrase is called multiple times, and it should return newly allocated "char *" object each time, because it is released each time (in lower layer).

Nov 25 2020, 1:22 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

My excuse: Please note that the support of exporting secret keys by GPGME are relatively new feature (see {T5046) and the fix rM3382ecb17eb5: core: Support exporting secret keys.). The fix of rM53ac732bae46: core: Call _gpgme_passphrase_status_handler when exporting keys. is a part of the support.
I think that we need more fixes for gpg/gpgme to be fully working well.

Nov 25 2020, 12:51 AM · segv, gpgme, Bug Report

Nov 24 2020

nmset added a comment to T5151: GPGME++ : bad passphrase problems.

when passphrase is wrong, the passphrase callback is called more than one time (one for primary key, and another for a subkey, more if there are more subkeys).

Nov 24 2020, 9:30 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

Currently, gpg doesn't report any errors to status line for exporting secret keys. If needed, a patch like this is needed:

Nov 24 2020, 8:12 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

Chasing this bug, I pushed a change: rM53ac732bae46: core: Call _gpgme_passphrase_status_handler when exporting keys.

Nov 24 2020, 7:08 AM · segv, gpgme, Bug Report

Nov 23 2020

ikloecker added a comment to T5151: GPGME++ : bad passphrase problems.
In T5151#139353, @nmset wrote:

Using Context::setExpire(), expiry time of keys and subkeys can be changed in a predictable way, with good and bad passphrase (fails with error of course).

Nov 23 2020, 12:30 PM · segv, gpgme, Bug Report
nmset added a comment to T5151: GPGME++ : bad passphrase problems.

I highly recommend to use the new ChangeExpiryJob instead of the fragile (and apparently buggy) edit interactor.

Nov 23 2020, 11:56 AM · segv, gpgme, Bug Report
nmset added a comment to T5151: GPGME++ : bad passphrase problems.

Can you try if using the overload

Nov 23 2020, 11:06 AM · segv, gpgme, Bug Report
ikloecker added a comment to T5151: GPGME++ : bad passphrase problems.

Can you try if using the overload

Error Context::exportPublicKeys(const char *patterns[], Data &keyData, unsigned int flags)

which takes an array of patterns instead of a single pattern also crashes?

Nov 23 2020, 10:15 AM · segv, gpgme, Bug Report
ikloecker added a comment to T5151: GPGME++ : bad passphrase problems.

Unless you need some special features of GpgSetExpiryTimeEditInteractor or you have to support gpgme <1.15, I highly recommend to use the new ChangeExpiryJob instead of the fragile (and apparently buggy) edit interactor.

Nov 23 2020, 10:06 AM · segv, gpgme, Bug Report

Nov 22 2020

werner triaged T5151: GPGME++ : bad passphrase problems as High priority.
Nov 22 2020, 10:22 AM · segv, gpgme, Bug Report
werner edited Description on segv.
Nov 22 2020, 10:20 AM
werner set the color for segv to Red.
Nov 22 2020, 10:18 AM