Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment Timeline of events (Score 1) 194

It would be nice if someone has a compiled timeline of events starting with extremely uncoordinated writing and passing of the law, to the point where technical specs were released to the contractor, when the actually flow of information and final HHS rules were announced, up through go live and the fixes being implemented after go live.

From what I've read/heard there was little to no work being done from 2010 when the bill was signed into law up through 2012. The administration purposely withheld information about Obamacare from the public and from the contractor due to the election year (2012) and didn't want bad press. Once the election had passed the government released more specs and information to the public and to the contractor on how the website was supposed to function. That's when we found out the dirty little lies and secrets. It's damn near impossible to build a website/service to handle 300M+ people in 6 months, but that's what our government did.

This whole bill/law/implementation has been bungled so badly by:
- the incompetent people who wrote it (bureaucrats with no understanding of health care and did not consult people from the health care industry)
- the incompetent people in Congress who blindly passed it without reading or understanding the devastating effect it would have
- the incompetent administration who continued to lie about how the law affected the citizens, and took no ownership of this massive project

Can anyone imagine a scenario where this could have been handled worse? Every step along the way was screwed up.

Comment Re:Radicalization (Score 3, Insightful) 868

Hamas started it and reuses to agree to any proposed cease fire. Israel isn't the group calling for the extermination, Hamas is. Israel has also offered legitimacy to the Palestinian government in exchange for a cease fire and removing the language in the charter to kill all jews.

But yeah, go ahead and blame Israel.

Comment Probably because of French entitlements (Score 1) 309

People in France work fewer hours than their US counterparts. France has mandated a 35 hour work week for their full time employees. The US averages 42 hours for full time work (will probably go down after Obamacare is implemented) and often full time salaried employees have an average of 45-55 hours a week. France also requires a minimum of 5 weeks vacation.

Gee, I wonder why their products are more expensive than the US...

Comment I can't believe that people are falling for this (Score 1) 182

We all know that businesses really don't pay taxes, right? I mean they do, but the companies charge more for their products and services as a result of paying taxes. There's not a single business around that just eats that cost. My point is that it's not like this man is voluntarily giving up money. He will still make just as much money.

Everyone who uses oil and gas products will pay a higher price because of this. I'm not saying that's good or bad - that's not the point of my post. I'm just trying to point out that everyone pays for business tax increases, not just the businesses.

Comment Re:this is reassuring (Score 1) 481

The only security was that it was airgapped and had obsessive, paranoid, over the top physical security. The age of the systems (the existence of 8" floppies for example) added nothing to the system security. Because it likely was never designed with any computer security beyond the console itself, bypassing the console could well bypasses the entire missile security system.

We have no proof or idea of the security within the system itself. Any talk of it is pure speculation. What we do know is that the code is constantly being reviewed and has been updated since it's first implementation.

It would be much easier for an enemy/terrorist to get their own nuclear bombs from another source.

Comment Re:this is reassuring (Score 1) 481

Likewise the idea that there are no "network ports", hence no way for modern systems to get access. This probably also that the whole system has no "network" security, bypass the security console and you have direct access to the entire launch system, because it never occurred to the creators that you could spoof the entire console. (The equivalent of the old Windows password you could bypass by hitting "cancel" on the "Try again: Yes/No/Cancel".) So if someone can smuggle something small past the, probably impressive secured, airgap, there is no second line of defence. Unplug the existing terminal, plug in a tiny portable bit of modern, hard-hacked kit, pwn the whole system.

You might argue that the techniques necessary are not routine hacker knowledge. But Stuxnet was not created by a script-kiddy. They had a deep understanding of the system they were trying to sabotage. This is a nuclear missile silo, you can reasonably assume a motivated attacker.

The scenario you describe means that they would have had to bypass several layers of physical security and also remove/compromise the two people at the missile command consoles, which are probably also armed.

The chances of someone successfully pulling off a plan like this is so insignificant it would never happen, unless its in a movie.

Face it. The system is about as secure as it possibly could be.

Slashdot Top Deals

Serving coffee on aircraft causes turbulence.

Working...