Encrypting to secondary key
Larry Ellis
Larry_C_Ellis@hotmail.com
Mon Sep 16 15:01:02 2002
This is a multi-part message in MIME format.
------=_NextPart_000_00A0_01C25D57.24A0C890
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
When encrypting to a DSA/El Gamal key, GPG forces use of the secondary =
(El Gamal) key for encryption. In verbose mode:
gpg -v -e -r <primary keyid> <file>
results in:
gpg: using secondary key <secondary keyid> instead of primary key =
<primary keyid>
However, the same message is issued if the secondary key is specified =
directly:
gpg -v -e -r <secondary keyid> <file>
also results in:
gpg: using secondary key <secondary keyid> instead of primary key =
<primary keyid>
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....
------=_NextPart_000_00A0_01C25D57.24A0C890
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>When encrypting to a DSA/El Gamal key, =
GPG forces=20
use of the secondary (El Gamal) key for encryption. In verbose=20
mode:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>gpg -v -e -r <primary keyid> =
<file></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>results in:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>gpg: using secondary key=20
<secondary keyid> instead of primary key <primary=20
keyid></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>However, the same message is issued if =
the=20
secondary key is specified directly:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>gpg -v -e -r <secondary =
keyid>=20
<file></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>also results in:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>gpg: using secondary key=20
<secondary keyid> instead of primary key <primary=20
keyid></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>One cannot argue with the truth of the =
message, but=20
I wonder if it is intentional to output this message even when the key =
is=20
specified directly....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></DIV></BODY></HTML>
------=_NextPart_000_00A0_01C25D57.24A0C890--