BitHorde

Something significant just landed in git-master. Encryption.

Yes, BitHorde now supports node-node encryption, and key-based cryptographic authentication. 4 different crypto-levels are supported at the moment;

• Cleartext. No encryption, just cryptographic authentication. Fastest
• XOR. Not really encryption, just obfuscation, and still very fast. Insecure, but keeps nosy people away with very little performance-impact. (>10gbit encryption-rate on the Core i7used for test)
• RC4. Long-time industry defacto-cipher. Has known weaknesses, but still considered reasonably secure. Default-cipher if nothing else specified. (~2gbit encryption-rate on test-system)
• AES 128, CTR-mode. Very secure, but the slowest of the current options. ~600mbit on the test-system.

Besides the crypto-work, there has been a plethora of bug-fixing and minor features, including:

• Fixing the file-descriptor-leakage that plagued 0.1
• Big rewrite of the asynchronous core, fixes amongst other things a possible Denial-of-Service, where one client refuses to acknowledge sent data, blocking all others.
• A simple http-based monitor-interface.
• Rudimentary Python-client-library.

All in all, if you haven't already, checking out the latest git-source might be a good idea. There are still a few items on the TODO-list for 0.2, but given time I might release an Alpha-build in a couple of weeks for impatient souls that still prefers to not build from source.