[Noisebridge-discuss] Cypherpunks 2.0

[Leif Ryge]

On Sun, Oct 13, 2013 at 04:14:20PM -0700, Andy Isaacson wrote:
> On Sun, Oct 13, 2013 at 10:40:39AM -0700, Andy Isaacson wrote:
> > I gave a talk about the new energy in the Cypherpunks movement at
> > Dorkbot last night.
> > 
> > My slides are up at
> > http://adi.is/s/cpunk20
> > 
> > and hopefully the livestream got archived somewhere (I haven't seen a
> > copy yet).
> 
> Here's video, perhaps a cleaner audio will show up:
> https://twitter.com/eqe/status/389518159125827584
> 
> (If anybody feels like ripping the video from livestream and giving me a
> copy I'd deeply appreciate it.)
> 
> -andy

Excellent talk, thanks for doing it!

You can download the flv files (which you can play with mplayer or VLC) here:
http://tcdn.ustream.tv/video/39791560
http://tcdn.ustream.tv/video/39791773

Btw, newer versions of youtube-dl (eg not the version in debian) will download
video from ustream and numerous other sites. I recommend using virtualenv+pip
to semi-safely (relying upon certificate authorities) install python software
such as youtube-dl into self-contained environments (no root required!). Here
are some instructions which show how to create a new python environment called
"youtube-dl-env" and securely(tm) install youtube-dl there:

wget https://pypi.python.org/packages/source/v/virtualenv/virtualenv-1.10.1.tar.gz &&
[ "$(sha1sum virtualenv-1.10.1.tar.gz)"                                == \
"0c441553f97a1ed68bb2032c9ab65e6c3bc38e24  virtualenv-1.10.1.tar.gz" ] &&
tar xf virtualenv-1.10.1.tar.gz                                        &&
./virtualenv-1.10.1/virtualenv.py ./youtube-dl-env                     &&
source ./youtube-dl-env/bin/activate                                   &&
pip install --no-allow-external --no-allow-insecure youtube-dl

Running the above commands should put the youtube-dl command in your PATH in
your current shell; to use it again later in a new shell just source the
activate script again. (Some people prefer to create a single virtualenv for
all of their python software and then source the activate command from their
bashrc.)

~leif

ps: In the talk you say you thought Tahoe-LAFS uses TLS but weren't certain.
FYI it does, via the foolscap library, which provides self-authenticating URLs
called FURLs which (similarly to Tor's onion addresses) contain a hash of the
TLS public key so that there is no need to rely on certificate authorities.
The TLS is only for authenticating storage servers and providing
confidentiality of the metadata (which pieces of ciphertext are being read and
written) - it is not involved in providing confidentiality of the data itself,
as the unencrypted data is never sent to storage servers.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.noisebridge.net/pipermail/noisebridge-discuss/attachments/20131014/13c81eff/attachment-0003.sig>