bug : exporting a set of public keys into an asc file

[Marc Meurrens]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

It seems there is a bug in version 0.7.6 of gpa.

Gpa allows you to select *one* public key and export it
(with the menu entry of the button 'export key*s*').

Gpa allows you to select a set of public keys,
but does nothing when you click on 'export keys'

I hope you can reproduce the bug.

Below is a comparison of the behaviour of gpa, seahorse and Kgpg
regarding the export (or backup) of public and private keys
to ascii files (and for seahorse to a zip file)

Regards

marc

===================

With *seahorse*,
you can backup your 2 key rings into a single zip file
you can export a set of public keys into an .asc file
you can NOT export your private key(s) into an .asc file (use gpa to do
this)
of course, you can import from an .asc file

With *gpa*,
you can NOT backup your 2 key rings into a single tar.gz or other file
(use seahorse to do this)
you can export one public key into an .asc file
you should be able to export a set of public keys but currently there is
a BUG (thus, use seahorse to do this)
you can export (backup) one private key into an .asc file
if you have multiple private keys, you can NOT export them all into a
single .asc file (wait for a next version of gpa or seahorse ?)
of course, you can import from an .asc file

With *KGpg*,
you can NOT backup your 2 key rings into a single tar.gz or other file
(use seahorse to do this)
you can export a set of public keys into an .asc file
you can NOT export your private key(s) into an .asc file (use gpa to do
this)
of course, you can import from an .asc file

If I remember well, with *GPG under Windows*,
I was able to export my multiple private keys into a single ascii file.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHN3bvwq/V6u582tIRAgXQAKC9iMspptWS7VOGsVwCxtLqmvpFiACg4sFO
oCETnnsvB37vA9gNxtZcuxA=
=A2L7
-----END PGP SIGNATURE-----