Note: This content is accessible to all versions of every browser. However, this browser may not support basic Web standards, preventing the display of our site's design details. We support the mission of the Web Standards Project in the campaign encouraging users to upgrade their browsers.
Thursday, September 30, 2004 16:04 // SANE 2004, RAI, Amsterdam, Nederlands // href
a presentation by Rüdiger Weis
My interpretation: TCG is basically a system for vendors who do not trust users. Even though the licenses which go with TCG enabled products with licenses that would not be valid in Europe to enforce it with hardware support. TCG 1.2 fixes some of the problems, but only some.
In principle a security infrastructure in every computer would be nice if it did not come with all the (evil) 3rd party interests and did not have all the problems still to be found in TCG 1.2.
The systems that prevent access to copyrighted songs can also be used to prevent any other documents. It would even be possible to prevent access to some documents at a later date by changing the appropriate access keys.
Imagine the copyright holder looses his keys, all copies of his work may become inaccessible.
The cryptographic foundations of TCG 1.2 stand on pretty week (new) legs cryptographically as many new methods are being employed in this system.
While TCG supports long keys of 2048 bits, it is still possible to use 512 bit keys and weak 160 bit sha-1 keys this raises questions regarding the cryptographic viability of this system.
Neat: https://www.trustedcomputing.org uses an invalid SSL certificate.
Bundesamt für Sicherheit in der Informationstechnik (www.bsi.bund.de ...)
Thursday, September 30, 2004 16:46 // SANE 2004, RAI, Amsterdam, Nederland // href
A presentation by Clifford Wolf
SubMaster is a system for distributed software development where every developer can develop on his own repository and then forward patches to a central repository. The patches received at the central repository go into a system from where their integration into the main repository can be controlled by the project maintainer using specialized tools.
With SubMaster you get a rich tool set for working in such an environment.
SubMaster uses SubVersion as its data repository but wraps it so that distributed development becomes possible.
SubMaster comes with two main scripts sm for maintaining local repositories and uploading patches and smap for applying the patches to the main repository.
Further information is available on (www.rocklinux.org ...)
Content © by Tobias Oetiker