From: Steven Toth <stoth@linuxtv.org>
To: Aidan Thornton <makosoft@googlemail.com>
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Hauppauge WinTV-CI Spec
Date: Thu, 27 Mar 2008 15:57:13 -0400 [thread overview]
Message-ID: <47EBFC19.4060106@linuxtv.org> (raw)
In-Reply-To: <c8b4dbe10803271241i20990cf3j1b75c85f1f649916@mail.gmail.com>
Aidan Thornton wrote:
> On Thu, Mar 27, 2008 at 7:25 PM, Steven Toth <stoth@linuxtv.org> wrote:
>> Recap: I said I'd notify the list when the spec was released for the
>> Hauppauge CI device.
>>
>> Hello!
>>
>> http://www.smardtv.com/index.php?page=dvbci&rubrique=specification
>>
>> Looks like SmartDTV have finally got something out of the door. Put your
>> email address in their database and they'll email you the PDF with full
>> command interface describing the protocol.
>>
>> Regards,
>>
>> - Steve
>
> Hi,
>
> I'm not sure how that's relevant. It seems to be the spec for
> something called CI+, intended to prevent unauthorised systems from
> getting access to the decrypted stream coming out the CAM and ensure
> only authorised host devices can use CAMs. I expect open source
> software will be able to make use of this stuff approximately when
> hell freezes over. If this catches on, say hello to more copy
> protection and bye-bye to being able to use CAMs under Linux!
A subset of the spec will work with the CI USB device, for those that
are interested.
- Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-03-27 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 19:25 Hauppauge WinTV-CI Spec Steven Toth
2008-03-27 19:41 ` [linux-dvb] " Aidan Thornton
2008-03-27 19:57 ` Steven Toth [this message]
[not found] ` <c8b4dbe10803271428y13bd710co995e25bb9a2eb614@mail.gmail.com>
2008-03-27 21:41 ` Steven Toth
2008-04-08 13:24 ` Derk Dukker
2008-04-08 13:40 ` Steven Toth
2008-04-08 18:53 ` Luc Brosens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47EBFC19.4060106@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=linux-dvb@linuxtv.org \
--cc=makosoft@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox