Peter Surda
2f9501fa1a
Attackers injected node addresses with port 0 into the network. Port 0 is unusable on many OSes and can't be listened on. PyBitmessage won't accept nodes that have port 0 anymore. |
||
|---|---|---|
| archpackage | ||
| debian | ||
| desktop | ||
| man | ||
| puppypackage | ||
| rpmpackage | ||
| slackpackage | ||
| src | ||
| .gitignore | ||
| arch.sh | ||
| configure | ||
| COPYING | ||
| debian.sh | ||
| ebuild.sh | ||
| generate.sh | ||
| INSTALL.md | ||
| LICENSE | ||
| Makefile | ||
| osx.sh | ||
| puppy.sh | ||
| README.md | ||
| rpm.sh | ||
| slack.sh | ||
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.
Development
Bitmessage is a collaborative project. You are welcome to submit pull requests although if you plan to put a non-trivial amount of work into coding new features, it is recommended that you first solicit feedback on the DevTalk pseudo-mailing list: BM-2D9QKN4teYRvoq2fyzpiftPh9WP9qggtzh
This fork
The purpose of this fork is to add features for server deployment for a bitmessage/email gateway. It contains merged support for OpenCL PoW and a couple of new/modified API calls.