On Tue, Aug 06, 2013 at 10:09:15PM -0700, Tony A. wrote:
It’s written in Ruby and JS, and I need your help:
http://cryptosphere.org/
From there, I followed the GitHub menu link (which is inaccessible
without JavaScript for some reason that escapes me*), and from there the
libsodium link, then GitHub gave me a 404. The link URI in the README
is:
https://github.com/libsodium/libsodium
I found it here:
https://github.com/jedisct1/libsodium
Should the link be changed to that target?
I’m working on an end-to-end security model for the web, where content goes
in one end (via git), is encrypted end-to-end from the publisher’s computer
to the end user’s computer, and comes out the other side in the form of
cryptographically authenticated HTML5/JS applications.
I like the idea of a distributed, version controlled, encrypted web, and
that general idea has been on my mind a lot for the last half dozen
years. I really do think this is a worthy project, and even if I do not
find a way to contribute I hope it achieves some kind of success, and
wish you luck.
These applications are stored on a P2P grid in a decentralized manner and
fully encrypted/authenticated manner, preventing the compromise of a
hosting provider from manipulating the content. This sort of thing happened
just recently when Freedom Hosting was compromised, exposing large numbers
of users of the Tor anonymizing network to malware:
I think the biggest surprise about this was the fact so many
security-conscious privacy advocates were surprised by a major
compromise of Tor resources. One of my first thoughts when I
encountered Tor was that a surveillance society government could
probably just set up a lot of Tor nodes and correlate traffic.
Even worse, there are built-in disincentives for people to host Tor
nodes, because of the fear of being blamed for the traffic coming
through an exit node. While that does not seem to have so far been
problematic in the US, at least, we’re only a Congressional bill or
policy change away from that changing.
A better architecture is overdue. I hope this project will be a
significant step in that direction. I’ll be looking at it more, and
will share it with smart people I know who don’t follow this list.
If this sort of thing seems interesting to you, consider joining our Google
Group:
Redirecting to Google Groups
I don’t really see any other way to get involved apart from GitHub pull
requests, unfortunately. I’ll see if I get that far with this.
*: Yes, I’m aware that JavaScript is not always malicious, but it often
is, and it seems to me that we should try to cater to people who
therefore quite rationally try to avoid running JavaScript in their
browsers. This seems particularly important for a privacy-oriented tool
that is meant to appeal to security-conscious geeks.