Skip to content

Instantly share code, notes, and snippets.

View nicolaslegland's full-sized avatar

Nicolas Le Gland nicolaslegland

View GitHub Profile
@jwilkins
jwilkins / gist:c298e419b6483aadd181
Created February 13, 2015 23:00
public pgp key ids == 0x00000000
gpg --keyserver pgp.mit.edu --recv-keys 00000000
gpg: requesting key 00000000 from hkp server pgp.mit.edu
gpg: key 00000000: public key "Thorsten Rapp <Thorsten@giblicht.de>" imported
gpg: key 00000000: public key "Julian Blake Kongslie (Born 1985-Mar-03 in Portland, OR, USA)" imported
gpg: key 00000000: public key "Nicolas Le Gland <nicolas@legland.fr>" imported
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 3 signed: 1 trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: depth: 1 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2017-12-21
gpg: Total number processed: 3
@dominictarr
dominictarr / TahoeLAFS.md
Last active April 26, 2023 04:28
Writing out part of the Tahoe LAFS paper in my own words to check my understanding.

Tahoe LAFS

Tahoe LAFS is a distributed file system with an interesting permissions model. (whitepaper) Both Immutable and Mutable files are supported (Mutable is the most complex and interesting) There are three levels of permissions, Write, Read, and Verify. Each permission is granted by giving a user a special key called a "capability". If you have the Write capability you can update the file, if you have the Read capability you can retrieve the plain text, but if you only have the Verify capability you can only validate the file integrity, but not read the contents.

The lower level capabilities are generated deterministically from the higher level capabilites.