[Jelle asked me to forward his mail]
--- Begin Message ---
Werner Koch wrote:
On Fri, 18 Jul 2008 15:09, [EMAIL PROTECTED] said:
I tried searching the internet but found no solutions only this:
https://bugs.g10code.com/gnupg/issue673
Right, you hit this case.
The question now is, how can i backsig my old keys with my smartcard
system to solve the cross-certification workaround?
You need to do this on a system where the real key is available. The
error message indicates that the actual secret key is not available but
replaced by a dummy stub (protection mode 1001). This has nothing to do
with a smart card stub (protection mode 1002).
Salam-Shalom,
Werner
Thanks you again for the good information.
I imported my real security keys and did a cross-certify and uploaded
the keys to your preferred server. When will the key server sync?
gpg --edit-key 6F63E479
Command> cross-certify
Command> quit
gpg --keyserver keys.gnupg.net --send-keys 6F63E479
Because the keys are so imported, I ask a lot and experiment little I
hope this is a bid understandable.
I removed my ~/.gnupg/ folder and restored my original key system and
notisched the cross-certify issue was back agian. Then I updated my keys
with Enigmail agianst the keys.gnupg.net server and this updated my keys
and the cross-certify issues was gone again.
I would like to know how I should backup this new altered keys? What
keys are changed by the cross-certify command and how should I update my
orignal keys.
I have two original files secring.gpg and pubring.gpg
I hope you can help me,
Thanks in advance,
Jelle
gnupg.sh
Description: Bourne shell script
smartcard.sh
Description: Bourne shell script
--- End Message ---
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
