[lca2018-chat] Keysigning BOF

[Cera Davies]

Hey there

Glad this is happening, some quick thoughts -

At the last keysigning event I went to (not at LCA), I couldn't get anyone
to sign my key because at the time the name on my photo ID did not match
the name I go by. This was despite being well known by my name in the room
as well as going by that name publicly all over the web, on the website of
my employer, etc.

I'd like to respectfully suggest that keysigners at LCA reflect for
themselves on what it means to strictly require government-issued photo ID
as proof of identity over and above all other forms of social
identification, what kind of people may be excluded on that basis, what
kind of difficulties it could create for those people, and (most
importantly) whether it pushes away some of the people who could benefit
the most from security and involvement in our community. Of course I'm not
asking people to be less serious about verification - just to reconsider
how it should be judged.

In my own view, we've created a very impoverished distributed security
platform if we tut-tut and frown when asked to sign a key without a
document of proof from the state.

On Mon., 15 Jan. 2018, 17:36 Daniel Sobey, <dns at dns.id.au> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello Everyone,
>
> I'm planning on running a keysiging bof this year.
> For those that don't know a key signing party is a session where we prove
> our identities to each other and confirm that we own that gpg key building
> a web of trust between participants.
> I have not yet booked a time but i'm thinking of running this on Thursday
> or Friday possibly during lunch or during one of the regular conference
> slots.
> Anyone can attend the session even if you don't yet have a key.
> If you are new to this feel free to chat with me during the breaks and I
> can guide you on how to get started.
>
> Please submit your key to the following website:
> http://biglumber.com/x/web?keyring=7983 before we end submission on
> Wednesday night.
> I'll try and organize to have printed copies of the keys during the day
> for you to mark off.
> If the conference organizers can help with printing (or suggesting a place
> close that can print) it would be appreciated.
>
> As we have 2 free form text fields that will be printed on the badge I
> would recommend you put either the full fingerprint or just the last 8
> numbers is usually sufficient to look up a gpg key.
> 🔏 28F8 2EA3 26A3 7748 EC41  CD28 00D4 08C4 FA9E C035
> 🔏 0xFA9EC035
>
> Before you leave home remember to bring some sort of identity as well as a
> few copies of your key printed out.
> Know that the organizer could have changed paper copy so don't trust it,
> read your fingerprint off your own printout or a device you trust.
>
> See the wiki for further details
> https://wiki.linux.conf.au/wiki/Keysigning
>
> Regards,
>
> Daniel Sobey
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJaXEngAAoJEADUCMT6nsA1SYwP/2gdpx/bO/idX+oNEW7M7WcN
> kbKIUb/YHZ0fWklitVRYwHxevZH5J8T514cj9xDv3ULR4iFY6l8RxmnwGRiYL0iU
> FY0oFw5UH3YmOZw7l0T3jo8CjPIhFc+6FBUu39E8sm/WoX17BZU2az2bM902CKNc
> JL8JQtO5AWzH98eMSjYipBzTNCDWr9L8k7vewU76lawRFDfDyVJbcNE65CFZagy/
> Ww9UTNNnzlFhbJkOPfPqzLkyu4LwxvXArW1GTQP0KMoSAf32bB8ZUbRdqyTNi2H8
> n/IQJu6jnUwddTVEq5VQWDzQlw2uA+sR+f1CFPw13wgsysORDzStrKGci2Flv0+7
> P9jXUfGsBn/9MbVvpwdJCxoZg0TCTD16Br84/kha/LPsZ8+T/rjPSQoT36nzz8rb
> 7zw+9y/yQpg0TdXq8uu89jD6NlOXqzOFXrNUqXd4gjXiGxA2bGyIiosdR8D1Os43
> r8YDzcDAChjRIZgwJxOYQGthSvDEaxA2hUpCo3g1T+zuMnlVNMQ2Gpr0i1f/P4P2
> dSQ2hHbfAGgvWeDWuXQal/y4A2u18CDu2uEwdfQaBqkWwohatGGS1CutK+/2hFn1
> nV7h4eFgqIw8vPZXmcXtLDoCKnzhRzRYkcvcuessP6chawkTrEkI45ACZqPbr2gx
> oj4S+MkYMtii5lS2LFQ3
> =iy4x
> -----END PGP SIGNATURE-----
> --
> lca2018-chat mailing list
> lca2018-chat at lists.lca2018.linux.org.au
> http://lists.lca2018.linux.org.au/mailman/listinfo/lca2018-chat
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lca2018.linux.org.au/pipermail/lca2018-chat/attachments/20180115/32f7fa31/attachment.html>