Bitmessage

Bitmessage is a peer-to-peer communications protocol based on the Bitcoin crypto-currency 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. If Bitmessage is completely new to you, you may wish to start by reading the whitepaper.

Installation

Installation is very simple on modern GNU/Linux based operating systems. You may need to install python-qt4 first, then simply git clone it as shown here. And create a desktop launcher for it as shown in our GNOME article.

Use your mail client as the UI

Brilliant little script that sets up a basic POP3 and SMTP server on localhost to give Bitmessage an email interface for example that Thunderbird can connect to. This mean the messages can be organised in a local folder structure or easily coped to your IMAP structure.

• First enable the Bitmessage API in your local keys.dat configuration file.
• Install the PyBitmessage-Daemon script into your home folder (I used git clone for easy update) and run it with python daemon.py.
• Install the bmwrapper into your home (I used git clone again)
• Set up an account on your mail client on localhost, POP3 on 12344 and SMTP on 12345 as shown here.
• Create a .desktop file that runs a launch shell script
• Create the launch script that runs a separate launch script for each of the three e.g.

#!/bin/sh cd ~/PyBitmessage ./bm1.sh & ./bm2.sh & ./bm3.sh

• Create each of the three launchers one to run each of the scripts with python2.7, for example the first of mine is:

python2.7 ~/PyBitmessage/src/bitmessagemain.py

• Ensure all the launchers have executable permission. This complicated procedure is required because each one is a daemon that doesn't return and won't run in the background using the ampersand.
• You can check if they're running with netstat -nlp and check you have apps listening on 8442, 12344 and 12345, e.g.

tcp 0 0 127.0.0.1:12344 0.0.0.0:* LISTEN 3575/python2.7 tcp 0 0 127.0.0.1:12345 0.0.0.0:* LISTEN 3575/python2.7 tcp 0 0 127.0.0.1:8442 0.0.0.0:* LISTEN 3577/python2.7 tcp 0 0 0.0.0.0:8444 0.0.0.0:* LISTEN 3577/python2.7

See also

• Bitmessage home page
• Privacy
• Peer-to-peer
• Bitcoin