Tickets :: Comment on [#13190] import of large keyfiles fails

* Your Email Address
* Spam protection	Enter the letters below: __ .__ . . __ . . / `[__)\|\ \|/ `\| \| \__.[__)\| \\|\__.\|__\|
Comment	>>> But IMP can't handle keyfiles that are exported by gpg command line. >>> I exported my whole public keyring with "gpg -a --output $FILE >>> --export". >>> This file contains all public keys without a separator >> >> There's your problem. Horde/IMP only supports armored PGP data. >> From Horde_Crypt_Pgp_Parse: >> >> "Provides method to parse PGP armored text data." >> >> We don't support binary data. > > I know that Horde refuses to import a binary keyfile. As I wrote > above I exported all the keys with "-a" - as armored data. > > Maybe I wasn't clear enough: gpg -a creates a keyfile that lists all > the keys without separator - it looks like this: > > -----BEGIN PGP PUBLIC KEY BLOCK----- > $KEY_1$KEY_2$KEY_3 > -----END PGP PUBLIC KEY BLOCK----- > > That's how my keyfile looks like. There's no break between the keys > and no separator. With those keyfiles the error described in this > bugreport occurs. > > It seems that Horde need a key file like this: > > -----BEGIN PGP PUBLIC KEY BLOCK----- > $KEY_1 > -----END PGP PUBLIC KEY BLOCK----- > -----BEGIN PGP PUBLIC KEY BLOCK----- > $KEY_2 > -----END PGP PUBLIC KEY BLOCK----- > -----BEGIN PGP PUBLIC KEY BLOCK----- > $KEY_3 > -----END PGP PUBLIC KEY BLOCK----- > > With seahorse (a gui for key management) I created such a keyfile and > had no problems with Horde import. > > >> For what it's worth, your gpg appears to be broken. "-a" means to >> output armored text. > > I used "-a" and the output is ASCI not binary. Tested with different > Linux distros (Debian wheezy and Fedora 20) - same output: a keyfile > without separators between the keys. > > Hope this helps to reproduce the error. >
Attachment
Watch this ticket

Saved Queries