<font face="courier new,monospace"><br></font><br><div class="gmail_quote">On Thu, Sep 16, 2010 at 10:53 AM, drago01 <span dir="ltr"><<a href="mailto:drago01@gmail.com">drago01@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thu, Sep 16, 2010 at 4:49 PM, Jon Masters <<a href="mailto:jonathan@jonmasters.org">jonathan@jonmasters.org</a>> wrote:<br>
> On Thu, 2010-09-16 at 10:34 -0400, Fulko Hew wrote:<br>
>> On Thu, Sep 16, 2010 at 10:25 AM, Jon Masters<br>
>> <<a href="mailto:jonathan@jonmasters.org">jonathan@jonmasters.org</a>>wrote:<br>
><br>
>> > Well, the US law of the land says that you can't listen in on<br>
>> > telephone communications frequencies either. And the CFR advice and<br>
>> > FCC implementation is to require that designers of radio equipment<br>
>> > make it intentionally difficult to modify that equipment to listen<br>
>> > in on such frequencies.<br>
><br>
>> The law in Canada is/was a little different.<br>
><br>
> That's nice, but most of these manufacturers seem to be US based.<br>
<br>
</div>Its not that simple ... they have to comply with the regulatory rules<br>
of the countries they ship there products in.<br></blockquote><div><br>It just goes to show that the process is worthless,<br>because it can be circumvented in all sorts of manners.<br>Most simply by taking your laptop on your next trip outside of _your_<br>
'regulated' (where the hardware was shipped to) country.<br><br>Whats going to stop your hardware from broadcasting illegally?<br></div></div>A judge, a lawyer, a license agreement?<br><br>So in the end, it really doesn't matter where the source code,<br>
or the blob is hackable/crackable.<br><br>But lets not cloud the issue with facts. :-(<br><br>The fact is that we are currently saddled with this situation till some new<br>wireless standard can operate in a band, anywhere in the world, wit<br>
the same transmission characteristics.<br><br><br>