Reference client for Bitmessage: a P2P encrypted decentralised communication protocol
Go to file
nobody d606bb1333 Fix: Distinguish peers by both IP address and port.
Until now many parts of the code assumed that IP addresses are
unique for peers. However, more than one Bitmessage instance might
be running with a given IP address due to multi-user systems or
firewalls.
2013-07-30 22:23:18 +02:00
archpackage Improving the Ebuild 2013-07-23 16:04:44 +01:00
debian Merge pull request #328 from fuzzgun/master 2013-07-23 14:02:16 -07:00
desktop Packaging for multiple distros 2013-07-12 10:36:28 +01:00
ebuildpackage Fixed missing repository 2013-07-23 21:31:55 +01:00
man Packaging for multiple distros 2013-07-12 10:36:28 +01:00
puppypackage Fixed missing repository 2013-07-23 21:31:55 +01:00
rpmpackage Improving the Ebuild 2013-07-23 16:04:44 +01:00
slackpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
src Fix: Distinguish peers by both IP address and port. 2013-07-30 22:23:18 +02:00
.gitignore Adding src/.settings/ to .gitignore (for Eclipse developers) 2013-06-23 21:17:34 +01:00
arch.sh Some Arch dependencies 2013-07-12 14:03:11 +01:00
configure Packaging for multiple distros 2013-07-12 10:36:28 +01:00
COPYING Debian packaging 2013-04-01 20:23:32 +01:00
debian.sh manual merge 2013-07-14 16:35:16 -04:00
ebuild.sh Packaging for multiple distros 2013-07-12 10:36:28 +01:00
generate.sh Fixed missing repository 2013-07-23 21:31:55 +01:00
LICENSE Debian packaging 2013-04-01 20:23:32 +01:00
Makefile Increment version number to 0.3.5 2013-07-28 16:43:00 -04:00
osx.sh Generated py for search. 2013-07-12 02:01:33 -04:00
puppy.sh Improving the Ebuild 2013-07-23 16:04:44 +01:00
README.md Debian packaging 2013-04-01 20:23:32 +01:00
rpm.sh Packaging for multiple distros 2013-07-12 10:36:28 +01:00
slack.sh Improving the Ebuild 2013-07-23 16:04:44 +01:00

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.

references