Presented by:

Johannes Segitz

from SUSE

Security engineer at SUSE.

Since my time as a teenager in the 90s I was interested in IT security. After visiting my first CCC congress I got hooked and never looked back. In the last ten years I am a member of the SUSE security team and try to make open source software more secure.

No video of the event yet, sorry!

Sign GPG keys (and potentially verify other ways of communication).

If you're a long time member you might remember that we did this a while ago already. This time we'll switch up the mode a bit because some parts proved to be slightly problematic last time. We'll do it differently this time because having a central list caused issues with mail clients wrangling the list, which then caused confusion when verifying the hashes. The method we uses will have the drawback that we might run out of snippets or will have to throw some out, but lets see how this works out.

What to bring: - As said there will be no central list of participant. You are expected to print the information about your key to hand out to people willing to sign. You can you use gpg --keyid-format long --fingerprint $KEYID. For me this yields:

        gpg --keyid-format long --fingerprint EE166BCEAD56E034BFB33ADD7BF729D5E7C81FA0
        pub   rsa4096/7BF729D5E7C81FA0 2014-04-02 [SC]
              Key fingerprint = EE16 6BCE AD56 E034 BFB3  3ADD 7BF7 29D5 E7C8 1FA0
        uid                 [ unknown] Johannes Segitz <jsegitz@suse.com>
        uid                 [ unknown] Johannes Segitz <jsegitz@suse.de>
        uid                 [ unknown] Johannes Segitz <jsegitz@novell.com>
        sub   rsa4096/BC27DD9D2CC4FD66 2015-01-13 [S]
        sub   rsa4096/11A31E5DB3AFF881 2014-04-02 [E]

Fill a page with multiple copies of this with a bit of space in between. Then cut them up into snippets to hand out. Based on previous experience 30 copies should be enough.

Please note on the snippet if you do NOT want the signer to upload your key. Please respect the choice of the person and then send the mail to the person and not to a keyserver.

  • Something to collect the snippets of people you want to sign (your wallet will probably do, but you might not want to have 30 paper snippets in there for the rest of the conference)
  • Bring (if possible multiple) identity documents. Especially if you have old documents or some that are hard to identify for e.g. a European please bring multiple so that your chances increase that they're accepted.

People have different requirements for signing keys. Please respect those. If you pressure someone to sign your key you will be asked to leave.

We will form two lines, so we have pairs of people that can verify the identities of each other based on their own requirements and then move to the next person. I'll explain it at the event itself.

Feel free to also exchange other keys, e.g. Signal.

Please remember to actually sign the keys afterwards. You can do it manually or use a tool like caff to make it easier for you. You are encouraged to diligently check the information that was provided to you, but in the end you can of course sign whatever you like.

Date:
2025 June 27 - 15:15
Duration:
1 h
Room:
Seminar Room 1
Language:
Track:
Community
Difficulty:
Easy

Happening at the same time:

  1. SUSEID: Open by design, sovereign by choice.
  2. Start Time:
    2025 June 27 15:15

    Room:
    Saal

  3. Who broke the build? — Using Kuttl to improve E2E testing and release faster
  4. Start Time:
    2025 June 27 15:15

    Room:
    Gallerie

  5. Beyond GitOps: Building Intelligent Drift Detection and Auto-Remediation in ArgoCD
  6. Start Time:
    2025 June 27 15:45

    Room:
    Gallerie

  7. Building openSUSE Mirror(s) in Mauritius
  8. Start Time:
    2025 June 27 16:00

    Room:
    Saal