Full Disclosure mailing list archives

RE: Wi-fi. Approaching customers


From: "Soderland, Craig" <craig.soderland () sap com>
Date: Tue, 15 Mar 2005 22:41:10 +0100

Now here's the .90 cent question: 

If ISP's are not liable for the content across them, and cannot be held
liable. 

And you run an Open WIFI network... 

Aren't you in effect an ISP Albeit a free one? 

And if you are an ISP, then wouldn't you, not be liable for content sent
across your network. 




------------------------------------------------------------------

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- Benjamin Franklin

-----Original Message-----
From: full-disclosure-bounces () lists grok org uk
[mailto:full-disclosure-bounces () lists grok org uk] 
Sent: Tuesday, March 15, 2005 4:28 PM
To: full-disclosure () lists grok org uk
Subject: Re: [Full-disclosure] Wi-fi. Approaching customers

Matthew Sabin wrote:

My company has made a conscious decision to leave our WiFi open to
visitors, while our internal machines connect via IPSec on the open
airwaves.
A drive-by would show the open nature of our WiFi, but wouldn't
immediately tell you that we've secured our business fairly well.

but what if someone uses your unsecured network to download copyrighted 
material (just mp3s are enough :->) or to send porn?

An unsecured WiFi may have serious legal consequences.

And to come back on the original topic: These legal consequences may be 
good arguments to convince customers that they need to get their network

secured.

Ciao
Marcus

-- 
Hail Eris! Hail Discordia!
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://www.secunia.com/
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://www.secunia.com/


Current thread: