@jonhoneyball @bazzacollins Storing usernames and passwords in plaintext was :-)
-
-
Replying to @sbisson
@sbisson@bazzacollins but thats once they were in. And again its not a hack. They got in cos of bad password practise, which is not DB1 reply 0 retweets 0 likes -
Replying to @jonhoneyball
@jonhoneyball@bazzacollins Dropbox was storing usernames and passwords in the clear internally. That is the definition of bad security.1 reply 0 retweets 0 likes -
Replying to @sbisson
@sbisson@bazzacollins i agree storing username/pw in plain text was bad. But the route to that file wasnt a hack of DB's security.2 replies 0 retweets 0 likes -
Replying to @jonhoneyball
@jonhoneyball@bazzacollins That doesn't matter. You should assume that it's going to happen, and secure information appropriately.1 reply 0 retweets 0 likes -
Replying to @sbisson
@sbisson@bazzacollins it matters in correct terminology. dropbox's security wasnt hacked.2 replies 0 retweets 0 likes -
Replying to @jonhoneyball
@jonhoneyball@sbisson If you accept the definition of "hacking" as breaking into a computer network, that's exactly what happened.3 replies 0 retweets 0 likes -
Replying to @bazzacollins
@bazzacollins@sbisson simply because they didnt "break" in. They walked in using a legitimate username and password.1 reply 0 retweets 0 likes -
Replying to @jonhoneyball
@jonhoneyball@sbisson The flaw was the employee was seemingly reusing his work password on other sites.1 reply 0 retweets 0 likes -
Replying to @bazzacollins
@bazzacollins@sbisson agreed -- now was that a flaw of DB or not? Thats the question at hand.3 replies 0 retweets 0 likes
@jonhoneyball @sbisson It's certainly not clear cut.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.