HN user
The database contains full addresses, names. You can easily find who is cohabiting with them fairly reliably (near 100% if they live in a house) through a variety of services which list that information.
All I can say is there's going to be a hell of a lot of blackmail. I'm sure there's already a group on IRC organizing blackmail. There's a lot of targets and it's very information rich.
I'm obviously a dick because I already sent automated messages to relatives of people in the hack indicating to them that they were potentially cheated on.
Personally I would want to know so I share that information.
https://www.reddit.com/r/Bitcoin/comments/3fe92x/im_ashley_b...
The entire codebase was stored in a database, only accessible via a client Mark maintained, with no version control nor lock controls meaning if we both had a file open we could overwrite one another's files and undo work.
>Like, PHP source stored in mysql tables?
PHP, CSS, JavaScript, HTML. Errything.
There was no pre-production environment. Meaning changes were supposedly deployed untested or made straight on production.
I was told I could not touch the backend, although they were working on getting access to this via Mark.
WAT
They make some nice shoes, too.
Maybe they shouldn't have started the war in the first place. Stop trying to gentrify the internet.
Also, people who disagree with you == trolls? Nice.
It was a multi unit building.
Also holy shit that place looks like a dump.
One of the things that was emphasized to me when I was studying the ancient greeks was that I should try to step outside my own mindset and try to read the text as it is, rather than to try to interpret it from my own cultural or modern perspective. I think this is an important step to take when you study these kinds of texts.
This article really disappointed me. It isn't about how cryptographically "horse battery staple" is not correct, it's more that passwords in general are the wrong paradigm for security.
I don't see how it's obsolete. Just because code is old that doesn't mean that it's obsolete.
If code is sound it will be around for as long as it takes to supplant it. As far as I know the majority of the current Bash code is well suited and up to date. If this article is some kind of response to the recent vulnerability (that the media decide to lose their collective minds about) then it's simply reactionary garbage that has no real familiarity with the code base.
I'll finish by saying that a code base that is algorithmically sound will remain so for the foreseeable future.