SHA2017 Wiki - User contributions [en]

Harbour/CardBoardBoatRace

2017-08-06T17:56:25Z

Malan: /* Teams */

Day: 2017-08-07
Start time: 12:00
Location: Harbour

== RULES FOR ALL TEAMS ==
1. Teams consist of a minimum of 2 and a maximum of 4 people 
Two people in the crew will have to row (NO ENGINES allowed!) the boat from the harbour dock,race to the judges boat and ring the bell 
U can use up to 4 people to construct your boat. 
2. All teams will have 3 hours to construct their boat, after 3 hours have passed we will inspect the boats to check the materials used. 
No preconstructed boats allowed, boat has to be build at the race from raw materials.
3. A race consists of 25 meters 
4. The race must begin and end with the two-person crew intact. Any use of lane
lines, and pushing or pulling your boat will result in a disqualification. 
5. All participants’ arms and legs must be in the boat at all times. 
Body parts may not be used to propel the boat, please use paddles. 
6. The winner will be the team that rings the bell and has the fastest time 
7. Your boat must be free of sharp edges, pointy objects or anything else that could
cause injuries 
8. The judges have the final say about the rules 

=== Materials: ===
Only cardboard and ducktape may be used to construct the boat.
Only [https://en.wikipedia.org/wiki/Corrugated_fiberboard corrugated cardboard] will be allowed. The maximum allowable thickness of corrugated cardboard is one-half inch.
You may NOT use any other objects to contribute to the structural rigidity or the craft's flotation ability.
We will provider materials, ducktape and cardboard
Only seams and joints may be taped, not the whole boat.

==== Teams ====
Please sign up here:
{| class="wikitable"
|-
! Teamname !! Village !! Email
|-
| Moby Derp || /dev/derp || sha2017@heiko-reese.de
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

Village:/dev/derp

2017-07-22T17:05:24Z

Malan:

{{Village
|Has name=/dev/derp
|Has contact=mailto:sha2017@heiko-reese.de
+49 1520 1601774
|Has description=Some slightly disorganized nerds, feel free to join us :-)
|Part of=Cluster:Snowden
|Has village tag=security, open source, electronics, beekeeping, woodworking, hanging out, friendly people
|Provides session location=No
|Has Field=Hopper Field
|Has orga contact=sha2017@heiko-reese.de
|On site orga contact=DECT: 7772
|Village frab=No
|Village content space=No
|Village citizen count=4
|Village Needs power=Smaller Village (up to 2x 230V/16A CEE/Schuko)
|Village size needed=50
|Village hacktents num=0
|Village brings big stuff=No
|Village Special Vehicle=No
}}

User:Malan

2017-07-17T14:38:52Z

Malan:

{{User
|Name=malan
|Village=Village:/dev/derp
|Arrival=2017/08/02 20:00
|BuildupVehicle=No
|Departure=2017/08/09 09:00
}}

User:Malan

2017-07-17T14:37:50Z

Malan: Created page with "{{User |Name=malan |Arrival=2017/08/02 20:00 |BuildupVehicle=No |Departure=2017/08/09 09:00 }}"

{{User
|Name=malan
|Arrival=2017/08/02 20:00
|BuildupVehicle=No
|Departure=2017/08/09 09:00
}}

Keysigning-Party

2017-07-10T08:42:55Z

Malan: /* Participants */

The Keysigning party at SHA2017 will be a classic Sassaman-Efficient based keysigning party with some SHAdaptions, provided that at least 20 people show up. If not, we'll fall back to exchanging keyslips.

The SHAdaptions mainly consist of:
* Replacing the checksums with a SHA256 one
* Adding badges for easily verifying keys visually, and showing your signing policy
For a complete protocol, please see below at the Protocol section

Additionally, everyone is encouraged to bring keyslips anyway, so people who have not been able to prepare, can sign and have their key signed, but in a less efficient manner.

== What? ==
At a keysigning party, we sign eachothers PGP/GPG keys, to improve the web of trust. Also, please read https://wiki.debian.org/Keysigning

== Participants ==

{| class="wikitable"
|-
! Name !! KeyID (0xlong) !! Sent key to keysigning@sha2017.org
|-
| [[User:WebSpider]] || 0x37A169A51AC33EA2 || Yes
|-
| [[User:Piet0r]] || 0xD43B003FB3684634 || ACK
|-
| [[User:Atluxity]] || 0xA87A3C11E1F73953 || Not yet
|-
| [[User:-hp197]] || 0xAC082B028971394C || yez
|-
| [[User:sprawl]] || 0x1FDD301FB636D58B 0xAE8DA3E6A86CD3C0 || WIP…
|-
| [[User:malan]] || 0x84e614e61e13dac3 || Not yet
|-
| You || 0x1234567890abcdef || ?
|-
| Him || 0xabcdef0123456789 || ?
|}

== Protocol ==
The SHAdapted Sassaman-Efficient protocol goes as follows:

'''Before The Event'''
# All participants email their public key to the keysigning coordinator, diligently reading e-mails addressed to keysigning@sha2017.org
# The coordinator compiles all the submitted keys into an event keyring.
# The coordinator generates a text file containing a list of all keys and their fingerprints, and calculates the SHA256 checksum of the list.
# The coordinator publishes the text file either by emailing it to all participants or making it accessible on a website along with all the checksums.
# Participants download the text file and calculate the checksums of the list, and check them against the checksums provided by the coordinator. If the checksums match it shows that the participant has an identical and unmodified copy of the key list.
# Participants print out a hard copy of the key list and check the fingerprint of their own key included in the list is correct.

'''At The Event'''
# All participants bring along their own hard copy of the key list which they printed themselves. Participants should only trust the key list they printed themselves from the file with verified checksums. This ensures each participant is working from a list they know has not been tampered with.
# The event organiser reads out the checksums or displays them on a projector for all participants to compare with their own.
# Each participant in turn makes a statement that their fingerprint as included in the list is correct. This can be as simple as saying 'key XXXXX is correct'. There is no need to read the fingerprint aloud: since the lists have been checksummed, the fingerprint that appears on all lists must be the same. Participants put a tick on their copy of the list next to each key that is stated by the owner to be correct, and put a tick in their keysigning-badge.
# Once all participants have stated whether their fingerprint is correct, everyone forms a long line in the same order as their keys appear in the list. The head of the line then folds back on itself and the participants moving back along the line inspect the ID of each participant standing still. The ID requirement is generally 2 forms of government-issued photo ID, but individual participants may enforce their own requirements as appropriate. A second tick is placed next to the list entry for which sufficient ID has been sighted.
# Once all participants have presented their ID, key lists are to be stored away in a safe place by each participant to prevent tampering with the annotated list.

'''After The Event'''
# Participants retrieve the public keys of all keysigning participants either by fetching individual keys from public keyservers or by importing an event keyring if one has been created by the event coordinator.
# Participants work through their annotated key list, checking the fingerprint of each key against the printed list and signing keys that match and are ticked for valid ID and the owner stating the fingerprint is correct.
# Participants either upload each public key they sign to a public keyserver, or email it directly to the key owner. Some key owners prefer not to have keys sent to public keyservers so in general it is courteous to email the key directly to the owner.
# Signatures sent to each participant by other participants are imported into their local keyring.