- Namecheap's WhoisGuard. Do you really think I'd not try and protect myself? I was debating for a week whether I should post anything at all. Tesla sure as hell knows someone new is doing something somewhere. I'm trying REALLY hard to make it so absolutely nothing can be easily linked back to me. The "dramatic reenactment" had to be done. I have pictures of me actually rooting but the PS1 on the car is tesla@cid-<VIN>$ Can't really show that if I'm trying to be anonymous. Funny anecdote: I had posted it Tuesday night before bed, but I didn't show anyone. In the morning I was driving to work and looked down at my IC. So, you can name your cars, and the name I gave my car was on the IC. Sure enough, the factory mode IC picture had that name. It was a fairly unique name, and I had to hurry up and censor that one too.
- Sorry my blog doesn't pass your technical writing course. Thank God it's just a blog and I can write it however I want.
- There's no reason to mention the previous hacks from other people. Are they me? No. You can read that stuff somewhere else.
- Ahh, you caught me on the "2 months of research". That's the term I use when I'm actually saying "2 months of slacking." I was distracted by new coloring books for a while. Also I really didn't want to have to make the cable. I was trying to get a salvaged one for a while. Eventually I had to suck it up.
So, sooooorry to disappoint you that it's not an organized leak from Tesla and that it's not the "best case". I knew the post would be somewhat popular, but nowhere near this popular. I thought it'd be the later posts where I'm actually showing stuff instead of me just ripping my car apart that people would love. It's actually funny when a friend of mine told me about this thread. Here I am terrified out of my mind that Tesla was going to figure out who I was, and then everyone is saying I AM Tesla.
Because
* when I ask CloudFlare to stop resolving phishing domains with their nameservers they don't care.
* when I ask amazon to remove the content from their networks that's clearly against their TOS, they don't care.
* when I try to get in touch with PrivacyGuard about this domain, they don't care either.
* I ask aweber.com to cut off this customer who they are providing mailinglistservice for, they don't care.
These are all at least semi-reputable companies, who through inaction continue to allow criminals to abuse their infrastructure, and do not allow me to directly contact this offending customer.
So there is no way for me to find out which entity is responsible for actually creating this phishing operation. Granted, they'd probably fake whois data anyhow, but it's my last straw :-)
Now, I'm actually all for anonymity, I'm just frustrated with trying to remove this phishing site that's been up for months now.
[0] https://news.ycombinator.com/item?id=11440612 [1] https://news.ycombinator.com/item?id=11441113
- It is a blog with only 1 entry.
- The Whois entry is "WhoisGuard Protected" in Panama: http://who.is/whois/www.su-tesla.space . Very bad timing with the #panamapapers. The non-technical depth and the naive writing let me imagine that a junior social media employee could have done it. And I'm disappointed if Tesla hired such people / let an intern write a PR article.
- There is no mention about the previous testimonial of the guy who tried to hack his Tesla, received a disabling upgrade and a phone call from Tesla. https://news.ycombinator.com/item?id=11255160
- He pretends to have done "2 months of research". What could be researched? There is no public documentation and the hackerspace is still empty. At the very least he would have mentioned that he managed to overcome the item above.
In the best case this is an organized leak from Tesla: Let's hope they'll use this channel to unofficially explain how to hack the Tesla.