BitMessage is heavily secure but does not require pgp as this is built in using hash instead, making it simpler to use once you have an address to send to and from, this forming part of the security protocol used. Anonymity is all but guaranteed it cannot be traced and the message despite working through the peer network can not be hacked intercepted or altered in any way. Optionally create a startup script that runs the command python PyBitmessage/src/bitmessagemain.pyĪnd this is how the application looks like:īitMessage is a secure very secure paranoid email system which when run from the command line connects to many remote peer network clients.Start PyBitmessage by entering the command python bitmessagemain.py.Change to the PyBitmessage source directory by entering the command cd PyBitmessage/src.# git clone https: // /Bitmessage /PyBitmessage Open a terminal and test that you have python, OpenSSL and git installed by opening a terminal and testing them with the following commands :.If this operation is easily worked in to BitMessage clients, it could provide a push for other projects in the decentralized social networking space to put a stronger focus on privacy and security. As messages are sent out as broadcasts, it would be easy for individuals to simply “subscribe” to the messages that are sent by users they like, then receive them in a manner similar to Twitter, identi.ca or Tent feeds. More than just a decentralized and anonymous messaging system, BitMessage appears to also have limited social messaging capability. This follows a decentralized model in which certain machines act as “parents” for streams and will aid in advertising the clients it has in its stream, and facilitating the connection. Clients will only connect to a stream if they have a message to send or receive somewhere in that stream. Once the network gets to be a certain size, it will break itself into separate streams. BitMessage responds to this by proposing a so-called “stream” infrastructure. This presents major issues with scalability, as has been noted with BitCoin’s system. Messages not intended for that client will simply be ignored. Then, each client attempts to decrypt the message if it is intended for that client.
Similar to BitCoin’s operation, BitMessages are sent out to all users who are connected to the system. Similar to how BitCoin allows one to send money to anonymous recipients without advertising metadata to others, BitMessage communicates via simple addresses generated from public keys, which need not be tied to a specific user’s identity.
One of the most prominent strengths of the BitMessage system is how it enforces anonymity. Now a newcomer to the scene proposes a different way of thinking about encrypted communication, one that borrows from its more well-known older brother, BitCoin.Ī project has been started that intends to recreate BitCoin’s decentralized P2P model for seamless message encryption and transmission.īitMessage was started by Jonathan Warr en late last year and has now made it up to version 0.2.4. Over the past few years, a handful of different encrypted messaging systems have cropped up and gained prominence, notably Cryptocat and the OTR specification. Today I propose you an interesting topic based on an article by Jacob Cook first published on
0 kommentar(er)
