![]() In case of deterministic addresses it can be reproduced with a passphrase, in case of random addresses it can't be.Īs you see, the main security issues with the points you mentioned are, that the keys are stored unprotected and that the uniqueness of addresses relies on the collision resistance of RIPEMD160. The private key is stored keys.dat, without encryption, easily accessible by anyone having access to this file. However the reference implementation does the following: The protocol doesn't describe how the private key is to be stored. Furthermore the addresses have to live in the same stream (at the moment there's only one) and they have to share the address version. Now the odds of finding a collision are even a bit lower than the birthday bound of RIPEMD160 (80 bits) as the hash has to start with a zero (or more zeroes). Basically you'll obtain a collision if the RIPEMD160 of the SHA-512 of the two public keys (encrypting, verifying) yields a collision. You can also route the traffic via TOR it if you’ve downloaded the TOR browser bundle. For the details, enter/select the following: Type: SOCKS5 Server hostname: localhost Port: 9050. I'm not aware of any collisions, however the collision resistance isn't also at 80 bits. If you simply wish BitMessage to use Tor, all you need to do is click on settings > network settings. The way the public addresses are generated is quite complicated and is documented here. Bitmessage is an open source P2P program utilizing a Bitcoin like protocol that instead of sending money sends anonymous encrypted messages to one or multiple people at once, the application has a portable mode that does not need installation, it uses 2048-bit RSA encryption keys stored inside a keys. If the MAC's invalid discard the message as "not for you". Derive the shared key using the provided public ECDH value and your private key, derive the authentication key, check the MAC is correct and decipher the message. ![]() The message will be composed of the IV, the public ECDH value, the ciphertext and the MAC.ĭecryption is pretty straightforward. Encrypt the message using this symmetric encryption scheme and form the HMAC on the ciphertext. Hash the shared secret (using SHA-512) and use the first 256-bit as key for HMAC-SHA-256 and the second 256-bit as the key for AES-CBC with PKCS#7 padding. Generate a new message key by generating a new ECDH key pair and "agree" on a shared key with the recipient's (=Bob) public key. BitMessage is decentralized and trustless, meaning that users do not need to place faith in entities like root certificate authorities. The PyBitmessage client is written in Python with a Qt GUI. I'll quickly explain the basics.įor each message, generate a secure 128-bit IV. BitMessage is a P2P asynchronous communications protocol used to send encrypted messages to another person or to many subscribers. The bitmessage wiki explains how the encryption takes place. ![]() How does asymmetric encryption work in bitmessage? Perhaps the connections should be later raised from 8 to 16 to get enough speed in the i2p network.I'll answer your "detailed questions", I'm sure the "main security issues" will become obvious afterwards. Since the i2p is really slow, I will stop my test by now, because syncing of 100 messages takes several minutes with 2 connections over i2p. Is this possible? Are the BM- and BM+ addresses internal the same or are these messages never received by anyone, since one cant add BM- addresses? ![]() PS: I copied the messages.dat from the vanilla network into the i2p version, it seems that my client uploaded some messages from vanilla to i2p version. I got only 2 connections and 38 p2p - messages. Or someone wants to write me a personal message: BM+2cWvjUYVmMk7mTzt5MK1rZNSG9zshhhaRU Is someone interested to send some messages to the i2p channel:īM+2cUgwuy64AR7LiXx2aBJFSQcP1scfMMphW (It's the same from the normal bitmessage network just with an + instead of -) (If SAM was deactivated, bitmessages just started for 5 seconds and then shutdown without any message or GUI popping up.) Step 5: Scroll down and find Bitmessage notification address. Right-click on the adress and click Copy address to clipboard. I just activated SAM in i2p and started bitmessage and it worked. Step 1: Copy your Bitmessage address from the Messages section. Thx, its seems to work using windows 8.1 easily.
0 Comments
Leave a Reply. |