“Right wingers have been distributing the link to the necessary tools to perform the attacks on the Healthcare.gov website through social networking, as pointed out by Information Week, and other websites .”
Full article here:
Wow! Now, we know why Obamacare and the rollout have been such a failure! But, er, how have the attacks on the web site made people lose their insurance and medical provider? and is this why the insurance companies are balking? because they knew in advance that someone would/could disrupt the web site… and that this would affect pricing on a massive scale? Well, no wonder then! Evil right-wing reichists! How dare they take away grandma’s health care! Oh, Obamacare did that? er, but then how dare they take away some er yes… nevermind…
Sounds like script kiddies. Just installing a program in your home computer that targets the main website would be water off a ducks back. Those really intent to bring down a site like that, would have their personal army of hundreds or thousands of “bots” (other peoples computers they have control over) and wouldn’t target the main site, but a weak spot. Like something in the IRS for example that is required to process registration.
They should have employed the makers of pornhub. I’m sure they would have done an excellent job in handling the traffic.
[quote=“Mick”]Sounds like script kiddies. Just installing a program in your home computer that targets the main website would be water off a ducks back. Those really intent to bring down a site like that, would have their personal army of hundreds or thousands of “bots” (other peoples computers they have control over) and wouldn’t target the main site, but a weak spot. Like something in the IRS for example that is required to process registration.
They should have employed the makers of pornhub. I’m sure they would have done an excellent job in handling the traffic.[/quote]
with DDoS (distributed denial of service) attacks, necessary tools means tools that sniff out vulnerable computers to be used as bots.
I don’t really see how the news report conflicts with your description of attack. Also I think while aiming at a weak spot would more be effective, aiming at the main site makes it easier for those who aren’t entirely sure what exactly they are doing (if they are simply following a step-by-step instruction.) It wouldn’t completely hose service to the site, but could slow it down and make it intermittent if the attack approaches bandwidth capacity. And that description sounds pretty much like what happened.
Who says it even pulled off? As DDOS attempts go, this is pretty lame. This sort of thing is not effective against properly constructed sites. Oh wait… that’s right.
Who says it even pulled off? As DDOS attempts go, this is pretty lame. This sort of thing is not effective against properly constructed sites. Oh wait… that’s right.[/quote]
it has nothing to do with site construction, it has to do with bandwidth management. Upgrading (or getting redundant) networking hardware is pretty much the only way to go (yeah, yeah, firewall and mod_evasive for apache, doing so could still slows down your site or make it intermittent, which could limit actual usage).
There was a Taiwanese tech site that wrote a post for how to defend against DDoS attack using firewall and apache addon, and a few days after the post, his site fell prey to DDoS attack (which made his site service intermittent.)
DDoS attack has brought down the CIA, NSA websites before. It took down China’s .cn domain a while ago. It is also used to bring down the entire Filipino .gov domain earlier this year when Taiwanese hackers were angry with the killing of Taiwanese fisherman (which later was replaced by more skilled hacker gaining database password from an undeleted vim temp file, giving access to the entire system.)
Yeah, some of the most common complains were people couldn’t get to the website or could log in on it, was slow/long delays and timed out a lot, error messages, only 1 out of 10 was able to complete the process (9 bots?) and they said it had 19 million clicks the first day, and before the roll out, the concern was if people was going to be interested enough to sign in.
All of them sounded like a DDOs attack from the beginning.
Except that the problems with the Obamacare site had almost nothing to do with GETTING THE SITE TO RESPOND, but rather were about how unusable the site was WHEN IT WAS ACTUALLY FUNCTIONING.
[quote] A set of software bugs on HealthCare.gov had, for more than six weeks, prevented individual insurance company websites and web brokers including ehealthinsurance.com, getinsured.com and GoHealthInsurance.com from interfacing with the federal site to verify enrollee’s subsidy eligibility. That lack of so-called “direct enrollment” had undoubtedly played a role in what has been abysmally low levels of enrollment in Obamacare insurance.
(Read more: Low-bamacare enrollment)
“We do believe the the majority of the fixes for direct, online enrollment are addressed,” said CMS spokeswoman Julie Bataille. She said that “in coming days,” as insurers and online brokers make their own assessments of their systems, they could begin enrolling people.
EHealth spokesman Nate Purpura said, “We are still in the process of confirming that the fixes have been made that will provide a stable and consumer-friendly user experience. Once we have more information, we can provide further comment.”
Chini Krishnan, CEO of GetInsured, said, “We are close to completing this lap.” [/quote]
I’m sure those right-wing cyberterrorists also inserted the bugs in the Obamacare code. You know, because RACISM!!!