Akademy/2019/GPGKeys: Difference between revisions
No edit summary |
No edit summary |
||
| Line 55: | Line 55: | ||
| 8FE4 D32F 7061 EA9C 8232 07AE 01C6 CE2B FF04 1C12 | | 8FE4 D32F 7061 EA9C 8232 07AE 01C6 CE2B FF04 1C12 | ||
| ☐ | | ☐ | ||
|- | |- | ||
| ☐ | | ☐ | ||
| Line 67: | Line 66: | ||
| ☐ | | ☐ | ||
|- | |- | ||
| ☐ | |||
| Filipe Saraiva <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> | |||
| E759 F27D 8A03 7BF8 65F7 10ED C820 2AF1 0552 7004 | |||
| ☐ | |||
|- | |- | ||
| ☐ | | ☐ | ||
Revision as of 07:23, 10 September 2019
Why
GPG signing is our preferred method of establishing authenticity of anything ranging from mails to release tarballs/tags. To make this easy to verify and trustworthy it is useful to have yourself wired into the KDE web of trust (i.e. get your key signed by other KDE contributors).
If you are release manager of a project or a distribution packager it is highly recommended that you attend this BoF to get yourself wired into the release web of trust which makes tarball signature verification a lot easier.
There's lots of good guides on GPG in general and key signing in specific out on the internet, it is recommended you read up on this a bit. We'll only explain the process in broad strokes at the BoF. If you have questions you can send a mail to [email protected]
How This Works - READ THIS!
Add the name and email address of your key as well as the fingerprint below. Tuesday at 12:00 someone is going to do a print out for all listed attendants. If you would like to do your own print out, please send a mail to [email protected]. Please make sure that you send a mail if you add yourself after the deadline. It may be too late or not, but I definitely want to know.
To get your key fingerprint, you'll want to run gpg or gpg2 with the --fingerprint argument and your name or short ID. e.g.gpg2 --fingerprint Sitter
For the BoF Please:
- Bring an ID card or preferably a passport so we can verify you are who you claim to be
- Write down your fingerprint or print it out so you can verify your own fingerprint
Failing to do either will slow down everyone! Help us out and be prepared :)
| Key OK | Name <EMail> | Fingerpint | ID OK |
|---|---|---|---|
| ☐ | Harald Sitter <[email protected]> | CB93 8752 1E1E E012 7DA8 0484 3FDB B550 84CC 5D84 | ☐ |
| ☐ | Stefan Derkits <[email protected]> | 7786 B507 E1EF 5B9E 89BC B2FE 9591 D7BA 4228 0CA8 | ☐ |
| ☐ | Timothée Giet <[email protected]> | D2FA AB62 1F61 8D42 685B 427B 63D7 264C 0568 7D7E | ☐ |
| ☐ | Jonathan Riddell <[email protected]> | 2D1D 5B05 8835 7787 DE9E E225 EC94 D18F 7F05 997E | ☐ |
| ☐ | Ivan Čukić <[email protected]> | 8FE4 D32F 7061 EA9C 8232 07AE 01C6 CE2B FF04 1C12 | ☐ |
| ☐ | Sandro Knauß <[email protected], [email protected], [email protected]> | 39EC 11A0 2016 B729 2649 1A06 E3AD B008 5060 5636 | ☐ |
| ☐ | Florian Müller <[email protected]> | 5732 9DC4 268D B055 4E47 84D3 CE74 5A77 C2E1 B129 | ☐ |
| ☐ | Filipe Saraiva <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> | E759 F27D 8A03 7BF8 65F7 10ED C820 2AF1 0552 7004 | ☐ |
| ☐ | Your Name <[email protected]> | 1234 1234 1234 FINGER PRINT | ☐ |