Bug list update, 02.12.2002

[Miguel Coca]

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

On Tue, Dec 03, 2002 at 11:46:35 -0500, David Shaw wrote:
> On Tue, Dec 03, 2002 at 05:33:45PM +0100, Miguel Coca wrote:
> > We shouldn't encourage users to change the expiration date of their keys
> > (unless maybe in advanced mode). The "expire" command in --edit-key only
> > changes the primary key, not any encryption subkeys you may have.
>=20
> You can change the expiration of subkeys if you do "key n", (where
> n=3D=3Dthe subkey number) before you do "expire".

Yes, we talked about that back in August. It was decided that changing the
expiration date of a subkey didn't have much sense, as you can always
generate another subkey (you can check the archives for details).

Also, I'd like to know something. Can we trust that the subkeys are listed
in the same order in a key listing and in the edit menu. It doesn't happen
with user ID's (which will eventually be a problem, as soon as we want to
add a way to manage user ID's).

Regards,
--=20
Miguel Coca                                         e970095@zipi.fi.upm.es
PGP Key 0x27FC3CA8                         http://zipi.fi.upm.es/~e970095/

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE97OQWjE3Htif8PKgRAh2jAKCY9dJEME1Ku4TBMWzghf2lSIWqnQCfbFGD
q+qu2SZ05418pW1GI5meEHM=
=2aPy
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--