#40 ✓released
Benjamin Donnachie

Secret keys unusable

Reported by Benjamin Donnachie | January 30th, 2011 @ 11:31 PM | in 2.0.18 (closed)

Two users have reported issues following MacGPG2 v2.0.17 installs whereby they receive errors concerning their secret keys being unusable.

Possibility this may be linked to removal of --disable-endian-check option from compile of libgcrypt.

New versions of libraries sent to affected users to test. Awaits confirmation of issue.

If confirmed, will trigger immediate new release.

Comments and changes to this ticket

  • Benjamin Donnachie
  • Benjamin Donnachie

    Benjamin Donnachie January 31st, 2011 @ 08:31 PM

    • Tag set to critical

    Confirmed not libgcrypt related, however confined to 32-bit systems only.

    Pure 32-bit test version available from http://rapidshare.com/files/445517114/32-bit-MacGPG2-2.0.17-test1.zip

    Remove MacGPG2, change to root directory and then unarchive:

    sudo rm -fr /usr/local/MacGPG2
    cd /
    sudo unzip path/to/file/32-bit-MacGPG2-2.0.17-test1.zip
    

    Then rerun tests.

  • Benjamin Donnachie

    Benjamin Donnachie January 31st, 2011 @ 09:10 PM

    • Tag changed from critical to 32-bit, critical
  • Benjamin Donnachie

    Benjamin Donnachie January 31st, 2011 @ 09:26 PM

    32-only build tested by one affected user so far and successful.

  • Benjamin Donnachie

    Benjamin Donnachie January 31st, 2011 @ 10:10 PM

    Another affected user confirms successful.

  • Benjamin Donnachie

    Benjamin Donnachie January 31st, 2011 @ 11:04 PM

    On 31 January 2011 20:28, Benjamin Donnachie <benjamin@py-soft.co.uk> wrote:
    > Fingers crossed for the rest of you!

    I have a combined 64- and 32- build available for testing from
    http://rapidshare.com/files/445538395/MacGPG2-64-32-attempt2.zip

    Same procedure as before; remove MacGPG2, change to root directory and
    then unarchive:

    sudo rm -fr /usr/local/MacGPG2 cd / sudo unzip path/to/file/MacGPG2-64-32-attempt2.zip

    Then rerun tests. Should it fail, just reinstall
    32-bit-MacGPG2-2.0.17-test1 from earlier.

    I'll pick up the results in the morning (GMT).

    Thank you for your patience with this!

    Take care,

    Ben

  • Benjamin Donnachie

    Benjamin Donnachie February 11th, 2011 @ 10:51 PM

    • Importance changed from “” to “”

    Have been unable to isolate the issue. Rebuilding 32-bit only version.

  • Andreas

    Andreas February 12th, 2011 @ 02:51 PM

    The 32bit test builds seem to solve the problems related to 32bit hardware.

    I can create secret keys and I can encrypt and decrypt email with these keys.

    During the key creation process, running gpg --gen-key in terminal.app, german characters like ä ö ü are printed a bit strange on screen. Just have a look:

    s10e:Documents andreas$ gpg --gen-key
    Bitte wählen Sie, welche Art von Schlüssel Sie möchten:
    (1) RSA und RSA (voreingestellt) (2) DSA und Elgamal (3) DSA (nur signieren/beglaubigen) (4) RSA (nur signieren/beglaubigen) Ihre Auswahl? 1
    RSA-Schlüssel können zwischen 1024 und 4096 Bit lang sein.
    Welche Schlüssellänge wünschen Sie? (2048) 1024
    Die verlangte Schlüssellänge beträgt 1024 Bit
    Bitte wählen Sie, wie lange der Schlüssel gültig bleiben soll.

         0 = Schlüssel verfällt nie
      <n>  = Schlüssel verfällt nach n Tagen
      <n>w = Schlüssel verfällt nach n Wochen
      <n>m = Schlüssel verfällt nach n Monaten
      <n>y = Schlüssel verfällt nach n Jahren
    

    Wie lange bleibt der Schlüssel gültig? (0) 1
    Key verfällt am Sun Feb 13 14:37:16 2011 CET
    Ist dies richtig? (j/N) j

    GnuPG erstellt eine User-ID um Ihren Schlüssel identifizierbar zu machen.

    Ihr Name ("Vorname Nachname"): John Doe
    Email-Adresse: john@example.com
    Kommentar:
    Sie haben diese User-ID gewählt:

    "John Doe <john@example.com>"
    

    Ändern: (N)ame, (K)ommentar, (E)-Mail oder (F)ertig/(A)bbrechen? f
    Sie benötigen eine Passphrase, um den geheimen Schlüssel zu schützen.

    Wir m"ussen eine ganze Menge Zufallswerte erzeugen. Sie k"onnen dies
    unterst"utzen, indem Sie z.B. in einem anderen Fenster/Konsole irgendetwas
    tippen, die Maus verwenden oder irgendwelche anderen Programme benutzen.
    Wir m"ussen eine ganze Menge Zufallswerte erzeugen. Sie k"onnen dies
    unterst"utzen, indem Sie z.B. in einem anderen Fenster/Konsole irgendetwas
    tippen, die Maus verwenden oder irgendwelche anderen Programme benutzen.
    gpg: Schl"ussel A64BC3F4 ist als uneingeschr"ankt vertrauensw"urdig gekennzeichnet
    "Offentlichen und geheimen Schl"ussel erzeugt und signiert.

    gpg: "Trust-DB" wird "uberpr"uft
    gpg: "off. Schl"ussel des uneingeschr"ankt vertrautem Schl"ussel 7574A959 nicht gefunden
    gpg: 3 marginal-needed, 1 complete-needed, classic Vertrauensmodell
    gpg: Tiefe: 0 g"ultig: 7 signiert: 14 Vertrauen: 0-, 0q, 0n, 0m, 0f, 7u
    gpg: Tiefe: 1 g"ultig: 14 signiert: 7 Vertrauen: 1-, 1q, 0n, 2m, 10f, 0u
    gpg: Tiefe: 2 g"ultig: 1 signiert: 0 Vertrauen: 0-, 0q, 0n, 0m, 1f, 0u
    gpg: n"achste "Trust-DB"-Pflicht"uberpr"ufung am 2011-02-13
    pub 1024R/A64BC3F4 2011-02-12 [verf"allt: 2011-02-13]
    Schl.-Fingerabdruck = 981C FCAF C5C3 445B C9A2 D4E7 788F C6A1 A64B C3F4 uid John Doe john@example.com
    sub 1024R/7674CA37 2011-02-12 [verf"allt: 2011-02-13]

    Cheers and keep up the good work,
    Andreas

  • steve

    steve February 13th, 2011 @ 01:46 PM

    I tried setting up a friends machine. I experienced behaviour similar to the one described in this ticket, while using the latest GPGTools installer from 20110201 (couldn't import any keys in keychain, couldn't create a sec key ect).

    I then tried the MacGPG alpha you posted on rapidshare and that solved the problem.

    (just FYI)

  • Benjamin Donnachie

    Benjamin Donnachie February 14th, 2011 @ 04:24 PM

    • State changed from “open” to “resolved”

    New build released. Will need to create separate ticket for language issues.

  • Alex (via GPGTools)

    Alex (via GPGTools) December 28th, 2011 @ 01:27 PM

    • Milestone set to 2.0.18
    • Importance changed from “” to “”
  • steve

    steve March 30th, 2013 @ 02:28 PM

    • State changed from “resolved” to “new”
    • Tag cleared.
    • Assigned user cleared.
    • Importance changed from “” to “Low”
  • steve

    steve March 30th, 2013 @ 02:29 PM

    • State changed from “new” to “fixed”
  • steve

    steve June 18th, 2015 @ 04:40 PM

    • State changed from “fixed” to “released”

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket

Referenced by

Pages