<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Which leads to my favorite line from the congresswoman's summary<br>
is "In addition, the bill would permit the use and sale of<br>
tools – like software apps – that enable unlocking for uses that<br>
do not infringe on copyright. " I hope it's just a firmware<br>
update for the HDHR Prime to ignore the copy protection flags on<br>
cable channels!<br>
</blockquote></blockquote>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
You could, but in all likelihood the firmware itself is<br>
copyrighted, and thus you would not be able to distribute your<br>
modified versions of it. You could (in theory) write your own<br>
clean room firmware from scratch, but then you would still have to<br>
crack the CC handshake to authorize your new firmware. If you have<br>
to deal with the handshake, you may as well do that from their<br>
open source library, rather than trying to write a whole firmware.<br>
</blockquote>
<br>
<br>
I'm not suggesting that some 3rd party create the firmware... I am<br>
saying that the good folks at Silicon Dust could legally change the<br>
firmware to ignore those flags; after all "the bill would permit the<br>
use AND SALE of tools..."<br>
</blockquote>
<br></div></div>
That would undoubtedly constitute a breach of contract, and their<br>
authentication keys would be revoked.</blockquote><div><br></div><div style>Again, I am not suggesting anyone do anything stupid. I am talking about above the board, or at least well informed change. Essentially, this bill says that consumers and commercial hardware/software, are allowed to circumvent copy protection measures to allow fair use. Now it doesn't say that content creators have to make it easy... but it also clearly indicates that they cannot go after the makers of the device/software.</div>
<div style><br></div><div style>New Paragraph:</div><div style><br></div><div style><div>7 ‘‘(3) It is not a violation of this section to use, manu-</div><div>8 facture, import, offer to the public, provide, or otherwise </div>
<div>9 traffic in any technology, product, service, device, compo-</div><div>10 nent, or part thereof that is primarily designed or pro-</div><div>11 duced for the purpose of facilitating noninfringing uses of </div><div>
12 works protected under this title by circumventing a tech-</div><div>13 nological measure that effectively controls access to that </div><div>14 work, unless it is the intent of the person that uses, manu-</div><div>15 factures, imports, offers to the public, provides, or traffics </div>
<div>16 in the technology, product, service, device, component, or </div><div>17 part to infringe copyright or to facilitate the infringement </div><div>18 of a copyright.’’</div></div><div style><br></div><div style>So upon a review of any contracts or certifications, I wonder if they could implement it without risking their ability to continue to market products... or at very least, lobby to have those contracts/certifications changed to allow use under this law.</div>
<div style><br></div><div style>Of course I am only hopeful, not confident that this could/would happen. Hell I'm not even confident that this bill will pass, but I am hopeful!</div><div style><br></div></div></div>
</div>