|
|
Log in / Subscribe / Register

Security

Intel processors and DRM

There has been a persistent round of rumors stating that upcoming Intel processors come with an additional, unwelcome feature: hardware digital restrictions management (DRM) capabilities. According to some, this built-in DRM is the motivating force behind Apple's just-announced switch to Intel processors. If Intel is to be believed, the reality of the situation is not as bad as one might fear.

According to Donald Whiteside, an Intel VP, there is no secret DRM in Intel's chips:

The rights management technology referred to in the article was not a secret DRM from Intel, but the DTCP-IP technology publicly offered by the 5C Entity; which Intel is a Founder. Intel believes that the DTCP-IP technology is an important element in enabling protected transport of compressed content within the home network, and we continue to promote DTCP-IP for this application which enables greater consumer flexibility & use of premium entertainment content.

The DTCP web site has some information on this technology - though one must pay significant money and sign some highly restrictive documents to get the full scoop. Essentially, DTCP is a way for devices to talk over local links - an IEEE1394 connection or home wireless network, for example - without creating fears that somebody's Valuable Intellectual Property will leak out into the world and bring an end to civilization. It's a fairly straightforward combination of encryption and remote attestation protocols.

Essentially, a DTCP-enabled device has, buried within it, a signed certificate identifying it as being approved by the powers that be. When two such devices communicate, they send challenges and check certificates to ensure that they are both approved; if the authentication step fails, no content will be exchanged. Assuming the authentication succeeds, encrypted content can be sent in one direction or the other; this content includes a set of flags specifying the rules which are to apply to the copying of that content. Anybody who makes an approved device must, of course, promise to implement those rules.

The DTCP designers have not left things to chance; each device includes within it a "revoked certificates" list. When somebody's gadget is shown to be insufficiently attentive to the restrictions applied to Valuable Intellectual Property, its certificate can be added to that list. Every device, and every piece of content as well, carries a copy of the list, and devices will update their list when a newer version comes along. So your compromised video player may well make copies for a while, until you bring in a disk with a new revocation list; after that, none of your other gadgets will talk to it any more.

It is still not clear what features Intel has added to its chips to support DTCP. It is unlikely to be anything which will be useful to Linux users. But, at least, it does not appear to be a system to lock "unauthorized" operating systems out of the processor. And certainly none of us expected any sort of free multimedia software to get a stamp of approval from the entertainment industry anyway.

Comments (9 posted)

Brief items

Schneier: Attack Trends: 2004 and 2005

Bruce Schneier has posted some predictions on the types of security problems we'll see in the near future. "Targeted worms are another trend we're starting to see. Recently there have been worms that use third-party information-gathering techniques, such as Google, for advanced reconnaissance. This leads to a more intelligent propagation methodology; instead of propagating scattershot, these worms are focusing on specific targets. By identifying targets through third-party information gathering, the worms reduce the noise they would normally make when randomly selecting targets, thus increasing the window of opportunity between release and first detection."

Comments (1 posted)

New vulnerabilities

dbus: information disclosure

Package(s):dbus CVE #(s):CAN-2005-0201
Created:June 8, 2005 Updated:August 30, 2005
Description: From the Red Hat alert: "Dan Reed discovered that a user can send and listen to messages on another user's per-user session bus if they know the address of the socket." At current usage levels, this vulnerability is not particularly threatening.
Alerts:
Fedora FEDORA-2005-822 dbus 2005-08-29
Ubuntu USN-144-1 dbus 2005-06-27
Mandriva MDKSA-2005:105 dbus 2005-06-24
Red Hat RHSA-2005:102-01 dbus 2005-06-08

Comments (none posted)

Dzip: directory traversal

Package(s):dzip CVE #(s):
Created:June 6, 2005 Updated:June 8, 2005
Description: Dzip is vulnerable to a directory traversal attack when extracting archives. An attacker could exploit this vulnerability by creating a specially crafted archive to extract files to arbitrary locations.
Alerts:
Gentoo 200506-03 dzip 2005-06-06

Comments (none posted)

kdbg: command injection vulnerability

Package(s):kdbg CVE #(s):CAN-2003-0644
Created:June 2, 2005 Updated:June 8, 2005
Description: Versions of the kdbg debugger from 1.1.0 through 1.2.8 have a problem with permission checking in the .kdbgrc run command file. A local user may use this to inject malicious commands in the file.
Alerts:
Red Hat RHSA-2005:416-01 kdbg 2005-06-02

Comments (none posted)

kernel: local denial of service, possible compromise

Package(s):kernel CVE #(s):CAN-2005-0756 CAN-2005-1265
Created:June 8, 2005 Updated:June 9, 2005
Description: The mmap() system call does not perform proper checking of its parameters, leading to a possible kernel crash and possible code execution.

The ptrace() system call does not perform proper checking of addresses (on the x86-64 platform only), leading to a possible kernel crash.

Alerts:
SuSE SUSE-SA:2005:029 kernel 2005-06-09
Ubuntu USN-137-1 kernel 2005-06-08

Comments (none posted)

Mailutils: SQL injection

Package(s):mailutils CVE #(s):CAN-2005-1824
Created:June 6, 2005 Updated:June 8, 2005
Description: When GNU Mailutils is built with the "mysql" or "postgres" USE flag, the sql_escape_string function of the authentication module fails to properly escape the "\" character, rendering it vulnerable to a SQL command injection. A malicious remote user could exploit this vulnerability to inject SQL commands to the underlying database.
Alerts:
Gentoo 200506-02 mailutils 2005-06-06

Comments (none posted)

Wordpress: multiple vulnerabilities

Package(s):wordpress CVE #(s):
Created:June 6, 2005 Updated:July 4, 2005
Description: Due to a lack of input validation, WordPress is vulnerable to SQL injection and XSS attacks. An attacker could use the SQL injection vulnerabilities to gain information from the database. Furthermore the cross-site scripting issues give an attacker the ability to inject and execute malicious script code or to steal cookie-based authentication credentials, potentially compromising the victim's browser.
Alerts:
Gentoo 200507-02 wordpress 2005-07-04
Gentoo 200506-04 wordpress 2005-06-06

Comments (none posted)

Page editor: Jonathan Corbet
Next page: Kernel development>>


Copyright © 2005, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds