3 ms·
"... Firstly, we made a big error. For this we are, of course, extremely sorry. The legacy customer database, with passwords stored in plain text, was a liabili
by bootload 17y ago
"... Firstly, we made a big error. For this we are, of course, extremely sorry. The legacy customer database, with passwords stored in plain text, was a liability. Even though it wasn't active, it should have been deleted. There's no logical explanation for why it wasn't, other than as we moved off one project, and on to the next one, we dropped the ball and screwed up. ..."
Plain text for passwords fast, but not good.
- doron 17y agoIt is kind of amazing they did this, and the fact they didn't fix it when they could, speaks of negligence. I appreciate the honesty and the "No Bullshit" stance. Still you have to wonder, Atlassian is building organizational communication tools, they are also using them their own development and business process, It gives pause when you consider the software they develop to actually do the job the are claiming it helps to achieve. Isn't the whole point of this type of software, is to help stuff like that not happen by enhancing organizational communication?
- btilly 17y agoThey switched to dogfooding their own product in 2008, and you'll note that accounts created after that are not affected.
- amatriain 17y agoWhat the hell is "dogfooding"?
- waterlesscloud 17y agoUsing your own product internally. From "eating your own dogfood." http://en.wikipedia.org/wiki/Eating_one%27s_own_dog_food http://en.wikipedia.org/wiki/Eating_one%27s_own_dog_food