On Sunday, October 19, 2014 01:18:29 PM you wrote: > On 19/10/14 11:48, Sudhir Khanger wrote: > > By important I mean > > if you only had your secret key could get back to your original setup > > ignoring the imported public keys. > > Yes; also ignoring all assigned ownertrust values. > > Public key and revocation certificate can be recreated; the latter is > usually only used precisely when you have lost access to the secret key. > > I'm fairly sure even certifications from other users are included in the > private key, as long as you don't specify options scrubbing them from > the key on export. > > > 2. "gpg --import secret.key" I suppose this is the command I have to > > use to import the secret key on a new system. > > Additionally, you'll most likely want to assign ultimate ownertrust to > the key; this is automatically done when using --gen-key, but not on > importing a secret key. > > $ gpg2 --edit-key YOURKEYID trust > > HTH, > > Peter.
Thanks. Here is what I did and it worked fine. gpg --import secretkey.asc gpg --edit-key KEYID trust gpg --edit-key KEYID > Chose primary uid > primary > save It imported both secret and public key with both uid and everything seems to work fine as far as I can tell. -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
