Gpgtools MacGPG2 → 2.2.0

Comments and changes to this ticket

• 

  Luke Le November 23rd, 2016 @ 05:14 PM

  • Importance changed from “” to “Low”

  Hi Pavel,

  thank you for bringing this to our attention.
  From the log it looks like it might be crashing within a log message.

  Would you mind contacting the people at gnupg.org via the dev mailinglist:
  https://lists.gnupg.org/mailman/listinfo/gnupg-devel

  Thanks!

• You flagged this item as spam.
  

  Pavel Borzenkov November 23rd, 2016 @ 05:28 PM

  Actually, it crashes because app refcounter becomes less than zero:

  from scd/app.c:release_application()
  if (!app->ref_count) log_bug ("trying to release an already released context\n"); if (--app->ref_count) return;

  And here is a part of the logfile:

  2016-11-23 19:26:25 scdaemon[10144] sending signal 31 to client 545
  2016-11-23 19:26:31 scdaemon[10144] DBG: asking for PIN '||Please enter the PIN'
  2016-11-23 19:26:37 scdaemon[10144] updating slot 0 status: 0x0007->0x0000 (1->2)
  2016-11-23 19:26:37 scdaemon[10144] sending signal 31 to client 545
  2016-11-23 19:26:38 scdaemon[10144] Ohhhh jeeee: trying to release an already released context

  I'll try to contact upstream regarding this issue.

• 

  Luke Le November 23rd, 2016 @ 05:33 PM

  Ah ok, does log_bug force a crash (assert, the like?)?

  Thanks, it's best to contact upstream in this case.

• You flagged this item as spam.
  

  Pavel Borzenkov November 23rd, 2016 @ 05:44 PM

  Yes, log_bug() calls assert().

  JFYI: filed an upstream issue: https://bugs.gnupg.org/gnupg/issue2852

• 

  Luke Le November 23rd, 2016 @ 06:10 PM

  To completely eliminate GPG Suite as the culprit, you could install gpg2 via homebrew (after uninstalling MacGPG2) and see if the issue persists.
  We have a minor patch for scdaemon and helpers in order to circumvent a timeout on Yosemite which was caused by Apple's tokend drivers (if I recall correctly).

• You flagged this item as spam.
  

  Pavel Borzenkov November 23rd, 2016 @ 06:44 PM

  Unfortunately, gpg2 from homebrew simply doesn't work for me:

  $ gpg2 --card-status gpg: can't connect to the agent - trying fall back
  scdaemon[17683]: pcsc_control failed: invalid parameter (0x80100004)
  scdaemon[17683]: pcsc_vendor_specific_init: GET_FEATURE_REQUEST failed: 65538

  gpg-agent was manually started before.

  And ssh fails to talk to it as well.

• 

  Luke Le November 23rd, 2016 @ 06:47 PM

  Ha, that is interesting. Maybe hombrew installed gnupg 2.1?
  Just checked our patches and there's only one which affects tokens.

• You flagged this item as spam.
  

  Pavel Borzenkov November 23rd, 2016 @ 06:51 PM

  Sorry, I screwed up and forgot to actually export required env variables.

  After doing this, I was able to use gpg2 from homebrew and the problem reproduces just the same.

• 

  steve June 18th, 2017 @ 06:22 PM

  • State changed from “new” to “fixed”

  We have moved to gpg 2.1 so this should be fixed in latest nightly.

  Could you please download and install our latest GPG Suite nightly build and see if the problem persists. That page also has sig and SHA256 to verify the download.

  All the best,
  steve

  Disclaimer: This is a development version which has not been thoroughly tested yet - bugs or crashes are to be expected. Thanks for helping us test.

• 

  steve September 25th, 2017 @ 04:20 PM

  • State changed from “fixed” to “released”

  [bulk edit]