<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>RE: Compromised machines liable for damage? </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>If you want to choke off freeware(gnu, et. Al), sure, go after them. I doubt the licensing agreement allows it though. (IANAL).<BR>
<BR>
I think all you'd do is encourage people to write more music about 'freeing the software'. I'd rather not be stricken in that fashion.<BR>
<BR>
I think that angle is DOA.<BR>
<BR>
Martin<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Joseph Jackson [<A HREF="mailto:jjackson@aninetworks.com">mailto:jjackson@aninetworks.com</A>]<BR>
Sent: Mon Dec 26 03:13:02 2005<BR>
To: Hannigan, Martin<BR>
Cc: NANOG<BR>
Subject: RE: Compromised machines liable for damage?<BR>
<BR>
What about the coders that write the buggy software in the first place?<BR>
Don't they hold some of the responsibility also? IE I am running some<BR>
webserver software that a bug is found in it. Attackers use that bug in the<BR>
software to generate a DOS attack against you from my machines. No update<BR>
has been released for the software I am running and/or no warning as been<BR>
released. You sue me I sue the coders. What a wonderful world. (I'm not<BR>
for this but its another side of the issue.)<BR>
<BR>
<BR>
<BR>
_____ <BR>
<BR>
From: owner-nanog@merit.edu [<A HREF="mailto:owner-nanog@merit.edu">mailto:owner-nanog@merit.edu</A>] On Behalf Of<BR>
Hannigan, Martin<BR>
Sent: Sunday, December 25, 2005 9:22 PM<BR>
To: Steven M. Bellovin<BR>
Cc: Dave Pooser; NANOG<BR>
Subject: Re: Compromised machines liable for damage?<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Yes, I agree. As usual, I too am 'IANAL'.<BR>
<BR>
Marty<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Steven M. Bellovin [<A HREF="mailto:smb@cs.columbia.edu">mailto:smb@cs.columbia.edu</A><BR>
<<A HREF="mailto:smb@cs.columbia.edu">mailto:smb@cs.columbia.edu</A>> ]<BR>
Sent: Sun Dec 25 23:52:27 2005<BR>
To: Hannigan, Martin<BR>
Cc: Dave Pooser; NANOG<BR>
Subject: Re: Compromised machines liable for damage?<BR>
<BR>
In message<BR>
<80632326218FE74899BDD48BB836421A033001@Dul1wnexmb04.vcorp.ad.vrsn.c<BR>
om>, "Hannigan, Martin" writes:<BR>
<BR>
><BR>
>Dave, RIAA wins almost 100pct vs p2p'ers ir sues. Its an interesting =<BR>
>dichotomy.<BR>
><BR>
<BR>
"Wins" is too strong a word, since I don't think any have gone to<BR>
court -- see<BR>
<A HREF="http://www.nytimes.com/aponline/arts/AP-Music-Download-Suit.html">http://www.nytimes.com/aponline/arts/AP-Music-Download-Suit.html</A><BR>
<<A HREF="http://www.nytimes.com/aponline/arts/AP-Music-Download-Suit.html">http://www.nytimes.com/aponline/arts/AP-Music-Download-Suit.html</A>><BR>
as my source.<BR>
<BR>
Besides, it's a very different situation. For my take on liability<BR>
issues -- note that I'm not a lawyer, and note that this is from 1994<BR>
-- see <A HREF="http://www.wilyhacker.com/1e/chap12.pdf">http://www.wilyhacker.com/1e/chap12.pdf</A><BR>
<<A HREF="http://www.wilyhacker.com/1e/chap12.pdf">http://www.wilyhacker.com/1e/chap12.pdf</A>><BR>
<BR>
--Steven M. Bellovin, <A HREF="http://www.cs.columbia.edu/~smb">http://www.cs.columbia.edu/~smb</A><BR>
<<A HREF="http://www.cs.columbia.edu/~smb">http://www.cs.columbia.edu/~smb</A>><BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>