El Pollo Diablo REACHED THE END OF CAKE | aspegic500mg a écrit :
"Tout le probleme c'est le choix" Tout pendant qu'il y'a des alternative à ses produits (ex: linux, mac, openOffice, mozilla, etc etc..), Microsoft laisse les particuliers en paix et n'augmente pas -trop- ses prix. Si cette salope de paladium passe et que dans plusieurs années on a pu le choix, ca sera la mort de l'informatique car on ne pourra meme plus créer un programme (donc develloper un logiciel alternatif) qui fonctionne(car il faudra le faire certifier auprés de Microsoft, et le tarif de ce service est fixé de telle manière que seul ses partenaires commerciaux puisse le faire), donc on payera toutes nos licences (qui auront doublé de prix) et on pourra plus rien faire (en + d'ici ca on aura bien une super-LEN pour agrémenter tout ca )
|
Tout ceci est tres gentil, mais completement faux.
Palladium et le TCPA n'ont pas pour but de t'empecher d'installer ce que tu veux sur ta machine, mais de t'empecher de faire ce que tu veux avec du contenu protégé que tu pourrais avoir (fichier audio protégés, film achetés en ligne...), et dans une moindre mesure mais quand meme de controller un peu plus ce qui tourne sur ta machine.
Rien n'empechera d'installer un linux ou autre sur un PC TCPA compliant, rien n'empeche non plus aux communatés du libre de participer a l'elaboration de tout plutot que de tout rejeter en bloc, rien n'empechera d'utiliser le soft que tu veux ou de lire tes divx et mp3 sur le prochain windows.
Le danger n'est pas la, le vrai danger est que sous couvert de faire valoir leurs droits les "fabriquants" de cutlure en limite l'usage qu'on puisse en faire par rapport a aujourd'hui, dans le but de nous faire payer a tous les etages, et c'est pas Microsoft dont il faut avoir le plus peur dans ce domaine, loin de la... http://www.microsoft.com/technet/s [...] ngscb.mspx
Citation :
Q: What is the privacy model associated with NGSCB?
A: Users are always in control of whether nexus-aware technology is enabled on their PC and what nexuses have access to specific functions. The technology being developed as part of NGSCB provides a fine-grained access control model that allows users to specify (by hash) whether a given nexus has the right to invoke a specific security operation. In addition, SSC functions that reveal potentially machine-identifying information, such as the RSA public key, can only be performed once per SSC reset (and the SSC cannot be reset from software; the user must power-cycle the PC).
|
Citation :
Q: I have heard that NGSCB will force people to run only Microsoft-approved software.
A: This is simply not true. The nexus-aware security chip (the SSC) and other NGSCB features are not involved in the boot process of the operating system or in its decision to load an application that does not use the nexus. Because the nexus is not involved in the boot process, it cannot block an operating system or drivers or any nexus-unaware PC application from running. Only the user decides what nexus-aware applications get to run. Anyone can write an application to take advantage of new APIs that call to the nexus and related components without notifying Microsoft or getting Microsoft's approval.
It will be possible, of course, to write applications that require access to nexus-aware services in order to run. Such an application could implement access policies that would require some type of cryptographically signed license or certificate before running. However, the application itself would enforce that policy and this would not impact other nexus-aware applications. The nexus and NCAs isolate applications from each other, so it is not possible for an individual nexus-aware application to prevent another one from running.
|
Citation :
Q: How can anyone be sure that the nexus and related components do exactly what you claim they do?
A: Microsoft will make widely available for review the source code of the trusted computing base so it can be evaluated widely and validated.
|
Citation :
Q: Will other software products still run on machines with the TPM?
A: Yes. If the software runs on systems today, it is very likely that it will continue to run on systems with a TPM.
|
Citation :
Q: Will I still be able to play MP3s on my PC with NGSCB?
A: You will. NGSCB will not interfere with the operation of any program that runs on current PCs. The nexus and nexus computing agents are designed never to impose themselves on processes that do not request their services; nexus-related features must be explicitly requested by a program. So the MP3 player a user has today should by design still work on a next-generation PC tomorrow.
|
Citation :
Q: Can Linux, FreeBSD or another open source operating system run on hardware developed for the NGSCB architecture?
A: Virtually anything that runs on a Windows-based machine today will still run on a NGSCB machine (there are some esoteric exceptions*; a user with a machine that currently runs both Linux and Windows would be able to have that same functionality on an NGSCB machine).
Q: Could Linux, FreeBSD or another open source operating system create a similar trust architecture?
A: From a technology perspective, it will be possible to develop a nexus that interoperates with other operating systems on the hardware of a nexus-aware PC. Much of the NGSCB architecture design is covered by patents, and there will be intellectual property issues to be resolved. It is too early to speculate on how those issues might be addressed.
|
Citation :
Q: Some people have claimed that running the Windows operating system with the nexus will enable Microsoft or other parties to detect and remotely delete unlicensed software from my PC. Is this true?
A: This is not true. NGSCB does not include mechanisms that delete or disable any content or file that currently runs on a PC. In fact, the NGSCB architecture is built on the premise that no policy will be imposed that is not approved by the user. Microsoft is firmly opposed to putting "policing functions" into nexus-aware PCs and does not intend to do so. A machine's owner, whether an individual or enterprise, has sole discretion to determine what programs run on the nexus-aware system. Programs that run under nexus-aware systems, just like programs that run under Windows, will do whatever they are allowed to do, based on the security settings on the user's machine. NGSCB not only respects existing user controls, it strengthens them.
As stated earlier, the function of the nexus, NCAs and related components is to make digitally signed statements about code identity and to protect secrets from other nexus-aware applications and regular Windows kernel- and user-mode spaces. Enhancements to the Windows operating system introduced as part of NGSCB do not have any features that make it easier for an application to detect or delete files.
|
|