3 ms·
In a project this convoluted...not in terms of actual feature complexity, but the shitwork that was generated by bureaucracy and political infighting...how coul
by danso 13y ago
In a project this convoluted...not in terms of actual feature complexity, but the shitwork that was generated by bureaucracy and political infighting...how could Healthcare.gov not have serious issues with XSS and SQL?
Think back to Egor Homanov's amazing hack of Github using a Rails vulnerability to well-known to Rails core team that argued it was not an issue because only fools wouldn't use attr_protected. Github has brilliant programmers and (one would hope) a well-oiled engineering environment and still was vulnerable to this fatal flaw.
Now imagine a project with far lesser engineers, highly paid but no real ownership, controlled by people who care more about political deadlines than actual functionality. And top it off with what seems like a hodgepdoge of arcane technology and processes. How could there not be at least a few catastrophic holes?
On a sidenote...I've seen a few references to "MarkLogic" being the datastore for Healthcare.gov. It's not open-source and has little adoption in the developer community:
http://slashdot.org/story/13/11/24/1437203/nyt-healthcaregov-project-chaos-due-partly-to-unorthodox-database-choice http://slashdot.org/story/13/11/24/1437203/nyt-healthcaregov...
Whose genius idea was it to use a non-notable proprietary database software for this? And what was the reasoning? Technical, or political?