#75 ✓invalid
Alex (via GPGTools)

64 bit alignment issue

Reported by Alex (via GPGTools) | December 29th, 2011 @ 10:06 AM

Can't reproduce it (32bit and 64bit version works here as exprected). Here is the template for the GnuPG dev mailing list:

Dear all,

just another report from our side (but I assume this issue is known):

Description: Incompatible byte alignment on the keychain files
Version: 2.0.18 / OSX

Steps that will reproduce the problem?
1. Create a keyring using a 32bit version of GnuPG
2. Open this keyring using a 64bit version of GnuPG

What is the expected result?
GnuPG should be able to use the keyring.

What happens instead?
???

Possible workaround:
Since we're planning to distribute MacGPG2 for OS X on PPC and Intel machines with 32bit and 64bit installations the current workaround is to avoid 64bit builds.

Any additional information:
From Benjamin: "Unfortunately, x64 builds are presenting problems on systems that have already used the i386 version as the byte alignment on the keychain files are incompatible; they are not designed to be portable between machines or architectures".

Best regards, XXX

--
http://gpgtools.org
http://gpgtools.org/about (Google+, Twitter, RSS)

Comments and changes to this ticket

  • Sierk

    Sierk January 2nd, 2012 @ 07:18 PM

    Is this a general issue of GnuPG 2, or is this an issue only for one person and not always reproducable?
    Did the MacPorts folks have the same issue on their gnupg2 and gpg-agent builds (default build architecture of MacPorts for Snow Leopard and Lion is x86_64)? If they've had the same issue, how did they solve it?

    MacPorts: Portfile gpg-agent
    https://trac.macports.org/browser/trunk/dports/security/gpg-agent/P...

    MacPorts: Portfile GnuPG2
    https://trac.macports.org/browser/trunk/dports/mail/gnupg2/Portfile

  • Alex (via GPGTools)

    Alex (via GPGTools) January 2nd, 2012 @ 09:42 PM

    • Assigned user set to “Benjamin Donnachie”

    Hi Sierk,

    thank you for your feedback and the pointers:

    Is this a general issue of GnuPG 2, or is this an issue only for one person and not always reproducable?

    I can't reproduce it but Benjamin reported it and Roman confirmed it. Waiting for feedback on how to reproduce it myself (this is the "???" part)

    Did the MacPorts folks have the same issue on their gnupg2 and gpg-agent builds (default build architecture of MacPorts for Snow Leopard and Lion is x86_64)? If they've had the same issue, how did they solve it?

    I'll ask around (starting with the GnuPG dev list) after I was able to reproduce it.

  • steve

    steve January 3rd, 2012 @ 04:35 PM

    • State changed from “open” to “waiting”

    Waiting for patch from GnuPG.

  • Alex (via GPGTools)

    Alex (via GPGTools) January 4th, 2012 @ 08:00 AM

    • Assigned user set to “Benjamin Donnachie”
    • State changed from “waiting” to “open”

    Actually, we're not waiting for a patch from GnuPG since I've not sent the mail yet because I don't know how to reproduce the issue...

  • Luke Le

    Luke Le January 25th, 2014 @ 07:25 PM

    • State changed from “new” to “invalid”

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