![]() ![]() The status column displays the current status of the message. ![]() The sent tab displays messages sent by the user, including messages that are in the process of proof of work. Example: Sending a message to 8 people will generate the exact same message 8 times in the "Sent" tab. A message can be dedicated to multiple people but the protocol supports only one receiving address per message. The "Send" tab is used to compose new private or Broadcast messages. Messages that are no longer needed can be sent to the trash with the key. Using the HTML view renders some HTML tags from the message, for example images. The context menu in the message list provides additional features, such as HTML view, save as text file and a reply option. The bottom window allows copying and editing the message but it will not be saved. The inbox contains all your received messages (top part) and displays the currently selected message (bottom part). The Main interface contains the following tabs: PyBitmessage will automatically connect to other clients on start up, the user does not needs to wait for this to complete and can instantly send messages. Main window with sent tab open (Windows 7) It can be launched and the required files for its operation are created if they do not exist. The client sets up itself completely automatic. Other builds (for example for Mac OS X) can be found in the forum. PyBitmessage can be downloaded from the Main Page, either as Windows binary or as source from github. It is usually abbreviated "Bitmessage", causing confusion between the protocol and the client. using BitMessage).PyBitmessage is the official client, used as protocol reference. really is Alice's address step 2: send a message to BM‐2nTX1Kc. I think that something like PGP's web of trust could be implemented on top of BitMessage to provide identity verification: such authentication is not incompatible with BitMessage, but it seems to be a service that would exists independent of BitMessage (i.e., step 1: verify that BM‐2nTX1Kc. The primary use for BitMessage (as presented in the paper, anyway) seems to be the ability to sent messages that are from a cryptographically verified source, but that source is free to avoid identifying themselves in any real-world way. This would allow an individual or organization to anonymously publish content using an authenticated identity to everyone who wishes to listen. Even if throw-away email addresses are used, users must connect to an email server to send and retrieve messages, revealing their IP address.Īnd when talking about broadcast messages (emphasis mine): In fact, the lack of connection between an address and a real-world entity seems to be branded as a feature: Maybe so, but if they did, that's not a problem that Bitmessage is designed to solve. then, you use the Bitmessage system to encrypt your message so it is readable only by Alice's private key.īut how did you know that BM‐2nTX1KchxgnmHvy9ntCN9r7sgKTraxczzyE is really Alice's address? Maybe someone printed out fake business cards, or hijacked Alice's website to change her address. When you have fetched the key, you quickly verify that its fingerprint matches the one in Alice's address. You make a P2P Bitmessage request to get the public key associated with BM‐2nTX1KchxgnmHvy9ntCN9r7sgKTraxczzyE. Alice advertises her Bitmessage address (e.g., on her business cards, on her public website, etc.) as BM‐2nTX1KchxgnmHvy9ntCN9r7sgKTraxczzyE. Thus, there is nothing to verify: when you send a message to user with public key P, you don't need to verify that your recipient's public key is really P, because you have identified your recipient solely by his public key.Īs for how to tell if a public key belongs to a particular real-world entity: you can't, just as you can't easily verify that a particular email address belongs to a particular real-world entity.įor example, you want to send Alice a message. It appears that a user's public key (or, a hash of their public key) is their messaging address. an example address would be: BM‐2nTX1KchxgnmHvy9ntCN9r7sgKTraxczzyE. If the public key can be obtained by the underlying protocol, then it can easily be hashed to verify that it belongs to the intended recipient. We propose a system where users exchange a hash of a public key that also functions as the user’s address. Since only the actual recipient can successfully decrypt the messages intended for him, all network participants know that if they fail to decrypt the message then the message was not intended for them. Therefore, every network participant tries to decrypt every message passing through the network even if the message was not originally intended for that network participant. Outgoing messages contain no explicit address of the recipient of the message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |