The problem with the gridlock is that it is caused by the corporate interests who have lobbied their way into virtual ownership of the elected officials. Until the problem of lobbying is addressed, the US political system will continue along its merry, gridlocked way. If you want to know who's really in power, follow the money.
Slashdot videos: Now with more Slashdot!
Nah. I'm just cognizant that cutting the pipe can put businesses out of existence is all. I don't think it helps anybody to put a business out of business. Cutting the pipe should be, IMO, the last resort to the business not getting its ducks in a row.
Obviously, the owner of compromised systems is responsible for those systems. Period, full stop. In my line of work, I'm often the hapless slouch who has to find the root kits and whatnot, cleanse the system, determine (if possible) the vector of entry, etc. Usually, the system was owned by some undetermined means and all I can do is just cleanse and lock down as much as possible. Clients, however, being the meat sacks they are, always manage to encounter PEBKAC events.
I don't think we're actually all that far apart in our line of thinking, Marc. I just am reluctant to pull the pin on their network connection until such time as the company has proven itself either unable or unwilling to address its issues. This approach is fair, I think, when dealing with individual residential and corporate connections. When you threaten upstream disconnection at the ISP level to downstream ISPs, then the collateral damage is too great for such shenanigans. Putting hundreds of companies out of business simply because they chose an ISP who allows botnet traffic to pass its borders would penalize those who are not a part of the problem. That, IMO, is unethical.
P.S. - I noticed that I spelled your name 'Mark' before. Apologies for that!
So you don't mind pulling the plug on a residential connection, but pulling one on a business connection is the line? The business should have more care in their networks than an average user. So they should be pulled much less than grandma. So I wouldn't think it that huge of an issue. Most are residential connections, aren't they?
Oh, I have just as much of an issue with pulling the plug on a residential connection because of the possibility of negatively impacting business. For example, I do the vast majority of my work from home on a non-commercial connection. Were my ISP to simply pull the plug on my connection because one of the systems began, say, sending out thousands of spam per hour, it would create a huge problem for me. (Finding/cleaning the system not itself being The Problem.)
For any long-term success, we need to find ways to take down the botnets and patch the compromised systems. ISPs disconnecting problem systems/networks does nothing to deal with the malware that creates the zombies for the botnets, nor does it take out the command and control centre that inevitably tells the zombies to attack a particular target. To me, that's the more pressing issue. As long as the botnet lives, more zombies will be recruited.
Yep. Canada has some weird rules. For example, if you have servers in a rack and the feds want to do a search and seizure a la US style, not gonna happen. If the servers are essential for the running of your business, the most the feds can do is to copy all the relevant data. They can't actually seize the servers lest it causes your business damage.
It's actually a pretty good law in that it respects the ideal of innocent until proven guilty beyond reasonable doubt. In other countries, they can just take your crap and if you go out of business because of it - even if you're totally innocent - well, that's just tough luck, innit?
This is getting to become a circular argument, and I'm in no mood to argue. I cannot be more clear: One cannot simply 'pull the plug' on a network that provides service without opening up a complex can of legal worms. There's absolutely _zero_ doubt that DDoS activity is malicious by nature and intent by the botnet operator. There's absolutely _zero_ doubt that pulling the plug would help mitigate the damage to systems on the receiving end of attacks from such compromised systems/network. The fundamental problem, however, is that one does not merrily obstruct a business's capacity to DO business without incurring legal ramifications (dependent upon the jurisdiction in which the service is being hosted/operated).
It is what it is, Mark. It's a simple problem with a veritable rat's nest of legal implications to solve.
Happy New Year to you, sire.
It's trivial to cut off service, yes, but if an ISP and upstream providers to cut off all offending networks from access, the internet would pretty much go silent.
I think that's exactly why it's necessary. Most ISPs take very little notice of an obviously infected customer's machine, unless of course it's trying to pour its spam through their SMTP server. Then they immediately get their panties in a twist and pull your plug until you clean up your machine.
The difference here of course being who is the victim. You or me? Not gonna bother. US? Red Alert Ban Hammer Time!
So, your upstream pulling (or threatening to pull) your plug is precisely what's needed to motivate those ISPs. Some are lazy. Most are just too cheap to invest in fixing the problem and would rather bank the dollars than spend them to fix "someone else's problem". Make it their problem. Light a fire under their seat and watch them redirect a processes they already have in place, to fix the problem.
I think we're all in agreement that something needs to be done, but the ethics of disrupting a business's capacity for staying in business is shaky ground. In all of this, I'm certainly not defending the problem, merely discussing the complications associated with cleaning up the problem. In my case, I'm very proactive about making sure the SOHO networks and servers (including multi-tenant web servers) stay clean and patched such that they don't create problems. It's a never-ending story, too.
A typical problem scenario for a hosting provider, for example, is somebody's CMS gets hacked for whatever reason and the server becomes a malware distributor or starts sending out truckloads of spam. It's mindlessly trivial to cut off that customer's account until such time as they get their house in order. Do that in certain jurisdictions, however, and you risk a law suit in case the customer can prove that their capacity to operate their business was damaged by YOUR actions.
It just IS NOT as simple as you and AK Mark would like to see it. One doesn't just walk into Mordor . Oops. Wrong metaphor.
A compromised system that is operating without the knowledge of its owner does not constitute malicious activity. Malicious activity, by its very definition, is intentional.
So the Botnet owner isn't doing anything malicious when they perform a DDoS? Again, I think your logic is contrived and quite stupid, trying to defend negligent users who are financing attacks.
I said that the DDoS is malicious activity, and the connection is linked to that, and thus can be shut down. You are disagreeing. That makes you dumb or a liar. Which is it?
It amazes me how many people defend compromised computers and those performing DDoSs.
It occurs to me that reading comprehension may not be your strong suit. I have yet to see a single comment here that defends compromised computers or DDoS. Please, try not to pretend to be so dense. The issue of malicious intent has nothing whatsoever to do with the botnet operator and everything to do with the owner of the compromised computer(s)/network. You seem to be confusing the legality and morality of the perp with that of an ignorant owner/operator. Yes, the DDoS is malicious activity. Nobody that I have seen is arguing that point. Being on the wrong end of a DDoS is damaging and disruptive. That said, there ARE ramifications of simply turning off the tap that are not so simply dealt with as you seem to wish were the case. Were it so easy and legally simple, it already would not be an issue, IMO.
Because crime is common, it would be cheaper and easier to abolish the police and stop trying to fix things.
Nope, that's fucked up logic I'll never buy into.
That's not a logical rejoinder to my comment. I did not state that nobody should try to fix things, I merely stated that cutting off traffic is unlikely to happen for a number of reasons. The cutting off traffic only masks the symptoms, it does not deal with the cause of the DDoS. A holistic approach is required, not an allopathic one, IMO.
Most contracts will allow termination of service for malicious activity.
A compromised system that is operating without the knowledge of its owner does not constitute malicious activity. Malicious activity, by its very definition, is intentional. In certain jurisdictions, Canada comes to mind, it is illegal for processes to make it impossible for a company to do business. So, if an online presence would suffer financial damage or possibly go out of business through having its service cut off, the ISP has no legal ground by which to cut off service.
Besides, as has been described elsewhere, the amount of traffic generated by any individual botnet member is generally limited to the degree that only deep packet inspection will discover it. That opens up a whole different can of legal worms with regard to privacy. If a carrier is precisely that under the letter of law, deep packet inspection and preemptive disruption of service contradict the rules of Common Carriage. A telecommunications carrier cannot follow common carrier regulations while censoring traffic.
ISPs can cut off offenders trivially. Upstream providers can cut off offending ISPs trivially.
The problem here is that compromised systems are pretty much everywhere. I take care of a number of SOHO networks and have had to clean up mess after mess over the years. Drive-by exploits, phishing, worms, etc. are all vectors of infiltrating a network. DDoS and spam are widespread. It's trivial to cut off service, yes, but if an ISP and upstream providers to cut off all offending networks from access, the internet would pretty much go silent.
Short answer: It ain't gonna happen. Local administrators have the task of keeping their own backyard clean. Beyond that, good luck educating the average home user not to click on that supposed love letter from an admirer, not install that free software from some random web site they found on Google, not give out their password to tech support contacting them via e-mail, etc., etc.
In addition to your excellent points, SpaceX made history by being the first private spacecraft to berth with the ISS. NASA and SpaceX have a very complementary collaboration schedule in place. The cost-competitiveness of SpaceX's programs will make for a long-term paradigm shift in space exploration and commercial ventures for the private sector.
If the point of open office or cubicle is to promote sharing and collaboration, he just killed that idea right there.
Having to block out sights and sounds is not a good compromise, it's a symptom of a horribly designed workplace.
Ever tried to speak with someone with earplugs and listening to music?
Sharing and collaboration is easily accomplished by poking one's head around the corner and making eye contact. It shouldn't be necessary for a person to be subjected to incessant background noise/talk for there to be the possibility of collaboration. One's presence is enough. To that end, I mostly telework now, making sure that my Skype is always on for those who require my immediate attention. I'm a huge fan of video conferencing, too, which goes a long way to ensuring that things aren't lost in translation. Interestingly, I find others very quick to shoot down even turning on video during a call. I find that often seems to lead to misunderstandings and increased difficulty during communication.
I'm Canadian, but I've lived abroad so long that I have adopted various idiosyncrasies from other languages/cultures.
Sure you don't mean, "I have foreign nationality, but I've been a resident of Japan for so long that..."?
I surely mean that my English is peppered with American slang, Britishisms, Aussie snarks and all manner of other borrowed '-isms' from living and travelling abroad. To varying degrees, I speak English, Japanese, German and French. My sense of language is no longer defined by Canadian English. I spent some years as a technical rewriter at Fujitsu, which used American English as its baseline for grammar, spelling and punctuation. It damaged my native Canadian English sensibilities. When you combine that with my tendency to include loan words and phrases from various other dialects and languages, it leads to confusion in language identity.
Personally, I find it fascinating. We really do mirror our life experiences.