Page MenuHome GnuPG

Fw: gnupg/198: Didn't import additional new subkey
Closed, ResolvedPublic

Description

Description

This is a multi-part message in MIME format.

------=_NextPart_000_00FA_01C365DB.7AA20EB0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Sorry,
Forgot to cc: you...

----- Original Message -----=20
From: Richard Newell=20
To: gnupg-hackers@gnupg.org ; gnats-admin@trithemius.gnupg.org=20
Sent: Monday, August 18, 2003 10:50 PM
Subject: Re: gnupg/198: Didn't import additional new subkey


Hi all,

Regarding bug report...

http://bugs.gnupg.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&pr=3D1=
98&database=3Ddefault

You say...

"GnuPG does not let you merge secret keys - if you want to
import a new secret subkey onto an existing secret key, you
must delete the existing secret key first."

However, if you read my step six in the original submission, you will =
see that I tried that, and it didn't work...

"6) I deleted the secret key from my gpg keyring, and reimported it from =
the file. It imported the key with the expired subkey, but not the new =
subkey."

Please give this bug report some further consideration.  I suspect that =
if you try the steps I did, you will be able to reproduce the error.

Rich

------=_NextPart_000_00FA_01C365DB.7AA20EB0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Sorry,</FONT></DIV>
<DIV><FONT size=3D2>Forgot to cc: you...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dgrnewell@earthlink.net =
href=3D"mailto:grnewell@earthlink.net">Richard=20
Newell</A> </DIV>
<DIV><B>To:</B> <A title=3Dgnupg-hackers@gnupg.org=20
href=3D"mailto:gnupg-hackers@gnupg.org">gnupg-hackers@gnupg.org</A> ; <A =

title=3Dgnats-admin@trithemius.gnupg.org=20
href=3D"mailto:gnats-admin@trithemius.gnupg.org">gnats-admin@trithemius.g=
nupg.org</A>=20
</DIV>
<DIV><B>Sent:</B> Monday, August 18, 2003 10:50 PM</DIV>
<DIV><B>Subject:</B> Re: gnupg/198: Didn't import additional new=20
subkey</DIV></DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D2>Hi all,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Regarding bug report...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><A=20
href=3D"http://bugs.gnupg.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trai=
l&amp;pr=3D198&amp;database=3Ddefault">http://bugs.gnupg.org/cgi-bin/gnat=
sweb.pl?cmd=3Dview%20audit-trail&amp;pr=3D198&amp;database=3Ddefault</A><=
/DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>You say...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>"</FONT><FONT size=3D3>GnuPG does not let you merge =
secret keys=20
- if you want to<BR>import a new secret subkey onto an existing secret =
key,=20
you<BR>must delete the existing secret key first."</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>However, if you read my step six in the original =
submission,=20
you will see that I tried that, and it didn't work...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>"<FONT face=3D"Courier New" size=3D3>6) I deleted =
the secret key=20
from my gpg keyring, and reimported it from the file. It imported the =
key with=20
the expired subkey, but not the new subkey."</FONT></FONT></DIV>
<DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Please give this bug report some further =
consideration.&nbsp;=20
I suspect that if you try the steps I did, you will be able to reproduce =
the=20
error.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Rich</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_00FA_01C365DB.7AA20EB0--

Fix

Unknown