Invalid subkey binding

Dennis Lambe Jr. malsyned@cif.rochester.edu
Sun May 4 19:01:01 2003


--=-wDpzIZUcxWGEL32oTokP
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2003-05-03 at 19:04, Jason Harris wrote:
> Check the verbose (default) listing on keyserver.kjsl.com and see that
> a "[keybind, hash: type 2, 6e 50]" signature is present on both subkeys,
> making it likely to be a duplicate (that is invalid when paired with
> the wrong subkey).

On Sat, 2003-05-03 at 20:53, David Shaw wrote:
> Probably someone sent an update to your key to one of the other
> keyservers, which garbled it a bit, and re-synched that back to
> keyserver.bu.edu.  Basically, one of your subkeys has two signatures
> on it, only one of which is valid.
>=20
> So long as you have both your subkeys (and you do), it's a harmless
> warning, and can safely be ignored.

Thanks for the info, guys.  This mailing list is incredibly friendly and
useful.

I'm glad this isn't going to be a problem.  I don't suppose there's a
way to get that erroneous subkey signature to go away?  some kind of
magical revocation certificate that makes the world forget it even
existed?

--Dennis Lambe

--=-wDpzIZUcxWGEL32oTokP
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: My public key is available at http://cif.rochester.edu/~malsyned/public_key.html

iD8DBQA+tUfa+yh/ThbejSgRAlMJAJ9RshikIbgEudPLsTrrGIsYzlCi4ACghFgj
g9dOCPv6Hxy/0Z4m0+sj4Xw=
=l8wX
-----END PGP SIGNATURE-----

--=-wDpzIZUcxWGEL32oTokP--