Hello,
possibly there is a bug present if manipulating a GnuPG key with subkeys
attached!?
Example:
We want to expire validity of primary key and all subkeys.
C:>gpg --edit-key 7BF4xxxx
gpg> expire
This command modifies the date for primary key only, subkeys are NOT
affected.
BUT:
C:>gpg --edit-key 7BF4xxxx
gpg> key *
gpg> expire
This command only modifies the date for all subkeys, primary key is NOT
affected.
In my opinion
gpg> key *
should select all included key parts, primary key + all subkeys, but it
doesn't!?
So is it 'by design' (not logical, why?) or is it a bug in GnuPG-2.2x?
How to select all key parts (sec + ssb + ssb + ssb...)?
Thx + regards, Chris
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
possibly there is a bug present if manipulating a GnuPG key with subkeys
attached!?
Example:
We want to expire validity of primary key and all subkeys.
C:>gpg --edit-key 7BF4xxxx
gpg> expire
This command modifies the date for primary key only, subkeys are NOT
affected.
BUT:
C:>gpg --edit-key 7BF4xxxx
gpg> key *
gpg> expire
This command only modifies the date for all subkeys, primary key is NOT
affected.
In my opinion
gpg> key *
should select all included key parts, primary key + all subkeys, but it
doesn't!?
So is it 'by design' (not logical, why?) or is it a bug in GnuPG-2.2x?
How to select all key parts (sec + ssb + ssb + ssb...)?
Thx + regards, Chris
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users