, 2003-01-13
Why I should have the right to kill a malicious process on your machine.
Expand all |
Post comment
Strikeback, Part Deux
2003-01-13
Chris Caydes (2 replies)
Chris Caydes (2 replies)
Strikeback, Part Deux
2003-01-13
Stealthbadger (2 replies)
Stealthbadger (2 replies)
The Self-Defense Argument is flawed... Strikeback, Part Deux
2003-01-14
Shawn Duffy (5 replies)
Shawn Duffy (5 replies)
Give me a break... Strikeback, Part Deux
2003-01-13
Shawn Duffy (7 replies)
Shawn Duffy (7 replies)
Give me a break... Strikeback, Part Deux
2003-01-14
Anonymous (5 replies)
Anonymous (5 replies)
Give me a break... Strikeback, Part Deux
2003-01-14
Shawn Duffy (3 replies)
Shawn Duffy (3 replies)
Isn't this like smacking the neighbor's kid for mouthing off?
2003-01-14
Anonymous (7 replies)
Anonymous (7 replies)
No, it's like shooting your neighbor's dog who ruthlessly attacking someone.
2003-01-15
P. Hofmeister (1 replies)
P. Hofmeister (1 replies)
Strikeback, Part Deux
2003-01-20
Anonymous (1 replies)
Anonymous (1 replies)
Strikeback, Part Deux
2003-01-20
Anonymous (1 replies)
Anonymous (1 replies)
Strikeback, Part Deux
2003-01-21
Anonymous (2 replies)
Anonymous (2 replies)

1. Do a Google search on "Defense of Personal Property," there are legal precedents even there.
2. There is no reliable legal recourse to an "attack" of this nature.
3. Going with the author's argument a bit, if there is no attacker, if it's more along the lines of an out-of-control vehicle crashing into your front door, you are perfectly justified in reaching into the vehicle and turning it off.
4. The problem with using the self-defense analogy that I should have seen earlier: It doesn't take into account that the attack from the running process is not a single, discrete event, it's a continuous barrage. I don't know if this would work for corporations (depending on how the judge feels about Santa Clara County v. Southern Pacific Railroad Company), but Castle Law provides explicitly for standing your ground in your home if you can not evade the attack. Yes, you can block the flow of traffic from upstream, but the attack is *still* going on and *still* consuming bandwidth, which is a quantifiable "injury."
I'll have to have more coffee and think about it.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/134/17723#17723