|A message from Big Brother?|
I started using Bitmessage yesterday, and it didn't take long before I witnessed a possible Big Brother interference of the network. Of course, this is only speculations, but in light of what has been revealed over the last weeks you have to be naive not even thinking of the possibility that Big Brother would ta actions to know whom are using Bitmessage.
Everyone on Bitmessage has received a message on the following format:
Bitmessage has several potential security issues including a broken proof of work function and potential private key leaks.
A message written to trick users into clicking on the link.
And every address on Bitmessage did receive a unique URL, like:
Following the URL you would only get a "500 Internal Server Error page":
|The source code of the page.|
The domain secupost.net was registerred yesterday:
All pubkeys for all addresses are published except those for chans (assuming all of the humans join the chan correctly using the menu option rather than using "Regenerate Deterministic Addresses"). It is very plausible that it is someone attempting IP address correlation which would involve sending out a lot of messages which would explain the current spike in the number of messages in the network.
The website is not working, was it ever up?
I assume this is some sort of trap to find out more (IP, browser, etc) from the corresponding bitmessage ID?
I have now received it at all 8 of my addresses, only one of which I've ever given anyone. Maybe it's the NSA trying to link public keys to addresses when you open the link... Good thing I use a VPN.
This also leads me to wonder if the error 500 pages are really related to a resource issue as I previously speculated. It could be that the server was intentionally misconfigured and the plan all along was to log the incoming IP addresses next to the URLs of the incoming connection attempts, which can then in turn be correlated to BM addresses.
Mr "Robert White" was behind the "attack" (message from secupost.net and Bitmessage):
-- -- --
This message is also available at http://secupost.net
Alright, the messages sent out a few days ago are starting to expire now. It's time for everyone to learn what the purpose of secupost.net is.
As many of you guessed, this is indeed a Bitmessage address to IP address mapper. Yes, the only thing that webserver would send was a 500 message.
It did alright too, gathering nearly 500 bitmessage users information after sending 15000 messages. Double what I expected.
I've included both a log of each address detected and the first thing to hit it including IP, reverse DNS and useragent as well as raw logs for every valid request. If you need to confirm this signature so you can verify messages from me when bitmessage is down, please see the bitmessage general chan for a copy from my bitmessage address.
So, future lessons:
- - - Yes, all bitmessage addresses are public and can be read from your messages.dat file using a small script.
- - - Don't click links. Even if it looks like a security-related site and uses some technical terms. I am not a nice person, I will publish any information I can gather about you and I don't care if you get lit on fire by terrorists because of it.
- - - Bitmessage does _not_ scale. It took me around 3.5 hours to send ~15k messages but it took the bitmessage network over 18 hours to fully propogate them.
Some of you were smart enough to use tor or VPN providers, but many of these are direct home or server IPs. The information below is more than enough for any government to come after you or any script kiddie to DDoS you. Be more careful next time.
Some of you tried to use scripts to claim addresses which weren't yours and skew the data, of course, you didn't even change your user-agent.
Even without accouting for that your attacks were ineffective because the IDs were generated in a non-linear fashion using a cropped HMAC-SHA256. To find your id:
mac = hmac.new("fuck you", addr, hashlib.sha256).digest()
return unpack('>I', mac[0:4])
This simple deterministic method means that you would have had to try... (2^32/15000)/2 = 143165 times on average just to get a single collision. Thanks for playing, but no luck this time.
This service has been operated completely anonymously thanks to Tor and Bitcoin. I hope you enjoy the result.
Robert White (BM-2D8yr4fzoMzwndqPwLMVyzUcdfK9LWZXjY)
And here is one response from a Bitmessage user:
-- -- --
Thought #1, thanks asshole (Robert White (BM-2D8yr4fzoMzwndqPwLMVyzUcdfK9LWZXjY))
Thought #2, you aren't as smart as you think you are. Some of us took precautions that you haven't even considered. At least I did, and my spoofed records appeared in his list.
Thought #3, the conclusions are not supported by the facts. ("does _not_ scale")
Thought #4, my infant son can't get a job. He does not scale. He needs to be terminated.
Thought #5, be part of the solution, not part of the problem.
Thought #6, did I mention Robert White is an asshole?
-- -- --
Bitmessage Proof Of Work optimizations including OpenCL and C based PoW code.