Encrypting to secondary key
Larry Ellis
Larry_C_Ellis@hotmail.com
Mon Sep 16 18:58:02 2002
This is a multi-part message in MIME format.
------=_NextPart_000_043D_01C25D78.76296C00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Even if the syntax you specify is used, the warning message I originally =
asked about is still issued. (The message is only displayed in =
"verbose" mode).
Perhaps it is your intention to display that message any time a =
secondary key is used, no matter how the secondary key was selected. =
That seems to be the way gpg is behaving. If so, It's just a little =
confusing for DSA/ElGamal since it is not possible to use the primary =
key for encryption.
> > One cannot argue with the truth of the message, but I wonder if it =
is
intentional to output this message even when the key is specified
directly....
>
> if you want gpg to use a specific subkey, you must append a '!' to the
> keyID: -r 0x12345678!
>
------=_NextPart_000_043D_01C25D78.76296C00
Content-Type: text/html;
charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>Even if the=20
syntax you specify is used, the warning message I originally asked about =
is=20
still issued. (The message is only displayed in "verbose"=20
mode).<BR><BR>Perhaps it is your intention to display that message any =
time a=20
secondary key is used, no matter how the secondary key was =
selected. That=20
seems to be the way gpg is behaving. If so, =
</FONT></FONT><FONT=20
face=3DArial size=3D2><FONT face=3D"Times New Roman" size=3D3>It's just =
a little=20
confusing for DSA/ElGamal since it is not possible to use the primary =
key for=20
encryption.<BR><BR><BR>> > One cannot argue with the truth of the =
message,=20
but I wonder if it is<BR>intentional to output this message even when =
the key is=20
specified<BR>directly....<BR>><BR>> if you want gpg to use a =
specific=20
subkey, you must append a '!' to the<BR>> keyID: -r=20
0x12345678!<BR>><BR></DIV></FONT></FONT></BODY></HTML>
------=_NextPart_000_043D_01C25D78.76296C00--