<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body>
Daniel Thor Kristjansson wrote:<br>
<br>
<span style="white-space: pre;">> Yes, enabled but encrypted. Same
FCC order both allows the cable <br>
> operator to encrypt over-the-air channels and requires them to<br>
> provide firewire out for customers that request it. So you'll have<br>
</span>You've got to be shitting me. Whats the point in requiring them
to make the port available if they can encrypt the content that spews
forth from it?<br>
<br>
I have a huge beef w/ all this encryption crap. They encrypt it so an
extreamly small percentage of people can't what. . . Post it on
kazaa? There will *always* be a way to get the content off just about
any device. But, I'm probably preaching to the choir. . .<br>
-dan<br>
<span style="white-space: pre;">> firewire out, but unless you have
a relationship with the cable<br>
> operator's encryption provider (Motorola, Atlanta Scientific, or<br>
> Cable Labs) you won't get access to the feed. All of them require<br>
> NDA's which disallow open source development and the first two
charge<br>
> an arm and a leg for access to the documentation. I think they are<br>
> hoping Cable Lab's OCAP will take off and HDTV monitor makers will<br>
> sign up for access.<br>
> <br>
> OCAP uses a PCMCIA card to do all the decryption so you would rent
a <br>
> PCMCIA key for each of your OCAP capable TV's from the cable
company <br>
> that would allow the TV to show cable content sent over the
firewire <br>
> port. Your cable tuner or OCAP PVR would also need a PCMCIA key.<br>
> <br>
> -- Daniel<br>
<br>
</span>
</body>
</html>