Skip to main content

Key signing party at fosdem 2024

I'm organizing a GnuPG key signing party in order to bolster our web of trust, since there is no official ksp this year.

I have organized a few in the past using tools like biglumber (website is gone, if someone know of a replacement or where the source code of site is, I might end up running one again) and others tools. I've also run once the KSP at FOSDEM and helped running it a few other times. 

 

=== Details below ===

When, Where 

We'll meet in front of the infodesk stand in building K around 12:00 Sunday Feb 4th 2024. I'll have a sing of some sort with KSP and or Key Signing Party. Once enough participants show up we will move outside to proceed with the party.

What to Bring

Warm cloths as the party will happen outside this year, like in the good old days. I hope it won't rain, but it might.

Piece of papers with your fingerprint written on them. Each piece should look like below:

 $ gpg --fingerprint 34246C61F792FBCC1F23BFF296BD1F38FEA32B4D
pub   ed25519 2022-03-01 [SC]
      3424 6C61 F792 FBCC 1F23  BFF2 96BD 1F38 FEA3 2B4D
uid           [ultimate] Ludovic Hirlimann (ECC key) <ludovic@hirlimann.net>
sub   cv25519 2022-03-01 [E]
You can have multiple keys on the piece of paper.  Bring at least fifty (50) of these so you have enough. A good KP a FOSDEM is above a hundred participant with a hundred showing up. I don't expect these numbers, but be prepared to hand over a lot of these pieces of papers

Time, the KSP take at least one hour to two hours depending on the number of people showing up.

Some sort of ID.

A mask, even if outside, it's better to wear one than not - when there are some many people coming from all over Europe.

What not to bring

A laptop or a smartphone. We'll use paper exclusively.

Anger, impatience - ksp are parties so it should be fun :-)

How we'll proceed

We'll form a line. Split the line in two and make the last person in the line face the first, the second to last the second etc. Once key exchanged and ID verified, we'll step one step to the right. The now first in line will face the then second to last, etc. And we loop on that until the initial first in line exchanges with the initial second to last.
Sounds complicated? It's not you'll see when in it.

Home Work

Once back home, make sure your machine can send emails (see https://unix.stackexchange.com/questions/159608/how-to-configure-postfix-to-send-mail-to-external-smtp-server for instance). Install Caff  or Pius. Do that quickly, as it's fresh in your mind.

Edit: I just printed mini cards from moo with my fingerprint on it.
Labels:

Comments

Post a Comment

Popular posts from this blog

Firefox OS's story from a mozilla insider not working on the project

  I clearly remember, but can't date it. I was working for Mozilla messaging at the time ( momo ), being the QA lead for Thunderbird. It was at the end of one of the Mozilla All-hands, maybe in 2011 or 2012. At one of the ending keynotes, we were introduced to Boot 2 Gecko. A hack that would let US - Mozilla own the platform to run a mobile browser on. At the time, the iPhone was going strong and Google was trying to catch up with Android. MeeGo had been in development at Nokia for a while but was going nowhere even when Intel tried to help. Blackberry was slowly starting to die. In the Silicon Valley everything was about mobile, mobile, mobile and the emerging South Easter Asian market, where people would skip computers and use smartphones to join the internet revolution. We were struggling with Chrome and the massive investment by Google to take market share. Our Firefox port on Android was having loads of issues. We were denied by Apple's policies to be present on iPhones....
3 comments
Read more

Are mozilla's fork any good?

To answer that question, we first need to understand how complex, writing or maintaining a web browser is.  A "modern" web browser is : a network stack, and html+[1] parser,  and image+[2] decoder, a javascript[3] interpreter compiler, a User's interface, integration with the underlying OS[4], And all the other things I'm currently forgetting.   Of course, all the above point are interacting with one another in different ways. In order for "the web" to work, standards are developed and then implemented in the different browsers, rendering engines. In order to "make" the browser, you need engineers to write and maintain the code, which is probably around 30 Million lines of code[5] for Firefox. Once the code is written, it needs to be compiled [6] and tested [6]. This requires machines that run the operating system the browser ships to (As of this day, mozilla officially ships on Linux, Microslop Windows and MacOS X - community builds for *BSD do ex...
Post a Comment
Read more