Reference client for Bitmessage: a P2P encrypted decentralised communication protocol
Go to file
Gregor Robinson 9460712a59 File permission special case for NTFS-3g on POSIX.
Fix issue #347, "*SensitiveFilePermissions fails on ntfs-3g mounted filesystems".
2013-08-05 22:06:46 +02:00
archpackage Changed version to 0.3.5 2013-07-29 22:22:17 +01:00
debian Changed version to 0.3.5 2013-07-29 22:22:17 +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 -aChanged version to 0.3.5 2013-07-29 22:19:15 +01:00
rpmpackage Changed version to 0.3.5 2013-07-29 22:22:17 +01:00
slackpackage Packaging for multiple distros 2013-07-12 10:36:28 +01:00
src File permission special case for NTFS-3g on POSIX. 2013-08-05 22:06:46 +02:00
.gitignore Adding src/.settings/ to .gitignore (for Eclipse developers) 2013-06-23 21:17:34 +01:00
arch.sh Changed version to 0.3.5 2013-07-29 22:22:17 +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 Changed version to 0.3.5 2013-07-29 22:22:17 +01:00
ebuild.sh Changed version to 0.3.5 2013-07-29 22:22:17 +01:00
generate.sh made generate.sh readable, and added icons and shortcuts to the menubar 2013-08-01 00:26:46 -05:00
INSTALL.md Changed INSTALL to markdown 2013-08-01 14:22:53 -05: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 Changed version to 0.3.5 2013-07-29 22:22:17 +01:00
README.md Debian packaging 2013-04-01 20:23:32 +01:00
rpm.sh Changed version to 0.3.5 2013-07-29 22:22:17 +01:00
slack.sh Changed version to 0.3.5 2013-07-29 22:22:17 +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