User: Password:
|
|
Subscribe / Log in / New account

driver and device reliability authentication and DRM monoopolisation

driver and device reliability authentication and DRM monoopolisation

Posted Jul 22, 2003 17:43 UTC (Tue) by iabervon (subscriber, #722)
In reply to: driver and device reliability authentication and DRM monoopolisation by copsewood
Parent article: 2003 Kernel Summit: High Availability

I disagree; I think that it would be pretty easy to add support for signed code. Of course, you could just turn it off, but users who want to use signed code wouldn't do that. Signing could be done by anyone, and the users could be made aware in this way of who has tested the code on what; you don't really need decentralized trust in such an application, because customers who want this sort of thing are generally getting support for somebody, trust them, and will ask them to verify anything else they might use. (Or they might have a testing environment themselves, and sign code which passes, and only allow signed code in production).


(Log in to post comments)

Isn't that what we use?

Posted Jul 31, 2003 16:20 UTC (Thu) by job (guest, #670) [Link]

But, we already have that!

Drivers for Linux must pass a quite rigorous quality test to become an official driver. Those are signed and distributed together, through the official channels.


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