OK, fair point about bitcoin. But other than that, I really feel like the cypherpunk types have been fairly invisible lately. Maybe it's just that there was a certain period of time, back in the /. heyday, when discussions of cryptography, surveillance, data-havens, etc. were at a peak, and now they've leveled off. But in any case, I would argue that we (still) need an active and efficient cypherpunk community to promote technological freedom.
The problem with crypto-currency isn't the "crypto", it's the "currency". I think that same phenomena is the culprit for most "cyperpunk-related" discussions.
10 years ago I'd have said that I was really hoping for the "Star Trek" future, but that if I was forced to bet, I'd bet on a "BladeRunner" future being way more likely.
Now I'm old, and I think if I was forced to bet, "Brazil" is a more likely model (the movie, not the country).
But I don't want to sound like I'm dismissing the value of a healthy "cypherpunk" community. I think you can look at a lot of things that came out of the original community and see value there.
http://img197.imageshack.us/img197/3199/inforn.jpg
Another image I can't locate showed how we used to see the future, from a 1980's standpoint (think: Jetsons), and how we see it today (think: "The Road", "Book of Eli" or "I am Legend").
I think you must mean a 1960s standpoint. 1980s gave us Bladerunner and Terminator.
The movie The Terminator was at probably partially inspired by the short story Second Variety, written by Philip K Dick in 1953.
I'm afraid you may be right. But I still hold out some hope that we can do better than that.
Crypto solutions lead to technical complexity which in turn raises the barrier to entry and makes it difficult for outsiders to join in. It's some kind of isolationist community. Who uses Diaspora, anyway? Anyone? Doesn't it offer precisely what everyone's allegedly in need of?
check out the bitcoin forums. Honestly, I think the op has been hiding under a rock for the past couple years. Bitcoin and tor are great examples, but there are plenty of other disruptive projects out there, like loom, open-transactions, ripple. Crypto-anarchists didn't go away, they got to work creating practical applications that can change people's lives, and not just for the geeks.
You may find some interested people in UK Crypto (but obviously I'm not suggestion you spam their list). (http://www.chiark.greenend.org.uk/mailman/listinfo/ukcrypto)
> This group is comprised of people with a professional interest in the formulation and content of UK government policy on the provision, use and control of encryption products and services in the UK. It was formed in response to the 1996 announcement of UK policy on the provision of encryption services on telecommunications networks.
> The mailing list is unmoderated, but only subscribed members can post. Please try and restrict postings to UK Encryption law and try not to stray onto general cryptology topics.
I'm not a cryptographer by any means, but my first thought when reading that is can we make non-terrible in-browser javascript crypto?
(Copied from http://news.ycombinator.com/item?id=3872007)
;)
Which is that it sounds rather complicated (which makes my security-sense go off, but certainly isn't a fatal indictment) and that I'd really need to either do an active evaluation of the system or get several reassurrances that someone else decent (ideally someone much smarter than me) did and it checked out before I'd be remotely comfortable using it or recommending it.
Data-dependent timings could conceivably allow a bad guy to deduce something about the data being sent.
Note that this is all highly speculative; I'm not convinced it's truly impossible, but it's one of those attack scenarios where "put a gun to the sysadmin's head" begins to look like a pleasant and trouble-free option...
What? How does the machine -the machine not connected to the network- get the results off Amazon?
Say, a signed webapp manifest, listing all files that are supposed to be used in that context and their hashes. On first execution, the associated key is stored, maybe compared with third party knowledge about the site (not tampered with) and key (known not-trustworthy).
After that, you know when someone else than the maintainer tampered with the code.
With that you're down to trusting the maintainer. Which makes it as good as any other code distribution scheme.
Is it worse than nothing, or just bad?
What alternatives would you suggest?
Some people are of the opinion that the usefulness of being able to do crypto in people's browsers outweighs exactly how inhospitable it is. I don't share this opinion.
In most circumstances, something bad might be preferable to nothing at all. I think crypto is one of the rare exceptions where "bad" is actually worse than none.
My alternative suggestions are conservative: PGP and TLS
These suggestions aren't particularly exciting, however, so people keep looking for other, newer, ones.
I'm actually in the small minority of security people who don't think it's feasible to discourage people from trying to muck around with crypto. It's like sitting a kid in front of a television,handing them a video game controller, and then telling them not to play video games.
Crypto is an attractive nuisance. It also seems like it answers a lot of our problems (it actually answers far less than we think, and just creates new ones in their place), so people naturally are inclined to experiment with it.
So I hope someday to be wrong about crypto in the browser, because it'd be great. But right now, it's sort of like trying to fancy up a glory hole.
There's the remaining problem of key management, though for many people, browser-based password managers are a reasonable mechanism.
PGP/GPG and TLS still provide key management issues (with several notable registrar incidents in the past year). And even if you're, say, parking a public key on a site to autoencrypt material sent there (assuming it's not encrypted prior to upload), there's the question of how you're going to interact with encrypted data on that site. I see three basic options: server-side encrypt/decrypt, browser-based, or client-side non-browser utilities. In the latter case, you now have a wide range of environments (Windows variants, Mac, Linux, etc.) to support.
Not saying it can't happen, but good crypto is hard.
Even the pros (PGP) ended up using a server-based solution which had both public and private keys on it as their solution to the key-management problem.
Something like this is the ONLY way I can see crypto in the browser gain any credibility and traction. Crypto in the JS is not only potentially the easiest attack vector, it's also abhorrently slow. With native browser constructs we get access to safe(r) implementations which cannot be DOM manipulated, MITMed or simply replaced at load time. We get access to speed boosts by running natively and on hardware supporting AESNI it can zoom.
I suppose we all see what we want to see.
I do wish that there existed a forum for some of the discussions that used to actually happen on the cypherpunks list (even though it would frequently derail into arguments about assasination markets, and paranoid conspiracy theories).