citizenaspirant/PyBitmessage
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity
Reference client for Bitmessage: a P2P encrypted decentralised communication protocol:
1,263 Commits 3 Branches 0 Tags 13 MiB
Python 96.6%
Shell 1.1%
RPM Spec 0.9%
C 0.6%
C++ 0.2%
Other 0.5%
03263156de
Go to file
Neil Roberts 03263156de Add a 'trustedpeer' option to keys.dat 
If this option is specified in keys.dat then Bitmessage will connect
to the host specified there instead of connecting to the hosts in the
list of known nodes. It will also stop listening for incoming
connections and the timing attack mitigation will be disabled.

The expected use case is for example where a user is running a daemon
on a dedicated machine in their local network and they occasionally
want to check for messages using a second instance of the client on
their laptop. In that case it would be much faster to catch up with
the messages by directly downloading from the dedicated machine over
the LAN. There is no need to connect to multiple peers or to do the
timing attack mitigation because the daemon is trusted.

The host is specified as hostname:port. Eg, ‘192.168.1.8:8444’.
2014-02-06 13:16:07 +00:00
archpackage Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
debian Changes for the OpenSUSE build service 2013-09-28 15:26:10 +01:00
desktop Packaging for multiple distros 2013-07-12 10:36:28 +01:00
ebuildpackage -aChanged version to 0.3.5 2013-07-29 22:19:15 +01:00
man Packaging for multiple distros 2013-07-12 10:36:28 +01:00
puppypackage Packaging updated to be architecture independent 2013-08-11 12:07:54 +01:00
rpmpackage Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
slackpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
src Add a 'trustedpeer' option to keys.dat 2014-02-06 13:16:07 +00:00
.gitignore Adding src/.settings/ to .gitignore (for Eclipse developers) 2013-06-23 21:17:34 +01:00
arch.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
configure Packaging for multiple distros 2013-07-12 10:36:28 +01:00
COPYING changed 2013 to 2014 in copyright notices 2014-01-21 22:41:48 -05:00
debian.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
ebuild.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
generate.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
INSTALL.md Fix a typo in INSTALL.md 2014-01-10 15:25:21 +02:00
LICENSE changed 2013 to 2014 in copyright notices 2014-01-21 22:41:48 -05:00
Makefile Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
osx.sh Force the right version of osx in the build script 2013-09-27 10:28:01 -04:00
puppy.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
README.md Modify readme.md 2013-10-25 19:49:18 -04:00
rpm.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00
slack.sh Increment version number to 0.4.2 2014-01-20 23:04:41 -05:00

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.

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

references