Expiry and subkeys

[Ben Finney]

--MIMEStream=_0+240413_30423625111387_6626659499
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw"
Content-Disposition: inline


--wac7ysb48OaltWcw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 06-Jun-2003, CL Gilbert wrote:
> So your main key is still expired, but you made a sub key on that
> expired key, which is not expired?
>=20
> What did you do with the original subkey?
>=20
> sounds like you have done away with your original encrypting key.  Do
> you still have the original private key?  You did not delete the
> expired portion did you?

I don't really know the answers to your questions.  Is this enough
diagnostic information?  How do I get more (to answer your questions)?

=3D=3D=3D=3D=3D
$ gpg --list-keys bignose
pub  1024D/BD41714B 2000-01-19 Ben Finney <bignose@zip.com.au>
sub  2048g/05508D5C 2003-01-19 [expires: 2006-01-18]
sub  4096g/3D0FDD17 2000-01-19 [expires: 2003-01-18]
=3D=3D=3D=3D=3D

I was happily using the key long after the expiry date of 2003-01-18; it
has only been in the last month that I get the message (immediately
following the command, before any prompt):

=3D=3D=3D=3D=3D
echo 'Blah' | /usr/bin/gpg --armor --clearsign -
gpg: no secret subkey for public subkey 3D0FDD17 - ignoring

You need a passphrase to unlock the secret key for
user: "Ben Finney <bignose@zip.com.au>"
1024-bit DSA key, ID BD41714B, created 2000-01-19

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Blah
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iEYEARECAAYFAj7h0K8ACgkQt6wuUb1BcUubygCg2asOIzQ9GkPcuvlsR51IzjHi
4WAAnilXoy7Vodp3yc4foP9RpeE5rrSv
=3DNP/1
-----END PGP SIGNATURE-----
=3D=3D=3D=3D=3D

--=20
 \           "If you're a cowboy and you're dragging a guy behind your |
  `\      horse, I bet it would really make you mad if you looked back |
_o__)             and the guy was reading a magazine."  -- Jack Handey |
bignose@zip.com.au  F'print 9CFE12B0 791A4267 887F520C B7AC2E51 BD41714B

--wac7ysb48OaltWcw
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iEYEARECAAYFAj7h0OgACgkQt6wuUb1BcUsszwCfQ1m/tCnnDB5+AJFF2xad0uld
0TsAn0uV3oHMsbZoT3vLFbvIs/q7WJSd
=z+A0
-----END PGP SIGNATURE-----

--wac7ysb48OaltWcw--
--MIMEStream=_0+240413_30423625111387_6626659499
Content-Type: text/sanitizer-log; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="sanitizer.log"

This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1054986475"):
  Forcing message to be multipart/mixed, to facilitate logging.
  Writer (pos="1312"):
    Part (pos="1361"):
      Part (pos="183"):
        SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
          Match (rule="9"):
            Enforced policy: accept

      Part (pos="2065"):
        SanitizeFile (filename="unnamed.txt", mimetype="application/pgp-signature"):
          Match (rule="9"):
            Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $

--MIMEStream=_0+240413_30423625111387_6626659499--