On Wed, May 14, 2014 at 11:32:07AM +1000, Fraser Tweedale wrote:
This behaviour also occurs for me in 2.0.22. Instead of exporting
the key, you could use --list-keys, which works for me:
Yeah, I'm not interesting in running it from the keyring, as I am assuming that
the key is not imported,
On Tue, May 13, 2014 at 11:30:21PM -0400, David Shaw wrote:
Looks like a bug. Note that on each of the keys that didn't work there is a
direct signature on the key. This is not very common, and is usually used
for a designated revoker (i.e. I permit so-and-so to revoke my key for me).
I
On Wed, 14 May 2014 14:51, aaron.topo...@gmail.com said:
Ah. Interesting. Should I file a proper bug against GnuPG then?
Please do that.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
___
Gnupg-users
On Wed, May 14, 2014 at 06:26:31PM +0200, Werner Koch wrote:
Ah. Interesting. Should I file a proper bug against GnuPG then?
Please do that.
Done. https://bugs.g10code.com/gnupg/issue1640
Thanks,
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o .
I don't know if this is a bug, or if I am doing something wrong, so I might as
well ask here. I ran the following command from my terminal, and cannot
retrieve the fingerprint from the file:
$ gpg --output 0xBB065B251FF4945B.gpg --export 0xBB065B251FF4945B
$ gpg --with-colons
On Tue, May 13, 2014 at 05:15:57PM -0600, Aaron Toponce wrote:
I don't know if this is a bug, or if I am doing something wrong, so I might as
well ask here. I ran the following command from my terminal, and cannot
retrieve the fingerprint from the file:
$ gpg --output
On May 13, 2014, at 7:15 PM, Aaron Toponce aaron.topo...@gmail.com wrote:
I don't know if this is a bug, or if I am doing something wrong, so I might as
well ask here. I ran the following command from my terminal, and cannot
retrieve the fingerprint from the file:
$ gpg --output
