Problem with adding a name to a key

[Ingo Klöcker]

On Donnerstag, 27. Februar 2025 15:18:17 Mitteleuropäische Normalzeit Thomas 
Schweikle via Gnupg-users wrote:
> On Thu, Feb 27, 2025 at 12:29 PM Ingo Klöcker <kloecker at kde.org> wrote:
> > What you did looks correct, but your keyring seems to be corrupt. I would
> > try
> > the following:
> > * Make a backup of ~/.gnupg and of everything in this folder.
> > * Export the first key (including the secret key) with
> > gpg --export-secret-keys 565931F52CE768F643389BABA9CA236BDBEC9779
> > >565931F52CE768F643389BABA9CA236BDBEC9779.gpg
> > 
> > * Delete the first key (including the secret key). This is a destructive
> > operation!
> > I hope you have created a backup.
> > gpg --delete-secret-and-public-keys FINGERPRINT_OF_YOUR_FIRST_KEY
> > * List your secret keys to verify that your first key (and all of its
> > bogus
> > copies) has been removed from your keyring. Also list the public keys.
> > gpg --list-secret-keys 565931F52CE768F643389BABA9CA236BDBEC9779
> > and
> > gpg --list-keys 565931F52CE768F643389BABA9CA236BDBEC9779
> > should both print an error "No secret key" or "No public key".
> > * Import the exported key
> > gpg --import 565931F52CE768F643389BABA9CA236BDBEC9779.gpg
> > * List your secret keys. If everything worked according to my plan you
> > should
> > now see only one "block" for your first key, i.e. you should see
> > 
> > > sec   ed25519 2020-11-18 [SC] [verfällt: 2026-12-31]
> > > 
> > >       565931F52CE768F643389BABA9CA236BDBEC9779
> > > 
> > > uid        [ ultimativ ] name <mail6>
> > > uid        [ ultimativ ] name <mail4>
> > > uid        [ ultimativ ] name <mail1>
> > > uid        [ ultimativ ] name <mail2>
> > > uid        [ ultimativ ] name <mail5>
> > > uid        [ ultimativ ] name <mail3>
> > > ssb   cv25519 2020-11-18 [E] [verfällt: 2026-12-31]
> > > 
> > >       97F6060D825C74CA8A7E49CFA0F506A815F9DDAD
> 
> This worked:
> "gpg --list-secret-keys" after importing the exported keys shows:sec
> ed25519 2020-11-18 [SC] [verfällt: 2026-12-31]
>       565931F52CE768F643389BABA9CA236BDBEC9779
> uid        [vollständig] name <mail6>
> uid        [vollständig] name <mail4>
> uid        [vollständig] name <mail1>
> uid        [vollständig] name <mail2>
> uid        [vollständig] name <mail5>
> uid        [vollständig] name <mail3>
> ssb   cv25519 2020-11-18 [E] [verfällt: 2026-12-31]
>       97F6060D825C74CA8A7E49CFA0F506A815F9DDAD
> 
> sec   brainpoolP512r1 2022-07-13 [SCA] [verfällt: 2026-12-31]
>       ACDFB1AF82CF084B948ECB5D27AE2304B4974851
> uid        [ ultimativ ] name <mail6>
> uid        [ ultimativ ] name <mail1>
> uid        [ ultimativ ] name <mail4>
> uid        [ ultimativ ] name <mail5>
> uid        [ ultimativ ] name <mail2>
> uid        [ ultimativ ] name <mail3>
> ssb   brainpoolP512r1 2022-07-13 [E] [verfällt: 2026-12-31]
>       0A5D749D75F3D847CEC42CFF737D00DCF417C669
> 
> But now one key is only trusted "vollständig" not "ultimativ".

To make your own keys trusted "ultimate" after import you have to set the 
ownertrust to ultimate. You can do this with the "trust" command of `gpg --
edit-key 565931F52CE768F643389BABA9CA236BDBEC9779`.

I assume that Kleopatra now shows the new name. Correct?

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250227/5ebeaf1e/attachment.sig>