This is relevant for VSD-3.3 IMO since from a security standpoint it makes sense to regularly change the encryption subkeys and expire old ones while keeping the sign/certify key.
It should also allow you to create an Authentication / Sign subkey though since there are usecases for that, too.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRAcef9c2b0bc61 Implement adding subkeys to an existing key | |||
| rKLEOPATRAebc411664d75 Implement adding subkeys to an existing key | |||
| rKLEOPATRA6b0a2f87967a Implement adding subkeys to an existing key | |||
| rKLEOPATRAbb27866f5ccd Implement adding subkeys to an existing key | |||
| rKLEOPATRAb4be37f5f001 Implement adding subkeys to an existing key | |||
| rKLEOPATRAf97d6fc3815b Implement adding subkeys to an existing key | |||
| rKLEOPATRAf3b590b38c37 Implement adding subkeys to an existing key | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Testing | None | T6874 Kleopatra subkey management improvements | ||
| Resolved | • TobiasFella | T6877 Kleopatra: Add support for adding a subkey |
Tested with gpg4win-beta-50:
Adding a subkey works, its possible to add A, E or S subkeys with different algorithms and expiration dates.
One minor irritation: you do not see what the standard algorithm will be before you create it.
Works in VS-Desktop-3.2.94.481-Beta and you even see beforehand which algo will be used:
