Reference client for Bitmessage: a P2P encrypted decentralised communication protocol:
95a1afb84b
As per http://docs.python.org/2/howto/sockets.html#using-a-socket it's possible that a socket recv() call returns 0 bytes if the remote closes the connection. In that case, recv() does not obey settimeout(): it just doesn't block and returns zero bytes immediately, which in this case results in an infinite loop if the transmission was incomplete. |
||
|---|---|---|
| debian | ||
| desktop | ||
| src | ||
| .gitignore | ||
| COPYING | ||
| debian.sh | ||
| LICENSE | ||
| Makefile | ||
| osx.sh | ||
| README.md | ||
PyBitmessage
Bitmessage is a P2P communications protocol used to send encrypted messages to another person or to many subscribers. It is decentralized and trustless, meaning that you need-not inherently trust any entities like root certificate authorities. It uses strong authentication which means that the sender of a message cannot be spoofed, and it aims to hide "non-content" data, like the sender and receiver of messages, from passive eavesdroppers like those running warrantless wiretapping programs.