segvBugs
ActivePublic

Members

  • This project does not have any members.

Watchers

  • This project does not have any watchers.

Details

Description

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

Recent Activity

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
gniibe added a commit to T5151: GPGME++ : bad passphrase problems: rG605ab99912ac: gpg: Report an error for receiving key from agent..
Nov 26 2020, 1:52 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