Earlier quoted context omitted.
Maybe then they'll stop with the half-assed apologies and recognize that there's a right way and a wrong way to do things. PHPFog built a castle out of sand and you're upset that a wave came and demolished it. I'm always surprised at how thin-skinned a lot of HN commentary is. "Oh, Zed shouldn't be so rude" "These kids' lives should be destroyed for playing games with an wholly insecure website." "I stopped reading t…
This isn't a wave knocking over a sandcastle or a dog shitting in the house. These are 16 year old kids, old enough to know right from wrong, and with the knowledge and skills to exploit the system. And once the exploit worked, they didn't then responsibly disclose the problem to PHPFog; they started vandalizing, changing passwords, and the works. This is like someone finding an unlocked door to the apartment buildin…
How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
191–200 of 202 posts
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#192Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#193Earlier quoted context omitted.
Or swapped over to Bcrypt
we've cleared the old SHA512-salted passwords out of our production database and have upgraded the password hashing to bcrypt, with a cost of 10.
Just in case anyone doesn't know why Bcrypt is so awesome, it's because it actually takes longer to hash (based on the difficulty level you set, and you can bump up the difficulty level as hardware gets more powerful).
For other applications, you want hashing to be fast. But for passwords, you want hashing to be as slow as possible without compromising user experience.
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#194I feel really bad for the phpfog guys. But given the situation, I think they handled it admirably well - kudos to them. No software is secure and this could have happened to anyone. Especially startups who have to take shortcuts at the very beginning. I know the attackers were just kids but I have to admit pursuing legal action sounds very tempting - even to just act as a deterrent to others. If they had just put up…
What I find most disturbing about this whole situation is the way in which these teenagers are handling themselves, especially after the fact. The continued denial of responsibility and half-hearted mea culpa, coupled with the monetary damage to those businesses who had been running on PHPFog, leads me to sincerely desire that these teenagers face a penalty of some magnitude, not just a slap on the wrist. Maybe then…
I think they should definitely get something a little stronger than a slap on the wrist, but also remember that they're just teenagers who don't know any better. All they really need is enough of a punishment to learn their lesson, and they'll probably end up productive members of society.
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#195The phpfog guys really deserve praise for being so open on this issue. As a fellow engineer, being able to learn from their mistakes and see exactly what they could have done ahead of time to avoid the disaster is priceless. Just goes to show that those with the time to spend are the most likely to break your stuff, even if you pay "professional white hat hackers" to test your system.
On the contrary, they knew of security vulnerabilities and intentionally left them unpatched, then blamed it on chance and timing when they got owned because of it. Avoid phpfog if at all possible, in my opinion.
Honestly, there are very very few developers that fix security problems in beta environments before anything else. In my experience, it's more likely that you're fighting fires, handling outages, and dealing with problems of scale than fixing security vulnerabilities.
Besides, isn't a beta the correct time to find these security issues? (Design / Alpha would be the ideal time, granted, but sometimes that's not possible.)
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#196Earlier quoted context omitted.
we've cleared the old SHA512-salted passwords out of our production database and have upgraded the password hashing to bcrypt, with a cost of 10.
Good call :) Just in case anyone doesn't know why Bcrypt is so awesome, it's because it actually takes longer to hash (based on the difficulty level you set, and you can bump up the difficulty level as hardware gets more powerful). For other applications, you want hashing to be fast. But for passwords, you want hashing to be as slow as possible without compromising user experience.
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#197Earlier quoted context omitted.
When I asked for a raise to my limit they denied me, on the basis that my usage was insufficient. Of course, my usage was low because I hadn't launched my product fully because I didn't have enough instances to serve a lot of customers ... catch 22. So I had to build out a rather convoluted architecture that used the loophole of deploying to multiple regions and failing over to whichever region would give me an insta…
Sorry you had a bad experience. I have gotten nothing but superb support from Amazon staff. I'm surprised they weren't willing to accommodate you, doubly so if you were ready to pay. One thing that surprises me is when people talk about utilizing multiple availability zones in EC2 as some sort of burden. It's very clear from their documentation and architecture that you need to be capable running in at least 2 availa…
My use case isn't for an ongoing server where you require availability. It's purely about compute power - I don't care where the compute power comes from but preferably I want low latency to my customer. So ideally I would just get all instances for any given customer from a single region.
I did find in the end that, as you say, I would sometimes not be able to get an instance in a region even when I was below my 20 limit for reasons internal to Amazon, so the failover work was going to be something I had to deal with anyhow ... but it just added complexity to my life earlier than it would have otherwise.
Edit: I would also mention that I certainly don't think of it as a "bad" experience. I think it is something of a small miracle that Amazon offers the service they do in the first place and I certainly understand why they have caution about handing out large limits to just anyone. I only made my comment above as a kind of caution to not just assume you're going to get a raised limit from Amazon immediately and especially don't leave talking to Amazon about it until the last minute if you're planning to launch something.
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#198I mentioned this last time, but I don't think anyone was interested, but the "John" guy is compwhizii (same handle on Twitter) who runs the forums (facepunch.com) for garrysmod, a very popular game. I will be curious to see how garry (owner person) responds to this, or if he already has. Elliot is apparently VERY scared and blames John (compwhizii) (edit: not john, he blames someone else called supersnail1): http://w…
And here's Elliot's "official statement": http://elliotspeck.com/phpfog.html And for anyone who missed it, here's what Elliot posted in the previous HN discussion about the phpFog breach: http://news.ycombinator.com/item?id=2346161
Kids (and like it or not, that IS what they are) are notoriously dramatic and these kids are definitely experiencing this as a crisis, no matter how they present in their comments.
They are also now being border-line, and in some cases overtly cyber bullied by some of their peers online which may be devastating if they don't have great face-to-face support. As adults, we have a responsibility not to add fuel to that fire and remember that if teenagers were predictable and transparent, there wouldn't be so many tragic cases in the news where they hurt themselves and each other.
Part of the problem is that teenagers and young adults aren't great at predicting consequences. This isn't opinion - it's science.
Especially in males, the part of the brain that is responsible for predicting consequences is not fully developed until the early to middle twenties. This is a double whammy because it leads to their bad decision making, but also to their belief that when something bad happens as a result, that it's literally the end of the world... that there is no way out.
There is no disputing that what these boys did was a big deal and that there have to be consequences. But it's also just a symptom of a bigger problem: as a society, we have failed to keep pace with the challenges that are the result of the first generation of digital natives (kids) being raised and educated by a generation of adults who are (at best) digital immigrants.
This post is getting way too long so I'm going to finish it on my blog @ thenewtag.com But thanks, criticsquid and nbpoole for posting some of the aftermath. I hope that one of the 1st things phpfog (or the authorities) did was involve these boys' parents?
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#199I mentioned this last time, but I don't think anyone was interested, but the "John" guy is compwhizii (same handle on Twitter) who runs the forums (facepunch.com) for garrysmod, a very popular game. I will be curious to see how garry (owner person) responds to this, or if he already has. Elliot is apparently VERY scared and blames John (compwhizii) (edit: not john, he blames someone else called supersnail1): http://w…
Re: How We Got Owned by a Few Teenagers (and Why It Will Never Happen Again)
#200Earlier quoted context omitted.
The last bit is priceless. The mere fact that the kid doesn't show any sort of adequate moral judgement should justify prosecution.
Isn't the lack of adequate judgement (moral or other) the definition of being a kid?