<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Would the argument more-so go negligence vs actual liability - i.e.
if I put a open wifi access point in the middle of town, no logging,
no monitoring, no filtering, and it was used to circulate
questionable, child endangering, content, then I'd imagine
punishments would be much harsher than if it was secured by a ToS
splash page, some logging and category filtering, which the user
then circumvented (thus breaking the ToS they agreed on) pushing
liability back to them, and covering yourself for negligence?<br>
<br>
I'm not a lawyer by any sense of the meaning so probably completely
wrong - but that would be my take on it.<br>
<br>
<div class="moz-cite-prefix">On 08/10/14 11:37, Damien Gardner Jnr
wrote:<br>
</div>
<blockquote
cite="mid:CAPrfDLWQrWWRoB784i=wnm9CiLKg8r5tzdFSy9nE-ffCVw51BQ@mail.gmail.com"
type="cite">
<div dir="ltr">Re Liability of the provider, I'd be concerned that
if you DO make an effort to filter, and then someone manages to
get questionable content up (as in porn, not as in the awesome
cartoon), whether you are then accepting liability for the
person being able to get to that content?
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 8 October 2014 11:33, Skeeve Stevens
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:skeeve+ausnog@eintellegonetworks.com"
target="_blank">skeeve+ausnog@eintellegonetworks.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">In my view, Filtering in this scenario is
less about what the user can access, but more about the
liability on the provider.
<div><br>
</div>
<div>IMHO, Filtering should be mandatory in public access
areas. We generally use Juniper SRX's with Websense
backend and harsh category selection.</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">
<div><br>
...Skeeve</div>
<div><br>
</div>
<div>
<div><b style="font-size:13px;font-family:Calibri">Skeeve
Stevens - </b><span
style="font-size:13px;font-family:Calibri">eintellego
Networks Pty Ltd</span></div>
<div>
<div><span
style="font-family:Calibri;font-size:13px"><a
moz-do-not-send="true"
href="mailto:skeeve@eintellegonetworks.com"
target="_blank">skeeve@eintellegonetworks.com</a> ; <a
moz-do-not-send="true"
href="http://www.eintellegonetworks.com/"
target="_blank">www.eintellegonetworks.com</a></span><font>
<p
style="font-family:Calibri;font-size:13px;margin:0px">Phone:
1300 239 038; Cell <a
moz-do-not-send="true"
href="tel:%2B61%20%280%29414%20753%20383"
value="+61414753383" target="_blank">+61
(0)414 753 383</a> ; <a
moz-do-not-send="true">skype://skeeve</a></p>
<p
style="font-family:Calibri;font-size:13px;margin:0px"><a
moz-do-not-send="true"
href="http://facebook.com/eintellegonetworks"
target="_blank">facebook.com/eintellegonetworks</a> ; <a
moz-do-not-send="true"
href="http://linkedin.com/in/skeeve"
target="_blank">linkedin.com/in/skeeve</a> </p>
<p
style="font-family:Calibri;font-size:13px;margin:0px"><a
moz-do-not-send="true"
href="http://twitter.com/theispguy"
target="_blank">twitter.com/theispguy</a><span
style="color:rgb(0,0,0)"> ; blog: </span><a
moz-do-not-send="true"
href="http://www.theispguy.com/"
target="_blank">www.theispguy.com</a><br>
</p>
<p
style="font-family:Calibri;font-size:13px;margin:0px"><img
moz-do-not-send="true"
src="http://eintellegonetworks.com/logos/ein09.png"><br>
</p>
<p style="margin:0px"><span
style="color:rgb(127,0,127);font-family:Calibri,sans-serif;font-size:13px">The
Experts Who The Experts Call</span></p>
</font></div>
<div
style="font-family:Calibri,sans-serif;font-size:14px;color:rgb(127,0,127)"><span
style="color:rgb(0,32,96);font-size:13px">Juniper
- Cisco </span><span
style="color:rgb(0,32,96);font-size:13px">-
Cloud</span><span
style="color:rgb(0,32,96);font-size:13px"> </span><span
style="color:rgb(0,32,96);font-size:13px">-
Consulting</span><span
style="color:rgb(0,32,96);font-size:13px"> </span><span
style="color:rgb(0,32,96);font-size:13px">-
IPv4 Brokering</span></div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div>
<div class="h5">On 8 October 2014 11:05, Andrew Yager
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:andrew@rwts.com.au" target="_blank">andrew@rwts.com.au</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div>
<span>
<div>Hi,</div>
<div><br>
</div>
<div>We’re currently developing a public
internet access solution for a public space,
and one of the things we’re considering is
content filtering as part of the solution.</div>
<div><br>
</div>
<div>Obviously the usual caveats apply around
success, ability to circumvent, etc, but
given all of these caveats, what are
people’s general opinion on:</div>
<div><br>
</div>
<div>- is it a good idea to do this in a
public space (think children, families, etc
all around)</div>
<div>- what sort of filtering have you
implemented in the past? We are looking at a
solution that would do simple category
filtering at the moment, with the option to
blacklist and whitelist particular URLs</div>
<div>- what sort of categories would you
generally block?</div>
<div><br>
</div>
<div>I’m personally of the opinion that it’s a
“good idea” in this context although not
fool proof.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Andrew</div>
</span><span><font color="#888888">
<div>
<br>
-- <br>
Andrew Yager, Managing Director MACS
(Snr) CP BCompSc MCP<br>
Real World Technology Solutions Pty Ltd -
IT people you can trust<br>
ph: 1300 798 718 or (02) 9037 0500<br>
fax: (02) 9037 0591<br>
<a moz-do-not-send="true"
href="http://www.rwts.com.au/"
target="_blank">http://www.rwts.com.au/</a></div>
</font></span></div>
<br>
</div>
</div>
<span class="">_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net"
target="_blank">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
</span></blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">
<p>Damien Gardner Jnr<br>
VK2TDG. Dip EE. GradIEAust<br>
<a moz-do-not-send="true" href="mailto:rendrag@rendrag.net"
target="_blank">rendrag@rendrag.net</a> - <span><a
moz-do-not-send="true" href="http://www.rendrag.net/"
target="_blank">http://www.rendrag.net/</a><u><br>
</u></span>--<br>
We rode on the winds of the rising storm,<br>
We ran to the sounds of thunder.<br>
We danced among the lightning bolts,<br>
and tore the world asunder</p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
</body>
</html>