On 12/31/2016 11:22 AM, Guy Wyers wrote:
The command used to build this export was the following (executed with the
-vv option to get all the info):
$ gpg2 -vv -ao secret-key.asc --export-secret-keys
gpg: writing to 'secret-key.asc'
gpg: key 69F91A22: asking agent for the secret parts
gpg: k
Hey guys,
Interesting development: I rebuilt my whole setup, generated a new keypair
etc. and am now in the process of creating another copy of the secret key
for safekeeping and back-up purposes.
And lo and behold: the problem reappeared, so I'm now in a position to
reproduce the problem. The ex
On 12/27/2016 11:16 AM, MFPA wrote:
The --export-secret-subkeys command will do what it says on the tin.
That option would still generate a secret key packet for the primary
key, it's just that this packet would not actually contain any key material.
Here, what has been generated is a file c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Monday 26 December 2016 at 9:21:37 PM, in
, Damien
Goutte-Gattat wrote:-
> As far as I know, the only way to export a subkey
> only is to explicitly
> specify that subkey by its key ID with an appended
> '!',
The --export-secret-subkeys comm
Thanks for the reply. At least I know where things stand now, which is not
a good place :-(
I guess this is another *fine* example of the principle that an
insufficiently tested DR arrangement, will always break down when you need
it.
I'm still puzzled about this partial export, however. I'm quite
On 12/26/2016 06:52 PM, Guy Wyers wrote:
- Can I somehow recover from this? I guess that, at least theoretically,
the public should be "derivable" from the private key?
The problem here is not that you are missing the public key (the public
key *is* derivable from the private key, and GnuPG wo
That's what I feared looking at the output.
Now, I have two questions:
- Can I somehow recover from this? I guess that, at least theoretically,
the public should be "derivable" from the private key?
- How did I end up with this truncated export? As far as I remember -even
if it was long long time
On 12/26/2016 10:34 AM, Guy Wyers wrote:
Here is the output I get with the -vv option:
Your file seems to contain only a private *sub* key. I don't think GnuPG
can import such a file (I've just tested with a similar file on my
system with GnuPG 2.1.17, I got a similar result).
signature.a
Here is the output I get with the -vv option:
gpg: armor: BEGIN PGP PRIVATE KEY BLOCK
gpg: armor header: Version: GnuPG v2
# off=0 ctb=9d tag=7 hlen=3 plen=966
:secret sub key packet:
version 4, algo 1, created 1481270099, expires 0
pkey[0]: [2048 bits]
pkey[1]: [17 bits]
> Any ideas?
Try verbose mode.
gpg -v --import keyfile.asc
If that doesn't give you enough information, try ultra-verbose mode:
gpg -vv --import keyfile.asc
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/g
I'm using Gnupg2.0 and I'm in a situation where I need to restore my
configuration.
I have an ascii armored export of my private key which looks like
-BEGIN PGP PRIVATE KEY BLOCK-
Version: GnuPG v2
...
-END PGP PRIVATE KEY BLOCK-
When I try to import his using "gpg --import", I ge
11 matches
Mail list logo
