<div dir="ltr"><div><div><div>Mark,<br></div>I'm pretty sure I get your point. I'm not obtuse. We just don't agree and I'm happy we leave it there.<br><br></div>Kind regards<br><br></div>Paul Wilkins<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 May 2016 at 12:51, Mark Smith <span dir="ltr"><<a href="mailto:markzzzsmith@gmail.com" target="_blank">markzzzsmith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><p dir="ltr"><br>
On 4 May 2016 12:07 PM, "Paul Wilkins" <<a href="mailto:paulwilkins369@gmail.com" target="_blank">paulwilkins369@gmail.com</a>> wrote:<br>
><br>
> Yes, but this is not Russia.<br></p>
</span><p dir="ltr">You've missed the point entirely, and I've spent enough time trying to explain it.<br><br></p><div class="HOEnZb"><div class="h5">
<p dir="ltr">> The sites they will want blocked will either be illegal content (child pornography, terrorism related) or phishing sites. In both cases, the security services are quite entitled to terminate the service as a criminal enterprise. The point being not to firewall out the content (which is not achievable), but to prevent inadvertent access - eg. <a href="https://www.xn--ba-3ia.com.au" target="_blank">https://www.ÇBA.com.au</a>. After that, perps cannot claim they were browsing <a href="https://www.12yovirgins.com" target="_blank">https://www.12yovirgins.com</a> by accident.<br>
><br>
> Kind regards<br>
><br>
> Paul Wilkins<br>
><br>
> On 4 May 2016 at 08:25, Mark Smith <<a href="mailto:markzzzsmith@gmail.com" target="_blank">markzzzsmith@gmail.com</a>> wrote:<br>
>><br>
>><br>
>> On 2 May 2016 7:16 PM, "Paul Wilkins" <<a href="mailto:paulwilkins369@gmail.com" target="_blank">paulwilkins369@gmail.com</a>> wrote:<br>
>> ><br>
>> > Mark,<br>
>> > I'm glad you raised the point, as it needs to be clarified that the purview of the s313 inquiry is "disruption" of services. It's not required to read the data stream. For the purposes of s313 it should be sufficient to read the SSL certificate, and then block by either white list or black list.<br>
>> ><br>
>><br>
>> You're assuming that the entire HTTPS website's content is "prohibited", so this censorship can be implemented at a certificate granularity. Incorrect assumption.<br>
>><br>
>> "Russia blocks Wikipedia"<br>
>> <a href="http://www.businessinsider.com.au/wikipedia-blacklisted-in-russia-2015-8?r=US&IR=T" target="_blank">http://www.businessinsider.com.au/wikipedia-blacklisted-in-russia-2015-8?r=US&IR=T</a><br>
>><br>
>><br>
>> > John,<br>
>> > For better or worse, we're heading to a future where SSL will not be banned, but it will be licensed. This in my view is what's driving the ongoing spat between the FBI and Apple.<br>
>> ><br>
>> > Kind regards<br>
>> ><br>
>> > Paul Wilkins<br>
>> ><br>
>> > On 2 May 2016 at 13:49, Mark Newton <<a href="mailto:newton@atdot.dotat.org" target="_blank">newton@atdot.dotat.org</a>> wrote:<br>
>> >><br>
>> >> On May 2, 2016, at 1:41 PM, John Lindsay <<a href="mailto:johnslindsay@mac.com" target="_blank">johnslindsay@mac.com</a>> wrote:<br>
>> >><br>
>> >> > This is easy. Just ban ssl. Sorted.<br>
>> >><br>
>> >> Sure, they can do that, and we’ll all keep using it. Maybe we’ll rename it “TLS” so we don’t have to tell them that their ban has been unsuccessful.<br>
>> >><br>
>> >> - mark<br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> AusNOG mailing list<br>
>> >> <a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
>> >> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
>> ><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > AusNOG mailing list<br>
>> > <a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
>> > <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
>> ><br>
><br>
><br>
</p>
</div></div></blockquote></div><br></div>