dgfv1
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.
Personally I would want to know so I share that information.
>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
Also, people who disagree with you == trolls? Nice.
Also holy shit that place looks like a dump.
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.