Skip to content

Missing section for adding uids #445

Description

@angelacastaneda

Love this guide and having so much value out of my yubikey.

I followed it for myself back in fall when things weren't so automated, and I just helped my friend set up his key today, and while it is nice to be able to copy-paste more commands, one thing that was very useful with the guide then was a pit stop during key generation to run adduid for more emails and names.

I helped him add the extra email out of script when editing the Certify key, but he would not have figured it out without me being there to help.

Activity

  1. drduh commented on Jun 10, 2024

    @drduh
    Owner

    Thank you for the feedback @angelacastaneda

    My impression is the use of additional identities is quite rare for the purposes of this guide. Would you mind sharing more about your context/use case? And how we could make this pit stop more prominent and helpful for users such as your friend?

  2. angelacastaneda commented on Jun 10, 2024

    @angelacastaneda
    Author

    I'm something of a multicultural guy, so I have different email addresses depending on the language. I also have a leet, hacker email too that I use for git commits, mailing lists, open source stuff in general to separate from the normal, personal email address.

    see key here -> FB38 5581 F9E8 58F3 99DE 8DFE 099F 4FAF E6D2 E988

    That last use-case was the one that was relevant to my friend and I think a lot of people that wanna do the effort of encrypting with a yubikey but don't wanna have to buy a separate one for another email they might want to use.

  3. forbytten commented on Nov 21, 2024

    @forbytten
    Contributor

    I also have a use case for multiple uids: I want to use the same key for both GitHub and GitLab and potentially more repos. Both GitHub and GitLab allow use of a private email address, specific to each provider. From my brief testing, a key with both uids will allow commits to be marked as verified by both providers. I don't know how common this use case is but I would imagine it's not that rare, or at least it shouldn't be, either now or in the future ;) albeit, this use case probably only applies to users who have all the following requirements:

    1. Signed/verified commits
    2. Need to use both GitHub and GitLab and/or other repositories
    3. Don't want a real email exposed in their key and want to take advantage of the repository providers' anonymizing functionality
    4. Want a single key

    I have raised pull request 464 with a suggested change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions