nanog mailing list archives
Re: de-peering for security sake
From: Valdis.Kletnieks () vt edu
Date: Sat, 16 Jan 2016 21:48:38 -0500
On Sat, 16 Jan 2016 11:09:27 -0800, Owen DeLong said:
Making the owner of the host responsible for an attack -personally- responsible would require every grandma & 6 year old to have insurance before buying a laptop or Xbox. And would bankrupt your favorite startup no matter how smart & competent the first time a zero-day caught them by surprise.
Agreed⦠I think, instead, that the commercial purveyors of vulnerable software should be held liable.
And this is another one that needs *really* careful definitions. How much time does Redhat get to patch a bug in (say) OpenSSH or the kernel or any other package from upstream, before you want to hold them liable?
Attachment:
_bin
Description:
Current thread:
- Re: de-peering for security sake Richard Hesse (Jan 02)
- Re: de-peering for security sake Randy Bush (Jan 02)
- <Possible follow-ups>
- Re: de-peering for security sake Rich Kulawiec (Jan 16)
- Re: de-peering for security sake Ca By (Jan 16)
- Re: de-peering for security sake Mike Hammett (Jan 16)
- Re: de-peering for security sake Rich Kulawiec (Jan 16)
- Re: de-peering for security sake Patrick W. Gilmore (Jan 16)
- Re: de-peering for security sake Ca By (Jan 16)
- Re: de-peering for security sake Owen DeLong (Jan 16)
- Re: de-peering for security sake Valdis . Kletnieks (Jan 16)
- Re: de-peering for security sake bzs (Jan 17)
- Re: de-peering for security sake Dan Hollis (Jan 17)
- Re: de-peering for security sake Ca By (Jan 17)
- Re: de-peering for security sake bzs (Jan 17)
- Re: de-peering for security sake Doug Barton (Jan 17)
- Re: de-peering for security sake Dan Hollis (Jan 17)
- Re: de-peering for security sake bzs (Jan 17)
- Re: de-peering for security sake Valdis . Kletnieks (Jan 17)
- Re: de-peering for security sake bzs (Jan 18)
- Re: de-peering for security sake Michael O'Connor (Jan 19)
- Re: de-peering for security sake Ca By (Jan 16)