Conversation:
Notices
-
Dear @CryptoParty, we should have a !StatusNet server for all our CryptoParty<location> accounts. Let's be available on the libre side!
-
How ironic. "Encrypt all things", yet #statusnet doesn't support https.
-
@zoowar your help in setting up a nice HTTPS-supporting StatusNet instance for @CryptoParty would be invaluable. :)
-
You should be looking for user-agent to user-agent encryption. In this case the "social stack" would not matter.
-
@zoowar well, you can't really do that well in pure JS bit.ly/IUAT6c so until browser have a nice crypto API, not really doable.
-
It can be done. I've done it myself with http://ur1.ca/cb3u2
-
The conclusions in the article are derivative of an assumption that ssl/tsl is "expensive and complicated". A fedweb mitigates this...
-
.@zoowar nope. the assumption is that JavaScript is a bad platform for crypto, because of a number of attacks possible.
-
@zoowar it's not that it's impossible to write a working JS crypto lib. it's impossible to write a safe one, and distribute it safely.
-
.@zoowar I would suggest reading the article more closely, esp. the "safe delivery chicken-and-egg problem" part.