Slashdot Mirror


LaGrande, TCPA, and Palladium

An anonymous reader writes "Intel's Paul Otellini gave a talk to developers where Intel's project called "LaGrande" was mentioned. This project is aimed to create a "safer computer environment", that would consist of an advanced TCPA implementation. Some of the features it has deal with physically "protected execution, protected memory, and protected storage". When talking on LaGrande, Otellini said "it's a core technology that things like the Microsoft Palladium initiative can take advantage of to build much more stable platforms.""

254 comments

  1. The scariest part by darkpenguin · · Score: 5, Insightful

    However the most negative single feature of TCPA and Palladium is the nature of Palladium and the philosophy that has driven Microsoft's development and promotion of Palladium. I think this is probably the scariest part of the whole deal. They recognize what could happen but they press forward regardless.

    1. Re:The scariest part by inode_buddha · · Score: 2, Insightful

      IMHO, the philosophy (and the reason for it) is the scariest part. In that regard, I strongly agree with you. It's just sad for me that a business this large seems to be required (by the people) to tell people what they should think.
      Not that this says anything great about American consumerism either; it simply says a lot about the mores of American consumerism. MS is not stupid; they are in business to make $$$ and those (economic) values will eventually clash with the moral values of their public as a whole. Other than that, what distinguishes this effort from earlier infosec security projects?

      (insert instant slashdot classic here)

      (think Honeywell/Orange Book) in the light of "security projects", even though the respective documents are long out of date they possibly speak volumes about the current expectations regarding information security per se.

      The part about MS that truly scares me is that they seem to be willing *and able* to twist things for mass-market consumption in the name of "security".... [1] [2]

      [1] and still sleep at night, regardless of the seeming fact that their motives could be driven more by internal American business needs than anything else.

      [2] Not that many ppl will take the trouble to d/l and read/understand copy of www.radium.ncsc.mil/pep/library/rainbow/5200.28-ST D.html

      --
      C|N>K
    2. Re:The scariest part by DopeRider · · Score: 1

      They know that they won't win in the long run. They must take as much as they can while they can.

    3. Re:The scariest part by Anonymous Coward · · Score: 0

      Well, it is not the "most negative single feature" , "Palladium" is the only feature that can be derived from all this.

      People can always make nice, clean, re-digitized copies by simply recording the analog signal humans need to sense data. Perfect coies? No. But ears don't range 0-100Khz, so any solid technique will yield better than most people can sense anyway.

      That means the ONLY thing all this crap can ever, even remotly, protect is data that only a computer can sense --> software, and ONLY software.

      And, that is what this is about -- a system for Microsoft to achive software lock-in.

  2. The sad thing is.... by Ezekiel+Zachariah · · Score: 5, Insightful

    Most people who hear about these projects don't really understand how little control or privacy these projects will leave us. As far as stable, thats just funny...These projects will not give us more stable software, just buggy software that will let us do less. Next they will be telling us about CPUs and HDs that require MS to work correctly. and I have the first coherent post on this subject :)

    --
    "/. = :)"
    1. Re:The sad thing is.... by shoppa · · Score: 4, Insightful
      These projects will not give us more stable software, just buggy software that will let us do less.

      That's the beauty of the thing. They add complexity, but the slightest bug in the complex software will probably be exploitable to make encrypted data available to "normal" (e.g. non-approved-by-the-Intel-Microsoft-hegemony) programs.

      Just like growing the government has historically added more layers of beauracracy, making the people safer from the more-massive-and-slower-moving government.

    2. Re:The sad thing is.... by jbolden · · Score: 5, Insightful

      I doubt it. In non protected mode you won't be able to decrypt the files. In protected mode the "exploiting program" will be running in a sandbox. One of the fundamentals of capacity systems (which is where the ideas behind palladium came from) "if programs can communicate they can collude".

    3. Re:The sad thing is.... by sconeu · · Score: 2

      Next they will be telling us about CPUs and HDs that require MS to work correctly.

      Sure, and I bet you'll be telling us about modem that need MS too... Oh wait, that really happened...

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    4. Re:The sad thing is.... by Reality+Master+101 · · Score: 2, Insightful

      What the hell, I'll ask you, too: Name one privacy or control that you will lose with this. Just one.

      Hint: you will be able to turn it off, since it would break backward compatibility if you couldn't.

      --
      Sometimes it's best to just let stupid people be stupid.
    5. Re:The sad thing is.... by irc.goatse.cx+troll · · Score: 2

      There are zero modems that require MS.
      However, There are modems that require a software driver, but thats far from requiring MS.
      All you need to do is make a driver for whatever platform you want, and it works fine.

      Getting way off topic here, but couldnt you use something like how mplayer loads windows codecs?
      There are existing softmodem drivers, So it could be done. You'd just have to wrap the calls right, and I think its possible to make a universal softmodem-driver-loader.

      --
      Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
    6. Re:The sad thing is.... by jbolden · · Score: 3, Insightful

      In terms of usage:

      1) Fair usage writes on media
      2) The right to copy and email many types of files on my own system
      3) The right to use international software without in running in a virtual environment (i.e. international software is unlikely to get certified)

      In terms of privacy
      Most content on my system will be registered to my name.

    7. Re:The sad thing is.... by ealar+dlanvuli · · Score: 3, Insightful

      because we all know the algorithm for discovering the private keys won't be cracked within a year...

      With that many eyes really wanting to break your encryption (basically everyone who can break encryption in the entire world) you stand no chance. I wouldn't doubt MS choses some retarded block style assignemnt method that allows you to throw out 90% of the private keys before you even begin to brute force.

      --
      I live in a giant bucket.
    8. Re:The sad thing is.... by cheezedawg · · Score: 2, Informative

      I think the sad thing is how much FUD there is about these technologies. Palladium, LaGrande, TCPA, and the like are NOT limiting technologies. All software that runs on non-Palladium systems will run on Palladium enabled hardware (like Intel's LaGrande). These technologies give developers more tools to protect data (something that is impossible without hardware support).

      how little control or privacy these projects will leave us

      The control still remains with the end user. By design, the user determines what is trusted and what is not trusted. And privacy is always protected, and that protection is backed by hardware.

      These projects will not give us more stable software, just buggy software that will let us do less

      I'm not sure where you are coming with that. Palladium will make it easier to develop secure applications- reduced complexity correlates directly with reduced bugs.

      Basically, Palladium sets out to solve the problem of protecting mobile code from a malicious host (that is, it protects software from software). Without hardware support, developers must rely on obfuscation or tamper-resistant code to completely protect their code and data (something which is provably impossible to do, btw).

      --
      "The defense of freedom requires the advance of freedom" - George W Bush
    9. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      yes it's possible, but the average linux devloper stoped caring about modems 2~4 years ago.

    10. Re:The sad thing is.... by ealar+dlanvuli · · Score: 5, Insightful

      and what happens when you can no longer turn it off?

      (the first shot is always free...)

      --
      I live in a giant bucket.
    11. Re:The sad thing is.... by Anonymous Coward · · Score: 5, Insightful

      Microsoft is a monopoly. "Trusted Office" will not run with Palladium disabled. "Trusted Mediaplayer" will not run with Palladium disabled. Same for Trusted Outlook Express, Trusted Internet Explorer, Trusted Windows, Trusted whatever. You may still be able to turn your computer physically on without enabling Palladium, but you will quickly find it is no more than a paperweight unless you enable Palladium.

      As for Linux, I wouldn't count on being able to run it in the future if Palladium continues unchecked. M$ wants a 'trusted path' to the keyboard and to the mouse - and presumably to the network too. Linux may very well lose the ability to access those devices (either through technical or through legal means), making it 100% useless.

      As for the notion that M$ would NOT abuse their monopoly powers, well I wouldn't count on that...

    12. Re:The sad thing is.... by Planesdragon · · Score: 1

      because we all know the algorithm for discovering the private keys won't be cracked within a year...

      With that many eyes really wanting to break your encryption (basically everyone who can break encryption in the entire world) you stand no chance. I wouldn't doubt MS choses some retarded block style assignemnt method that allows you to throw out 90% of the private keys before you even begin to brute force.


      Why does it need a key? Palladium-locked data isn't going to jump all around the net--it's going to stay right at home, and be accessed only by the program that wrote it.

      Sounds like an ideal security problem to me. Each program can run its own securty functions, and that'd just be on top of the SQL filesystem that doesn't respond to any query for said files unless you're the approved program...

      And MS would be foolishly lazy to make an OS-wide key be able to crack its new "trusted computing" initative. The system will no doubt be modular, scalular, and at least as secure as PGP email that never leaves your computer.

    13. Re:The sad thing is.... by cheezedawg · · Score: 3, Informative

      They add complexity, but the slightest bug in the complex software will probably be exploitable to make encrypted data available to "normal" (e.g. non-approved-by-the-Intel-Microsoft-hegemony) programs.

      Bugs in software cannot lead to protected data being divulged. The encryption key management and encryption routines themselves are implemented in hardware. The software portion of Palladium is actually pretty small, and Microsoft plans on releasing that code for public review.

      And no programs are approved by Microsoft or Intel- Palladium amounts to an API that is available for ANY developer to use without any need to certify or register that software with anybody.

      --
      "The defense of freedom requires the advance of freedom" - George W Bush
    14. Re:The sad thing is.... by Anonymous Coward · · Score: 1, Insightful

      Talk about FUD! The whole purpose of Palladium is to take control away from the user. It tells a remote machine (that is, _somebody elses_ machine) that your machine is trustworthy; that there is nobody on your end who can infringe upon their copyright - they can stop you from doing that.

      Right now, they do not have this ability. With Palladium, they do. They shift the balance of control from the local user to some corporate headquarters. You, as a user, lose those rights.

      Palladium sure makes it easier to develop secure applications. However, that security does not mean YOU (the consumer) are secured from THEM (intruders). It means THEY are secured from YOU.

    15. Re:The sad thing is.... by Anonymous Coward · · Score: 1

      The ability to copy and manipulate any data on my machine as I see fit. The ability to listen to music without restrictions. The ability to watch video without restrictions. Possibly, the ability to boot into a non-Microsoft product. Possibly, the ability to connect a non-Microsoft operating system to the network or internet.

      As for privacy: making a machine uniquely identifiable reduces privacy for the owner of that machine. He can no longer hide in a faceless, nameless crowd behind a changing IP address and a cookie-less browser - now he is known by a number that will no doubt directly link to all his Passport data; any site you browse to will know your name, email, street address, credit card numbers, and who knows what else...

    16. Re:The sad thing is.... by cheezedawg · · Score: 5, Interesting

      1) Fair usage writes on media

      - The media that will most likely be restricted is media that is not available at all right now (legally) because the media producers fear piracy. Fair usage is a pretty muddy area, anyway.

      2) The right to copy and email many types of files on my own system

      - In general, you do not lose this "right". The cases where you do lose it, it is not legal to copy the file anyway.

      3) The right to use international software without running it in a virtual environment (i.e. international software is unlikely to get certified)

      - Certified by who? The user still decides what software is trusted or not.

      About privacy:

      Each palladium system has a unique 2048 bit public/private key pair. However, the public key is protected by hardware and cannot be tracked by a third party because of a system of nonces (outside parties will never see the same public key twice for the same system). Therefore, privacy is maintained.

      --
      "The defense of freedom requires the advance of freedom" - George W Bush
    17. Re:The sad thing is.... by prepp · · Score: 1

      you must be the troll 2k , everyone I know in the security bussiness dont like this due to its implications and the people I know who are technically adept and into politics see the "1984":ish scenario coming into play.

      This is a technology that shouldnt be.

      "The control still remains with the end user. By design, the user determines what is trusted and what is not trusted. And privacy is always protected, and that protection is backed by hardware."

      er the OS (palladium) decides what is trusted , otherwise the certificates are useless, and the certificates are issued by microsoft.

      Read the documentation availible.
      and the reviews by people who know... for a minor hint on that look for palladium and cryptogram on google.

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
    18. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      The major thing wrong with palladium is that it cannot work. There is nothing stopping you from running everything inside a virtual machine which exactly emulates the palladium-protected machine. This lets everything be under your control, and all of the 'protections' can be broken trivially since you can record all input/output from the sandbox.

      Read-once cripple-ware can be installed into the sandbox, and you can monitor and record all communications it makes to the outside world. You can then revert it back to a previous state, and spoof all of that IO. When you control everything, including the virtual hardware, there is nothing they can do. There is no way for the hostile program to detect that it isn't running on a real machine.

      Now - you have to be able to install a virtual machine in order to do this... This isn't a problem. If they don't allow execution of developer-made binaries, then the platform will be useless.

      True - the virtual machine might be barred from talking to any other program on the box... Since hobby-developers might be given limited rights. However, this isn't a problem either. All you need to do is run everything inside that virtual machine. Including other versions of itself. You create one big file the size of your filesystem, and then mount a virtual filesystem inside it. The palladium-crippled hardware cannot possibly look at what you have under that layer of encapsulation. If they try to do so, it is trivial to modify the filesystem-in-a-file format.

      Basically, you can emulate a 'free' system inside the crippled system - and there is nothing they can do to prevent that. Once you have a free system (even virtually), their house of cards falls down.

    19. Re:The sad thing is.... by oconnorcjo · · Score: 2
      Most people who hear about these projects don't really understand how little control or privacy these projects will leave us.

      Actually I don't see any problem with what Intel is doing. If you are using software that you trust has your interests at heart (for me that is Linux) then you don't have to worry that your software is going to limmit you. However, if you do not trust your software or the provider of that software, then WHY ARE YOU STILL USING IT? If you give money or use software from people who you think are out to cheat you then you only have yourself to blame when it happens. Intel is adding features to thier hardware that could be used for good or bad but I only intend running software that will only utilize these features to my benefit.

      --
      I miss the Karma Whores.
    20. Re:The sad thing is.... by greenrd · · Score: 2
      Palladium-locked data isn't going to jump all around the net--it's going to stay right at home, and be accessed only by the program that wrote it.

      I thought Palladium was designed to be used for things like "digital rights management"? That is, everything from DRM-protected videos to emails that "cannot be forwarded" (easily). (That's the theory, anyway). Surely this type of DRM stuff would require moving data around the net?

    21. Re:The sad thing is.... by cheezedawg · · Score: 3, Insightful
      Not agreeing with you != troll.

      The people I know in the security business agree that the problem is impossible to solve without hardware support. If you haven't noticed, there is a huge demand for digital content, and there is a lack of supply of that content because the media companies fear piracy. This is a defensive move by Microsoft/AMD/Intel, because someday somebody was always going to find a way to allow media companies to distribute this content without fear of piracy, and that person is going to make a lot of money.

      er the OS (palladium) decides what is trusted , otherwise the certificates are useless, and the certificates are issued by microsoft.

      I have been reading the documentation available, like here where Microsoft says:
      Only the user decides what "Palladium" applications get to run. Anyone can write an application to take advantage of "Palladium" APIs without notifying Microsoft (or anyone else) or getting its (or anyone else's) approval.

      I have also been reading enough to know that most of the information out there about Palladium is untrue.
      --
      "The defense of freedom requires the advance of freedom" - George W Bush
    22. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      These projects will not give us more stable software, just buggy software that will let us do less.

      Whatever happened to protected memory maps by the CPU? Isn't this supposed to be performed by the Operating System software to make things secure? Have the fine folks in Redmond figgured out how to use this feature to its potential yet?

    23. Re:The sad thing is.... by prepp · · Score: 1

      first part is agreeable. but the second part is ... fud, all the information ive read is microsofts own and by people that know ;D
      professors and cto:s , and well as someone said there are things in pd i like and things im afraid of...

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
    24. Re:The sad thing is.... by bryston2 · · Score: 0

      Hmmm.. I did'nt know I had a "right" to infringe on someone's copyright. Oh, I forgot this is Slashdot, where AC's make up rights to suit their argument.

    25. Re:The sad thing is.... by Anonymous Coward · · Score: 0


      Hey look, it's the fucking genius kid again.

    26. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      Well, a software attack in an unsecure system could lead to a man-in-the-middle attack, that way data would be rendered completely unsecure again.

      Now look it the other way: an admin can't know what's happening with their processes. If the system is compromised by malware or viruses, how is he going to know how a process is operating, if he can't access it?

    27. Re:The sad thing is.... by archeopterix · · Score: 1
      This is a defensive move by Microsoft/AMD/Intel, because someday somebody was always going to find a way to allow media companies to distribute this content without fear of piracy, and that person is going to make a lot of money.
      The hardware required to do this would be very very expensive. Even with encrypted computer-monitor communications, there's still a possibility to rip the monitor open and record RGB signals directly from the tube (should the case be booby trapped?), not to mention videotaping the content off the screen. Of course, an ordinary user would not bother, but as with all content that can be distributed digitally one hacker is enough to cross the barrier from the DRM world to the world of unrestricted copying. This leaves us with another option - destroying the unrestricted copying world. This will not happen until most of the no-mandatory-drm PCs die off due to lack of spare parts. And of course all new PCs would have to be mandatory-drm. But this will not happen, right? Right?
      I have also been reading enough to know that most of the information out there about Palladium is untrue.
      Please share your wisdom.
    28. Re:The sad thing is.... by NortWind · · Score: 1
      I did'nt know I had a "right" to infringe on someone's copyright.

      It's not copyright infringement to rip an MP3 from a CD you bought, play it on your computer, play it on your PDA, play it in your car, or make a backup of it. It is not copyright infringement to sell a CD you bought to another individual, if you destroy any copies in your possesion. The Palladium system eliminates the possibilty of these legal uses.

    29. Re:The sad thing is.... by Sneftel · · Score: 1

      The key flaw in your argument is assuming that it is possible to emulate the architecture with a virtual machine. The whole point of Intel et al. being in on this is that processors will be "secured" as well. And you can be damn sure that Windows Media Player 12 won't be able to decrypt movies without the help of a properly keyed processor.

      --
      The opinions stated herein do not necessarily represent those of anybody at all. Deal with it.
    30. Re:The sad thing is.... by Sneftel · · Score: 1

      So your argument is, The system can't work, because MS has to be stupid? Just because CSS was cracked doesn't mean that every major software company in the world has its head up its ass. There are dozens of completely workable encryption algorithms that have been mathematically proven to be secure, any one of which could be used here. And when they do, a globe full of amateur cryptographers won't have a snowflake's chance in hell.

      --
      The opinions stated herein do not necessarily represent those of anybody at all. Deal with it.
    31. Re:The sad thing is.... by aronc · · Score: 3

      I have been reading the documentation available, like here [microsoft.com] where Microsoft says:

      Only the user decides what "Palladium" applications get to run. Anyone can write an application to take advantage of "Palladium" APIs without notifying Microsoft (or anyone else) or getting its (or anyone else's) approval.

      I have also been reading enough to know that most of the information out there about Palladium is untrue.


      Even assuming this is true (which I don't) this only applies to the application level. Yeah, so you can run any app you want. Whoopie. Apps are useless without data to manipulate and Palladium takes away my control of what I do with the data on my machine.

      If I can manipulate and distribute music/movies/text that I created there is, by definition, a way to do it with music/movies/text someone else made. Maybe not trivially, but there is a way. The system is useless either way. If I cannot distribute data a computer is worthless. If I can than the protections it supposedly gives do not perform as advertised.

      --

      jello.
      aka aron.
    32. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      The thing is there is a strong urge by many very tallented people to crack this particular scheme.

      There is no algorithm that has been mathematically proven to be uncrackable to my knoledge, I could be wrong about that though since I am not a crypto guy.

      I was making refernce to MS's beautiful "activation" key scheme, what makes you think they won't be as stupid in the future?

    33. Re:The sad thing is.... by Sneftel · · Score: 1

      The thing is there is a strong urge by many very tallented people to crack this particular scheme.

      There is a strong urge to crack all of the major cryptosystems out there.

      There is no algorithm that has been mathematically proven to be uncrackable to my knoledge, I could be wrong about that though since I am not a crypto guy.

      You are wrong about that. There are many proven-strong cryptosystems. Of course, any algorithm is vulnerable to exhaustively searching the entire keyspace (a "brute force" attack) but with a sufficiently long key, it would take many millions of years to do that.

      I was making refernce to MS's beautiful "activation" key scheme, what makes you think they won't be as stupid in the future?
      a) product activation != encryption
      b) the algorithm used was never cracked, only circumvented
      c) what makes you so sure they will be?

      --
      The opinions stated herein do not necessarily represent those of anybody at all. Deal with it.
    34. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      during key generation the CA's can map the key to a specific hardware...

    35. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      I would agree TCPA does what you state, Palladium is quite different than the TCPA spec though.

    36. Re:The sad thing is.... by geekee · · Score: 1

      Yeah, LaGrande is evil, just like guns are evil. Give me a break. Intel is providing an additional tool for software developers to do what they like with it. Quit with the paranoid fantasies. Intel has no love for MS, and has no plans to make a processor that with only work with Windows. There is no incentive for them to do this. It only makes things riskier for them to limit the applications of a Pentium chip.

      --
      Vote for Pedro
    37. Re:The sad thing is.... by phaserzen-x · · Score: 1
      The sad thing is that those of us that do know what's going on are doing nothing about it!

      I know people think that there's nothing we can do, but geez, we can think of something.

    38. Re:The sad thing is.... by Alsee · · Score: 5, Insightful

      Why does it need a key? Palladium-locked data isn't going to jump all around the net--it's going to stay right at home, and be accessed only by the program that wrote it.

      It is a cryptographic system, it kas keys. The way access is restricted to approved programs is by signing the programs with a key.

      Palladium-locked data isn't going to jump all around the net

      Yes, a signifigant amount of Palladium data WILL be bouncing around the net. Content delivery, patch delivery, every time you try to view certain kinds of DRM files you'll be bouncing locked data off of an approval server. One of the feature Microsoft is hyping is that you can send locked E-mails to people.

      Microsoft's marketing hype about Palladium is extremely misleading. It does not do the good things they say it does, and it does do the bad things they say it's not intended to do. Palladium is Bad News (unless you happen to want to sell DRM content or you happen to want an ultimate lock-out against competition).

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    39. Re:The sad thing is.... by Alsee · · Score: 1, Flamebait

      The only encryption mathematically proven to be uncrackable is the One-Time-Pad.

      Other kinds of encryption have only been "proven strong" in that many people have tried to crack them and no one has suceeded YET.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    40. Re:The sad thing is.... by Alsee · · Score: 2

      Sigh. Mis-informed Anonymous Coward. What else is new?

      The major thing wrong with palladium is that it cannot work. There is nothing stopping you from running everything inside a virtual machine which exactly emulates the palladium-protected machine.

      It is only possible to cun a virtual machine if you have full information about the machine you are emulating. This is exactly what Palladium is designed to prevent. The critical information is locked up inside special tamper-resistant chips.

      *IF* you could get the full information on the chips you could run the virtual machine, but then you wouldn't need to. If you have all the information you could just write a program to directly do the decryption.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    41. Re:The sad thing is.... by jbolden · · Score: 2

      DVDs and CDs exist today. What the entertainment business produces they do sell today in usable formats. There are certain other things like the video versions of their songs that they could release but pretty much they sell their products. I don't know what products they aren't releasing that they could be.

      As for copy files on my machine. Any doc I have I can copy and distribute. There may be civil penalties for doing so if I cause economic harm. That is far more free then a situation where I am criminally liable even if I am succesful in distributing something and these somethings which prohibit distribution aren't neccesarily things that would cause economic harm.

      Finally the user does not decide what software is trusted. If they did they could run a debugger and get the keys that are being used by the programs running.

    42. Re:The sad thing is.... by Alsee · · Score: 4, Insightful

      The media that will most likely be restricted is media that is not available at all right now (legally) because the media producers fear piracy.

      In a computer EVERYTHING is data. Media=content=data. Programs themselves can be locked inside the palladium system, as can the entire operating system, or websites. Anything and everything on a computer can be locked behind the Palladium wall, and all it takes is someone at a company to say "Heay, if we use Palladium on [something/everything] it then we could [do whatever]".

      Do you have any doubt that patches are going to be wrapped in Palladium "for your own protection"? Do doubt that websites that require Palladium will be as common as websites require cookies or require javascript?

      Fair usage is a pretty muddy area, anyway.

      The outter boundries of fair use are not well defined, but large areas are crystal clear. Courts have clearly and consistantly stated a wide varietey things are fair use, and that fair use is an ABSOLUTE exemption from copyright protection. You can't casually dissmiss fair use merely because there exist some areas that are unclear.

      >The right to copy and email many types of files on my own system
      - In general, you do not lose this "right".


      Unless the application goes out of it's way to enable you to move a file, you lose this right for every file within Palladium.

      The cases where you do lose it, it is not legal to copy the file anyway.

      Bullshit. (Pardon my french) Not every instance of moving a file is a violation of copyright law, and files inside Palladium are not necessarily covered by copyright protection. As I said before, anything and everything can and will end up inside Palladium. It's quite possible wind up with content to which YOU ARE THE COPYRIGHT HOLDER to be locked up on your machine, unable to move them.

      The user still decides what software is trusted or not.

      Then you do not understand Palladium at all. Trustworthy computing has ZERO to do with you trusting your machine or you trusting/not-trusting programs. YOU DO NOT GET TO DECIDE WHAT IS TRUSTED. Palladium is all about corporations not trusting YOU. THEY get to decide weather they trust your hardware. THEY get to decide weather they trust your operating system. THEY get to decide weather they trust your program. THEY get to decide weather they trust your data.

      privacy is maintained

      IF and ONLY IF the program chooses to do so. Palladium makes it trivial for programs to track you uniquely if they choose to, and companies are already trying to do this almost every chance they get.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    43. Re:The sad thing is.... by knorthern+knight · · Score: 1

      > There are zero modems that require MS. However, There are modems that
      > require a software driver, but thats far from requiring MS. All you need
      > to do is make a driver for whatever platform you want, and it works fine.

      Wrong. My old USR X2, flashed to v90, regularly connected at 50666 bits/sec under Windows 98SE, and today does so under Redhat 8.0. Have you ever seen a "software modem" do that outside of a test lab? Neither have I.

      There is a basic technological problem with "software modems". Communications is a real-time app. The system *MUST* respond to data I/O in a small time window. Ditto for your harddrive. If the modem has its own hardware doing this, then your cpu can look after harddrive I/O. However, if the modem manufacturer cheaps out and skimps on a chip or two to save $10, your CPU must handle *EVERYTHING SIMULTANEOUSLY*. Buffering helps provide a bit of safety margin, but overal throughput still slows down.

      Try *SIMULTANEOUSLY* downloading a large file *AND* writing a CD *AND* doing a large compile/build. Even a 2.4 ghz Intel CPU will fall behind servicing I/O requests.

      --

      I'm not repeating myself
      I'm an X window user; I'm an ex-Windows user
    44. Re:The sad thing is.... by knorthern+knight · · Score: 2, Insightful

      > Hint: you will be able to turn it off,

      Really ? You seem to trust MS/Intel a lot more than I do.

      > since it would break backward compatibility if you couldn't.

      Just like MS worries so much about MS Office 11 being backwards-compatible to Windows before 2K?

      And don't forget to ask a few bitter Visual Basic programmers about having to re-write the vast portion of their code to move it to dot-NET.

      --

      I'm not repeating myself
      I'm an X window user; I'm an ex-Windows user
    45. Re:The sad thing is.... by pseudochaotic · · Score: 1

      ...it would take many millions of years to do that. Some distributed computing efforts actually have had millions of years of computer time.

      --
      And the l33t shall inherit the 34r7h.
    46. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      I have also been reading enough to know that most of the information out there about Palladium is untrue.

      Did you get that bit of information from Microsoft too?

    47. Re:The sad thing is.... by inode_buddha · · Score: 1

      Point well taken re: trusted computing. I agree completely.

      That's why, in my home-based, non-commercial environ
      I do not alllow binariies which I do not at least trust halfway (by purely subjective standards) in addition to the practices and procedures recommended by DoD 5200-28 STD

      re: ("The user still decides what software is trusted or not.".) to which I can only say, "Bummer I still own the fsckin' machine that software might be installed on huh? Like I don't already have a few identical ones besides, and could toss this current machine out the window anytime. And could someone please prove that my actual handwritten signature carries less weight than a digital signature?

      --
      C|N>K
    48. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      The worst thing is - when I try to explain what Palladium/TCPA is, and what it means, I get the following responses:

      • Non-computer user: Bemusement... utter non-comprehension of how much their lives are controlled by computer, and how much this could restrict and control them.
      • Newbie Windows user (still have faith in technology [it's new to them]): Microsoft wouldn't do something like that. The Government wouldn't let them.
      • Moderately knowledgable Windows users: "[shrug] Someone will crack it."
      • Technically knowledgable user: "Oh shit."

      So good luck to anyone trying to stop this. It seems that these companies will win, simply because most people are stupid; or have a touching faith in capitalism and non-corrupt government; or think that uber-hackers are out there and will solve all their problems; or are so small in number so as not to show up in any kind of sales figures.

      It's enough to make you want to weep. It really is.

    49. Re:The sad thing is.... by knorthern+knight · · Score: 1

      > The people I know in the security business agree that the problem is
      > impossible to solve without hardware support. If you haven't noticed,
      > there is a huge demand for digital content, and there is a lack of
      > supply of that content because the media companies fear piracy.

      Hello! My PC is a powerful general purpose computer. It is *NOT*, repeat *NOT*, a f***ing "entertainment delivery device". If that was what I wanted, I would've gotten XBox and/or WEB-TV. You're missing the *REALLY* important objection to Palladium. I wouldn't mind if songs by scantily-clad-seventeen-year-old-screeching-sluts could only be played on dedicated special-purpose boxes. What I *DO* object to is the castration of PC's to the point where they're useful for *NOTHING BUT* playing songs by scantily-clad-seventeen-year-old-screeching-sluts.

      MS and Intel both know that given the option of buying similar machines with/without DRM, the public will go for the version without DRM. Why do you think they want to ram it down our throats by making it impossible to buy PC's without Palladium ? If MSN and AOL could both only be accessed via special dedicated terminals, I'd have no objection. Just leave my PC alone.

      --

      I'm not repeating myself
      I'm an X window user; I'm an ex-Windows user
    50. Re:The sad thing is.... by jbolden · · Score: 2

      You seem to be basically reversing my claim: arguing that trusted applications run in their own sandboxes and untrusted ones do not. I think you are wrong but for the purpose of argument I'll accept it for a second.

      If the user determined trust and untrusted apps all run in the same user space then all I'd have to do is kick windows media player into "untrusted" and run my debugger on it.

    51. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      What I dont get is how is this all supposed to work if you dont even have an internet connection? What if the only hardware/software you can legally use is pallidum but to authenticate everything it needs to be connected to the internet. So bascially if you cant afford to get internet access or you are in some remote place that does not have any access to the net, you arent allowed to use a computer?

    52. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      God bless you Alsee. This guy obviously works for MS. Your words are the truth, and you mentioned everything I was going to say.

      LaGrande and Palladium are EVIL, and only designed to allow the companies of the world MORE power in your PC...and you, the user...will have power taken away.

      It REALLY pisses me off that Microsoft has been selling Palladium by saying stuff like;

      "Palladium will allow you to say who gets to read your emails", then they go on to say, "If you are sending your medical history, and only want your doctor to have the ability to read the mail, you'll be able to set that up".

      BULLSHIT.

      We all know not ONE doctor will allow their patients to send in such information. They'll just have to write the small print contact info such that it revokes ANY sort of protection Palladium might have offered us (the consumer), while at the same time, protecting their own ass with Palladium

    53. Re:The sad thing is.... by Planesdragon · · Score: 3, Insightful

      Content delivery, patch delivery, every time you try to view certain kinds of DRM files you'll be bouncing locked data off of an approval server. One of the feature Microsoft is hyping is that you can send locked E-mails to people.

      Ok, so part of Palladium will involve internet transport--but not all of it.

      Palladium's chief change, as I understand it, is a "secured disk area" where only the actual program that writes the data can read the data.

      Microsoft's marketing hype about Palladium is extremely misleading. It does not do the good things they say it does, and it does do the bad things they say it's not intended to do. Palladium is Bad News (unless you happen to want to sell DRM content or you happen to want an ultimate lock-out against competition).

      Sorry, I don't consider DRM a bad thing. A trusted PC interface means that those-that-publish will be able to do so electronically without knowing that it's going to be pirated the next day.

      Neither do I consider a program being able to lock its own files a bad thing--since MS would be shooting themselves in the foot operatability-wise if it's impossible to tell the program to move the files to "public space."

    54. Re:The sad thing is.... by Nicolai+Haehnle · · Score: 1

      Sorry, I don't consider DRM a bad thing. A trusted PC interface means that those-that-publish will be able to do so electronically without knowing that it's going to be pirated the next day.

      Guess what, I'd _love_ to see a DRM system that I can trust - both as a creator of "content" and as a consumer.

      I would only be able to trust such a system if it were open, which implies that there could be a compatible, open-source implementation of the system.
      Now the obvious problem is that the kind of "security" that Digital Restrictions Management wants to provide can ultimately only work by security through obscurity. Kind of like what we saw with DVD encryption. And security through obscurity is obviously mutually exclusive with openness.

      So it's just not going to happen.

      I'd prefer to see an open, society-based solution to the "Intellectual Property" problems we're facing today, rather than a closed, locked down solution that gives tremendous power to the select few who built the solution.

    55. Re:The sad thing is.... by LarsG · · Score: 1

      One of the fundamentals of capacity systems (which is where the ideas behind palladium came from) "if programs can communicate they can collude".

      Excuse me for being slow, but isn't .NET, DCOM, DDE and OLE all about communication?

      Doesn't MS claim that Palladium won't break existing applications? *scratch head*

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    56. Re:The sad thing is.... by LarsG · · Score: 2

      The only encryption mathematically proven to be uncrackable is the One-Time-Pad.

      Why is the above moderated as flamebait? Hint to moderators - if you don't understand the subject matter, stay away.

      OTP is the only mathematically proven uncrackable encryption algorithm.

      OTP is rarely used because the key management is cumbersome - the key can only be used once, and the key must be the same length as the message.

      Apart from OTP, none of the other algorithms have a positive proof (i.e., a mathematical proof that states once and for all that it is unbreakable). There are no mathematical proofs that can show that a particular algorithm where the key length is shorter than the message is safe in all situations. They are only considered 'safe' because noone has so far been able to give a negative proof.

      All we know is that a lot of very skilled people have stared long and hard at some ciphers and said that they can't at this time think of any attack that would significantly reduce the effort required to crack them. That's the best you can get unless you go OTP, and is the most important reason for why the claim 'newer is better' does not hold true in crypto.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    57. Re:The sad thing is.... by Alsee · · Score: 2

      Palladium's chief change, as I understand it, is a "secured disk area" where only the actual program that writes the data can read the data.

      Not exactly. Palladium data is written to the disk just like any other data, anyone/anything can read/copy/modify it. The diference is that Palladium data is encrypted. Trying to alter encrypted data will generally destroy it completely. The data also says who/what is allowed to decrypt it. Generally this would say what operating system signatures it trusts, what program signatures it trust, and what machine it is useable on.

      It can also require active internet confirmation, meaning many of your files will be unusable unless you have an active internet connection and allow it to phone-home every time you use it. Some will require a CONTINUOUS internet connection constantly pinging a cryptographicly authenticated time server. If your net connection dies in the middle of a song or movie or while you are running a time-frame licenced program then the computer cannot verify you are currently within the time limit of your licence and the program or file locks up. Note that the time-frame licened program could be the operating system itself. If your internet service drops out for any reason whatsoever your entire computer DIES. If the their server goes down your data is gone until they get the server back up. If the the company folds your data is gone forever. If the company is hacked and their key is destroyed your data is gone forever. And remember, your data could be the operating system itself, meaning everything on your computer is gone forever.

      Sorry, I don't consider DRM a bad thing.

      While the stated purpose of DRM is fine, the problem is that is impossible to implement without (A) restricting more than it is permissable to restrict (B) creating a slew of (profitable) abuses and (C) the content escaping anyway.

      (A) A computer cannot know how you are going to use the information, and that is central to determining if it is a legally protected fair use. Since the computer can't tell, it has two choices, it can allow it (rendering the DRM worthless), or it can disallow it (denying you your rights).

      (B) DRM can enforce a spyware requirement. DRM can lock out competition. DRM can leverage dominance in one area to create a monopoly in another area (only RIAA brand radios can access RIAA DRM music). Palladium opens a route for Microsoft to literally own the internet. Doubt it? Websites ARE content that will be protected by Palladium, patches will be protected by Palladium, internet purchases and all sorts of data will be wrapped in Palladium. Why not just Palladium the entire connection? This is layer built on top of the internet. Browsers, websites, servers, everthing that moves inside this layer can still see out to the rest of the internet. Everything outside is locked out giving everything a motivation to move inside. The less there is outside, the more useless the outside becomes.

      (C) Someone can always copy text over by hand, record music with a microphone, capture an image with a digital camera, or record a movie with a video camera. They can then place it on the internet in unprotected form and it can be copied infinitly.

      Strong DRM failing to prevent a file from escaping once has the same effect as a weak protection failing to prevent the same file from escaping 500 times. Therefore how do you possibly justify all of the negative consquences associated with strong DRM when the results are the same?

      MS would be shooting themselves in the foot operatability-wise if it's impossible to tell the program to move the files to "public space."

      You are handing total control over to who ever controls the keys. Any program COULD be written to allow you to move files out to public space, but
      in some cases the company may find it more profitable not to. It locks out competitors. It forces you to by their new version. The application could be provided as a service (pay per use), the program could be licened by time period, you have to buy a new licence every year. They can sell you other applications that can access your data - can you imagine having to buy three seperate spellcheck programs because you have text documents locked within three different company's palladium spaces? Or your data could stay locked up because the programmer just never bothered to program in the option, or you could be denied the option in the name of piracy prevention even when you created the content and you therefore own the copyright.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    58. Re:The sad thing is.... by Alsee · · Score: 2

      I would only be able to trust such a system if it were open, which implies that there could be a compatible, open-source implementation of the system.

      That is EXACTLY part of what Palladium promises. It is also a complete deception. It will be virtually impossible for any open sorce code to get approved, Palladium content is unlikely to bother reconizing that approval, and the slightest change to the program voids the certifacation - strangling development work and patching. The program must be re-certified with every change.

      Open source might be able to use palladium itself in some ways, it WILL be locked out of the primary Palladium arena. And the things it can do with Palladium it can generally do without Palladium anyway.

      Palladium is severly anti-competitive and anti-open source, but it is hidden under a layer of marketing deceptions that it is supposedly fair and open. Microsoft is releasing Palladium code as open source. Good luck actually using it to watch a movie on Linux.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    59. Re:The sad thing is.... by quantum+bit · · Score: 2

      OTP is the only mathematically proven uncrackable encryption algorithm.

      OTP is rarely used because the key management is cumbersome - the key can only be used once, and the key must be the same length as the message.


      Sooooo... If OTP requires a completely secure delivery method for the key (which is the same length as the message), why not use the completely secure delivery method for the message itself and forget the encryption? It's kinda pointless at that point.

    60. Re:The sad thing is.... by Planesdragon · · Score: 2

      If your internet service drops out for any reason whatsoever your entire computer DIES.

      Then it won't be a requirement for the OS to work--at least, not any OS that works like the ones we know today.

      An OS that's a glorified cable box can, probably will, and probably should die when the cable dies. Then again, there's always DVDs... so I find it rather unlikely that MS will make an OS ISP dependant without far better ISPs than we've had so far.

      While the stated purpose of DRM is fine, the problem is that is impossible to implement without (A) restricting more than it is permissable to restrict (B) creating a slew of (profitable) abuses and (C) the content escaping anyway.

      Fifty years ago, the Internet was impossible. A hundred years ago, flight was impossible. Given enough time and money, a possible way will be found.

      (A) A computer cannot know how you are going to use the information, and that is central to determining if it is a legally protected fair use. Since the computer can't tell, it has two choices, it can allow it (rendering the DRM worthless), or it can disallow it (denying you your rights).

      Fair Use is copyright infringement that's "OK." Someone making a copywritten work is, AFAIK(IANAL), under *no* obligation to make it easy to copy. Especially in the digital sense.

      (Want to quote out of an ebook? Do what you did when it was a paper book, and copy the darn quote by hand.)

      (B) DRM can enforce a spyware requirement. DRM can lock out competition. DRM can leverage dominance in one area to create a monopoly in another area (only RIAA brand radios can access RIAA DRM music).

      In non-monopoly situations, that's all well and good.

      In monopoly situations, the government is charged with stepping in to regulate. I think I'll reserve judgement on the fed's ability to do so with how well MS is held to the spirit of the settlement.

      Palladium opens a route for Microsoft to literally own the internet. Doubt it? Websites ARE content that will be protected by Palladium, patches will be protected by Palladium, internet purchases and all sorts of data will be wrapped in Palladium. Why not just Palladium the entire connection? This is layer built on top of the internet. Browsers, websites, servers, everthing that moves inside this layer can still see out to the rest of the internet. Everything outside is locked out giving everything a motivation to move inside. The less there is outside, the more useless the outside becomes.

      It'll be an uphill battle. Every MS implementation has to fight against the extant OS installs. Sure, one day Palladium might be ubiquitous enough to "own" the internet--but that'll be another soon-to-be regulated monopoly on MS's behalf.

      (C) Someone can always copy text over by hand, record music with a microphone, capture an image with a digital camera, or record a movie with a video camera. They can then place it on the internet in unprotected form and it can be copied infinitly.

      Yes, at a lower quality--or via a traceable source.

      The effort to transliterate entire copywritten works of significant length is a not-insignificant ammout. Casual piracy will dwindle, and professional "software pirates" and "media pirates" will have a suddenly higher profile.

      (The effect of DRM will be to move the playing field back to pre-internet ages, when one needed to actually pay money to get a good copy.)

      You are handing total control over to who ever controls the keys.

      Well, yeah. People proved to be irresponsible with a heck of a lot of things, and since human nature has prooved to not be able to be trusted with IP, it's getting locked up.

      Any program COULD be written to allow you to move files out to public space, but
      in some cases the company may find it more profitable not to.


      Only in media-viewing apps. In content-creation apps, a company that makes it impossible to share your work loses (at least) half of its audience, right away.

      It locks out competitors. It forces you to by their new version. The application could be provided as a service (pay per use), the program could be licened by time period, you have to buy a new licence every year.

      MS has been itching for a way to do just that for quite some time.

      If they can pull it off properly, it'll be a good thing. No more half-assed marketing-driven "new versions," just a real patch...

      (well, good for the software anyway. Maybe not so good for the freedom zealots...)

      They can sell you other applications that can access your data - can you imagine having to buy three seperate spellcheck programs because you have text documents locked within three different company's palladium spaces?

      No. Proprietary formats are a killer to interoperability, and MS is showing signs that they've realized this.

      I cannot imagine Microsoft making Word docs "Word only." I know that something like that would make my employers drop it in a heartbeat, and I suspect most of corporate america would act the same way.

      Or your data could stay locked up because the programmer just never bothered to program in the option, or you could be denied the option in the name of piracy prevention even when you created the content and you therefore own the copyright.

      MS has addressed that to, IIRC--and, as a reasonable person could guess, the answer is "not gonna happen."

    61. Re:The sad thing is.... by jbolden · · Score: 2

      You aren't being slow. Communication and connections between systems increases fucntionality and decreases security. Isolation strict protocals which are easy to monitor and limited functionality increase security and decrease functionality.

      Microsoft is a feature vendor. Getting programs to communicate (OLE being a great example) was a major accomplishment. At this point there hope is that digitial content is going to be enough of a feature to outweigh the bad things they will need to do to get the MPAA and RIAA to stop worrying so much.

      You are correct however that the .net strategy and Palladium are pulling in opposite directions.

    62. Re:The sad thing is.... by jbolden · · Score: 2

      OK makes sense.

      I guess a few questions:

      a) Do trusted apps have to provide all there own OS functionality?

      b) How does the secure storage thing know what app it is talking to? In other words how does it know that it isn't talking to Hacker104 (which the user made trusted) instead of Windows Media Player?

      c)

    63. Re:The sad thing is.... by LarsG · · Score: 2

      If OTP requires a completely secure delivery method for the key (which is the same length as the message), why not use the completely secure delivery method for the message itself and forget the encryption?

      Exactly. :)

      It's kinda pointless at that point.

      For many normal uses of encryption, you're right.

      However, OTP can be used in situations where you can deliver the OTP securely at certain times only, but need to be able to send encrypted messages at random times. Say, a US nuclear sub can refill its stack of pads when it is at home base.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    64. Re:The sad thing is.... by Kjella · · Score: 2
      Sorry, I don't consider DRM a bad thing. A trusted PC interface means that those-that-publish will be able to do so electronically without knowing that it's going to be pirated the next day.

      Personally I think some heavy drugs would be more effective. That should keep their minds off it.

      Kjella
      --
      Live today, because you never know what tomorrow brings
    65. Re:The sad thing is.... by LarsG · · Score: 2

      Microsoft is a feature vendor.

      No shit. :)

      I'm not really sure who to blame for the sorry state of security in the MS world - the customers for asking for more features, or MS for providing it.

      At this point there hope is that digitial content is going to be enough of a feature to outweigh the bad things they will need to do to get the MPAA and RIAA to stop worrying so much.

      MS is not exactly the role model for a weak and malleable corporation. I'm kind of surprised that they are allowing the *AA to push them around like this.

      Besides, you'd expect that MS and the consumer electronics mfgrs know enough about history to recognize the pattern - the content industry yell and scream for each new technology, but eventually they come around. Why are they so willing to bend over when it should be obvious that Adam Smith's invisible hand will eventually force the *AA to adapt?

      (Anyone remember the movie industry and color TV? If people could see color movies on the TV for free, it would surely be the death of movie theaters. According to the MPAA, no movie company would ever license their movies for color TV. It only took one or two defectors before their line in the sand crumbled.)

      You are correct however that the .net strategy and Palladium are pulling in opposite directions.

      And I dislike both, for opposite reasons. Palladium for creating 'security' that so obviously can be abused for DRM purposes (and making machine virtualisation impossible), and .net for the possibility of becoming the next portmap on bugtraq.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    66. Re:The sad thing is.... by Alsee · · Score: 2

      >If your internet service drops out for any reason whatsoever your entire computer DIES.
      Then it won't be a requirement for the OS to work--at least, not any OS that works like the ones we know today.


      Really? WinXP already dies if it can't phone home for Product Activation, and again if you change the hardware. If it can't phone home on the internet YOU have to phone home for it on the telephone. There are also over a dozzen different processes in XP that phone home to MS servers, and if they cant your computer does not fully function properly. Would you belive that the god-damn Microsoft Mouse runs with reduced functionality unless you let it phone home? THE MOUSE! And Palladium isn't even out yet. If Palladium is successful according to MS's plans your computer will be severyly crippled or totally unusable without these internet connections.

      Fifty years ago, the Internet was impossible. A hundred years ago, flight was impossible. Given enough time and money, a possible way will be found.

      Nothing short of inventing strong AI can enable software copyright protections without (A) infringing fair use and (B) enabling rampant abuse. And I doubt even that could not prevent (C) content escaping.

      The limits of copyright protection (and therefore the extent of fair use) can only be decided by a court, expecially in cases where it is a new use that has never been seen before. Unless the DRM program is going to put you on hold while it initiates a court case it is indeed impossible for DRM to allow fair use and still work.

      Fair Use is copyright infringement that's "OK."

      No, that is a PR lie to paint "fair use" as a form of piracy and infringment allowing them to kill fair use. Copyright protections do not reach or include anything that is fair use therefore fair use cannot be an infringement. DRM extends beyond the limits of copyright protion, DRM infringes on fair use.

      (B) DRM can [be abused]
      that's all well and good.
      In monopoly situations, the government is charged with stepping in to regulate.


      Palladium is like making guns that spit out a hundred dollar bill every time you shoot someone. It rewards abuse. Sure, people can choose not to abuse it, sure the government can try to prosecute criminal acts, but it's still collosally bad.

      Every MS implementation has to fight against the extant OS installs.

      WindowsXP is perfectly capable of connecting to Microsoft servers and "upgrading" itself into a Palladium operating system. And the licence for it says that you give Microsoft the right to do so. Hell, the MediaPlayer licence alone grants them the right to do so. Just look for the section where they have the right to disable your software. The clause is for updating DRM, well, that's exatly what installing Palladium is. Will MS try it? I hope not. Can they? Yep.

      The effort... is a not-insignificant ammout.

      I think you completely missed my point. One person making the effort to do so and putting it on the internet has the exact same effect as if 500 people did so. The result is that everyone gets burdened with negatives, and there doesn't even exist a positive result to weigh against the negative.

      The effect of DRM will be to move the playing field back to pre-internet ages, when one needed to actually pay money to get a good copy.

      Not if a single copy gets posted onto the internet where it propagates for free.

      In content-creation apps, a company that makes it impossible to share your work loses (at least) half of its audience, right away.

      Are you really that naive? If a corporation sees a profit opportunity to leaving your files locked up they will jump at the chance and be quite creative about it. In many cases the major companies will simple hand it to you. Do you think people use locked WindowsMedia file formats because they preffer it? It gets used because Microsoft dumped the player on everyones computer. Do you think people preffer sound cards with SecureAudioPath? They are manufactured because Microsoft denies support and Windows Capatibility Certifacation to any sound card that does not have it. Do you think people preffer printers with expensive and incompatible ink cartridges? All manufacturers sell them that way. Some put crypto-chips in their ink cartriges and the printer silently goes into "crap quality" print mode if it's a refill. They do it because they can, and they make a buck off it.

      [software as a service, or a yearly licence] If they can pull it off properly, it'll be a good thing.

      True, is some ways it could. The point is that you don't need Palladium to do the good things. If it's done for the reasons I listed then it is a bad thing, and Palladium enables you to enforce it for bad things. If someone is still running Windows 3, and it does everything they need it to, would it be a good thing if it said "You must buy Windows 95" and stopped working? And then made you buy Win98, then 2000, then XP? They don't need or want 95,98,2000, and XP.

      I cannot imagine Microsoft making Word docs "Word only." I know that something like that would make my employers drop it in a heartbeat, and I suspect most of corporate america would act the same way.

      Text documents are an extreme case, but Microsoft has already hinted at it with their Palladium example about locked E-mail. Microsoft has intentionally made text documents fail non-MS programs. And it't wouldn't be a "Word only" document, it would be a "Microsoft only" document, all other Microsoft Palladium programs would be able to access it as well. It is pretty standard practice for any company to create an incompatible format for everything other than text.

      >you could be denied the option in the name of piracy prevention even when you created the content and you therefore own the copyright.
      as a reasonable person could guess, the answer is "not gonna happen."


      Bzzzt wrong answer. Already happened. Digital Audio Tape (DAT) had mandatory copy controls built in. People were recording their own band or their friend's band and were rather supprized to discover that they couldn't make copies. Do you really blame those people for reffering to DRM as DigitalRestrictionsManagment or DigitalRightsManglement? The legitimate copyright holder isn't allowed to make copies!

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    67. Re:The sad thing is.... by freefoote4 · · Score: 1

      That's all nice and pretty. It will be nice and secure. But what happens to those of us who are not connected to the net all the time? With my system here, my computer is not connected to the net directly. It is connected via the network and the proxy server on another machine. But even then, that's a dialup link and is not up all the time. Now what happens when I want to play that song? Now I've got to be online? I'd rather be able to play songs (like I do now) directly from my fileserver (another machine), without having the net connected. That's another reason why this won't work. It's nice for those in the US with always on cable connections, but here in Australia, it's still too expensive for the average person.

    68. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      The CSS algorithm was flawed, but that was not the only reason it was cracked.

      Another reason is that DVD-players were implemented in software, which is inevitably circumventable by reverse-engineering in the absence of harware protection. Palladium promises to deliver this hardware protection to trusted software, and if implemented properly, it might.

      However, regardless of the exact implementation, it will be difficult to do right, and 100% tamperproof hardware isn't even possible using current technology, even though it is much harder to reverse-engineer than software.

    69. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      I think that the problem here is that there is no way to keep the contents of the hardware secret, and it would be possible to implement the same algorithms in software.

      The question is how the provider of the media content verifies that the recipient is trusted. If it uses a central key to verify that it is really going to be decrypted by hardware, then that central key will be discovered, one way or another. If each unit has its own key...well, either there has to be a central database of keys, which is unmanageable and requires tracking of leaked keys, or the provider must trust anything that claims to be a trusted software/hardware combo.

      Remember, there is no such thing as 100% tamperproof hardware.

      Maybe what is being relied on here is that most consumers will use trusted software that doesn't play unencrypted content. This isn't as hard as it sounds, just introduce new media formats and codecs to go with the trusted framework so no old software works, provide trusted players for free. It'll take a while for third party players to implement compatibility, and they might never get trusted status...

    70. Re:The sad thing is.... by jbolden · · Score: 2

      I think the reason Microsoft is being malleable is that really wants digital media ASAP. Customer satisfaction with the current hardware / software bundle is really high. Over the last 5 years average PC sales price have fallen horribly. Remember it used to be:

      $4000 for the computer you want
      $2000 for the computer you will be happy with
      $1000 for the computer you can live with but won't like

      Now $4000 is absolutely top of the line and $2000 is considered high end. At the same time expanding number of computers sold is falling off primarily due to almost full market penetration. The less people spend on hardware they less they'll spend on software.

      Now replacing television / cable with computer generated digital media:

      1) Justifies large upgrades (ripping video is really tough on the CPU. Even the top of the line PC today cannot handle real time HDTV ripping).
      2) Justifies reoccuring monthly fees for software (i.e. like cable TV)
      3) Jusfties a rental model (Blockbuster...)

      I just don't think Microsoft sees any other technology to drive the next generation of upgrades. If you exclude web browsers Windows 3.1 on an 8 meg 386 would cover most user's needs. The web came along at just the right time to drive a whole additional generation of upgrades.

    71. Re:The sad thing is.... by LarsG · · Score: 2

      I think the reason Microsoft is being malleable is that really wants digital media ASAP.

      Ok, I can see that one.

      Doesn't exactly give me a happy fluffy feeling knowing that MS is helping the *AA erect the DRM iron curtain only because that might make the major content providers make their goods available on the 'net two years earlier than they would without ubiquous DRM. MS should also be smart enough to see that DRM will damage the market demand for digital media in the long run. I'm wondering whether this is a sign of MS getting desperate.

      I just don't think Microsoft sees any other technology to drive the next generation of upgrades.

      What about user created content? SMTP was the initial killer app of the Internet, SMS on cell phones, blogs are taking off.. All of this user created content.

      There is an obvious trend in handheld devices of including cameras and microphones - what if MS tried to make it really easy for people to create their own content instead of building infrastructure for force-fed content?

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    72. Re:The sad thing is.... by jbolden · · Score: 2

      I don't think there is much demand for user created content. Look at the web. Back around 97 small websites dominated people's time on the web, today its mainly larger sites. Also the biggest problem is the last mile is asymetric; that is broadband has much faster download than upload speeds. This is going to force content to come primarily in to homes rather than peer to peer.

    73. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      You've already got a copy of that debugger, I gather... I swear, I can't even imagine cracking without the rewind feature now. I'll never go back to Softice.

      Just one little problem with your attack, although it can be overcome with some work. Replay attacks aren't trivial, there will be trusted time sources. This isn't a problem unless it's closely integrated with DRM licensing protocols, and it will be, but good luck. It's not insurmountable.

    74. Re:The sad thing is.... by Anonymous Coward · · Score: 0

      > It is only possible to cun a virtual machine if you have
      > full information about the machine you are emulating.

      And it's only possible to tell if you're in an imperfect virtual machine if you're outside it.

      A debugger currently being whispered about in the cracking scene is (or rather, can recompile itself into) an almost entirely accurate VM of an ACPI compliant PC - nothing can (reliably or reproducibly) tell it's inside a VM, not even the debugger itself. As a result, it's stomped upon every DRM and debugger detection method it's come across.

      Among it's many neat features is the ability to do transparent patches. The memory reads one thing, but executes another - or, if you want to patch data, you can have a particular section of code read the data differently to every other. That's every form of checksum dead in the water, for a start - not very distributable, but seeing as it's all logged, a great information source when performing test cracks.

      The only things that are resistant to that are things that perform network checks - and even the code that performs network checks can be spoofed to respond in "a right way" if you have the appropriate information, or if there is a flaw (such as allowing brute force attacks, or man-in-the-middle attacks).

      TCPA - in fact, all of the TCPA-related technologies - add literally only one thing to this, and it isn't as much of a biggie as you think.

      They provide a key (or rather a method for generating a key), that requires some work to extract from the hardware, that the hardware will not provide to unsigned code.

      This doesn't change the local model at all, because how does it know the host key it's nub has been provided is a real host key, and isn't a VM? It has to check the signature. In software. At which point, that friendly debugger I mentioned, or a tool built from it, eats the signature checking routine alive, and the signature is, apparently, valid.

      The model TCPA changes is the remote control model. The signature would not be valid to a remote host - it could check it if, due to some network negotiation, the Judas machine was forced to use the key in a protocol, and transmit the signature. Being outside the VM, the remote machine checks the signature, and of course it isn't valid because the key is fake.

      Now, the Judas machine could still be tricked into just not negotiating, or continuing anyway, or communicating with another Judas as a remote server. The TCPA key validation protocol has to be required for what the Judas is trying to do - if it can be skipped at all, it's useless.

      Why, of course, what's to say it's the real key? It's been signed by the manufacturer, who themselves have been signed by a master key and so on.

      That is where the weakness in the TCPA-like schemes lie - in their signature schemes. Their revocation methods could allow massive denial of service attacks, and the value of master signing keys is truly immense - furthermore, practically, the value acquiring even one code signing key is significant.

      This is why the trusted core's actual key is never transmitted outside the chip, even to trusted code - it generates other keys and signs them and sends that to trusted code. Replay attacks are resisted by network-based trusted clock sources - there's another point you'd need to attack.

      However, this is insignificant, as the intermediate keys are useless except for the trusted boot chain (and if network is not absolutely required for boot, the VM can do that). They are discarded, ephemeral, and DRM of any form needs persistent, secret keys. That's Palladium's job to handle, and the trusted boot chain (TCPA) is used to ensure it's signed and that only Palladium gets access to the secret keyring.

      That's what it's used for. It can't actually do that, though. At least, not if the secret keyring is local. It'd have to be network based, and furthermore, network based and never saved to disc, but kept persistent in trusted memory and discarded upon power fail or reboot.

      Let me put it in a more practical fashion. TCPA means jack shit. It can't be used to enforce software licensing in any secure manner, and I look forward to tearing apart any system which tries to use it for that. It can be used for Digital Restriction Mechanisms, but only if an internet connection is actively REQUIRED to view the content - no, that's not right either. Only if a specific remote server happens to be up and accessible - if the company goes broke, or the network's feeling ill, you're out of luck. It will need to reauthenticate for every reboot, too. So only if an internet connection must have been made, and the keyring fetched. Want Windows to re-activate on every reboot? That's what they're going to have to do. Good luck with the convenience aspect, guys.

      Anyone with any brains and cash would take the clever solution. I mean, you could buy lots of TCPA PCs, in different places, at different times, as ordinarily as possible - turn them into Judases, by extracting their REAL signing keys from the chips. Throw them away - you don't need them now, a VM would do as well.

      But somehow that solution doesn't seem smart, when leaking a manufacturer key - which would have to be VERY commonly used, one sign for every motherboard pressed, say - in as low a profile fashion as possible to ensure no-one notices it's no longer a secret, would give you the ability to generate your own valid keys (while stealing a master key might sound a better idea, those signatures are likely to be rare enough that the lists of "trusted" manufacturers would be checked manually, and updated on the auth servers - creating your own manufacturer with it would probably ring alarm bells far too quickly).

      The truly smart pirate group solution, assuming a big budget (and you'd be surprised, really surprised - I was), is this - steal all the manufacturer keys, silently. Stick to Judas PCs from one manufacturer, leaking formerly DRM-protected content and software, in dewatermarked, open formats left, right and centre. Wait 'til someone realises the manufacturer key was pilfered, and pulls the plug. Wait for the consumer backlash when their new PCs they just bought don't play their DVDs anymore. Then switch to the next manufacturer. Rinse, wash, repeat until consumers correctly associate Palladium with "deliberately unreliable" and avoid it like the plague it is.

      There is one worse black-hat attack, and this would be if there existed design flaws in the revocation mechanisms. If it were possible to revoke manufacturer or master keys erroneously, even worse so in the firmware, or to revoke the BIOS's own signature, that would be a bloody vicious worm payload which would render every TCPA PC stone dead, forever. I freely encourage such an attack. Sometimes lessons can only be learned the hard way, and after about half a million customer service calls about a dead PC on the same day, if the manufacturers don't get the damn message, the consumers will.

    75. Re:The sad thing is.... by Anonymous Coward · · Score: 0
      One lie, one half-truth.
      1. The user does not decide what software is trusted by Palladium. The user can run untrusted programs, and the user can decide not to trust a specific signed program or licensed publisher, but the user cannot decide to trust a program that is unsigned, or is not signed by a licensed publisher.
      2. There will not be a central authority who can license software, but there WILL be a CA who can license software publishers. This will work out to be the same thing in critical areas of contention, like media players.
  3. Safer from what? by phreak03 · · Score: 2, Insightful

    A world withought hackers, were the only people who can allow software to be installed on your computer is the nice folks at Microsoft and intel, wait did i forget myself in that list? this is a joke all it will be is Microsoft schemeing to prevent "fair use", open source, and easy government computer spying and restrictions is all that palidinium will be used for. Sounds like the future of the wounderfull digital restrction management is comeing.

    --
    come comment on the madness at http://slashdot.org/~phreak03/journal/
    1. Re:Safer from what? by Lobsang · · Score: 2

      And I wonder how long it's going to be until MCSEs or other equally annoying "Microsoft Certified" mouse operators gain special codes or smartcards that only allows them to do windows installations and whatnot...

  4. The irony!!! by Anonymous Coward · · Score: 1, Insightful

    "Security is mostly a superstition. It does not exist in nature... Life is either a daring adventure or nothing." -- Helen Keller

    This was the quote on the bottom of the page... what irony!

  5. ... "more stable platforms" by Anonymous Coward · · Score: 0

    Hey, man, if this is what it takes to allow M$ to release an OS that's actually stable, I'm all for it. Once that little OS detail of being stable is out of the way, maybe they can put some time into security...

    1. Re:... "more stable platforms" by miketang16 · · Score: 0

      I think they pretty much pulled that one out of their @$$... I can't think of anyone putting restrictions on a CPU or OS, would make it more stable. More of a pain in the ass.. yes..

      --
      -------
      "In times of universal deceit, telling the truth becomes a revolutionary act."
      -- George Orwell
    2. Re:... "more stable platforms" by NortWind · · Score: 1
      Hey, man, if this is what it takes to allow M$ to release an OS that's actually stable, I'm all for it.

      Ben Franklin put it best when he said "those who would trade a little freedom for a little security deserve neither". And in this case will get neither, I might add.

  6. Great Name... by Ira-Waru · · Score: 5, Funny

    In the classic LucasArts adventure game Monkey Island 2, there is a character called Largo LeGrande. When we first meet him, IIRC, he tells Guybrush (the protangonist) that this island isn't safe, and then procedes to turn him upside down and shake all the money out of his pockets. Also, he has an oppressive embargo on the whole island (The Largo Embargo).

    Couldn't think of a better name, myself. :)

    --
    Such a price the gods exact for song: to become what we sing - Pythagoras
    1. Re:Great Name... by pommaq · · Score: 1

      To paraphrase mr. LaGrande himself:

      Wherever you go
      on sea or land
      you can't ever hide
      from Largo LaGrande!

    2. Re:Great Name... by yorgasor · · Score: 2

      It's actually named after a town in Oregon. Intel, being based in Oregon tends to name many of their projects after places in Oregon: Tualatin, Willamette, Yamhill, and LaGrande are ones I can think of off the top of my head.

      --
      Looking for a computer support specialist for your small business? Check out
    3. Re:Great Name... by certsoft · · Score: 1

      A company I do consulting for has named a number of programs after towns in New Mexico in a similar vain: Socorro, Mountainair, Willard, and Cimarron come to mind. But that was when I lived in New Mexico, now that I'm in Oregon that could change, but I doubt anyone will name something "John Day" :)

    4. Re:Great Name... by Anonymous Coward · · Score: 0

      I hope Intel doesn't install go to New Mexico, "Socorro" means "help!!!" in spanish

  7. I think these technologies are a good thing by solman · · Score: 1, Insightful

    Nobody is going to force users of Palladium enabled systems to actually use Palladium. If you are offended that RIAA decides to distribute music that can only be played on Palladium enabled systems, refuse to buy the music. Meanwhile, consider the benefits:

    I'm runing hundreds of different programs on my windows machine. If any one of these programs is subverted by a malicious user, all of the information on my machine is vulnerable.

    With Palladium, etc. it will become possible for programs to keep especially sensitive data safe from malicious programs operating on the same machine. Now an attacker will have to not only subvert one of the programs that I have trusted, it will also have to defeat the Palladium system.

    This is much more difficult than it sounds. It is easy to find a security hole in a machine that is runing hundreds of programs, because only one program out of hundreds has to be defeated. With these trusted computing platforms, software atackers will only have a few possible points of attack, and these have been subjected to much more strenuous security analysis because:

    1. There are only a few places that the effort has to be focused and:

    2. They were specifically designed for security (unlike just about everything else about Windows).

    I don't see how this can be a bad development. At worst its neutral. At best, Palladium will allow me to do all sorts of things on my computer that I wouldn't dream of doing today because of security concerns.

    1. Re:I think these technologies are a good thing by Pussy+Is+Money · · Score: 0
      I'm runing hundreds of different programs on my windows machine. If any one of these programs is subverted by a malicious user, all of the information on my machine is vulnerable.
      "My life is conjoined with thousands of different people in society. If any one of these people is a subversive, all of us are in danger."

      And your solution is to abolish society??

      --
      Pushin' 'n dealin', shovin' 'n stealin'
    2. Re:I think these technologies are a good thing by PhoenixK7 · · Score: 1

      why is this a troll?

    3. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 1, Insightful

      I don't see how this can be a bad development. At worst its neutral. At best, Palladium will allow me to do all sorts of things on my computer that I wouldn't dream of doing today because of security concer

      Wow, really?? What is it that you would so much like to do on your computer but wouldn't dream of right now because of security concerns?

    4. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 0

      If you run only one program which come with windows, lets say IIS on a clean installed machine, everyone could hack you, so downloading or running something micro$oft approved is not hackers-proof.
      The only difference will be that if Palladium-Sheriffs doesn't want you to run Apache (because it doesn't report any benefits to them) they will.

    5. Re:I think these technologies are a good thing by TRACK-YOUR-POSITION · · Score: 3, Insightful

      In case you haven't noticed, most of the big attacks that really impact ordinary users seem to be with code that the user has agreed to run--be it an email forwarding virus or spyware, the user instructed the computer to run the offending code. So how is Palladium supposed to help? If it blocks non-Microsoft endorsed code, it's as evil as Slashdot claims it is. If it runs the offending code, as instructed to by the Outlook or Internet Explorer user, then all of that fancy hardware security added up to exactly nothing.

    6. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 1, Insightful

      Some quick points:

      1) Had Windows been designed with security in mind, applications would have been properly sand-boxed in the first place. Windows has created this problem - why is it necessary to change all the hardware to make it go away? Why not fix the cause: a broken-by-design operating system?

      2) Right now you like Palladium. Wait until something about that machine breaks, and you want to restore a backup to a different machine. Oops - you cannot. All that scrambled data is lost forever.

      3) Right now you can access files with a choice of programs. You can access documents with multiple word processors, you can access music and video files with multiple players, you can acccess bitmaps with multiple viewers. If every one of those programs suddenly, by design, become unable to read each others' data, there will no longer be any choice whatsoever. You'd better like the 'default' program because there will not be any others.

    7. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 0

      Had Unix been designed with security in mind, applications would have been properly sand-boxed in the first place. Unix has created this problem, and was copied by Microsoft - why is it necessary to change all the hardware to make it go away? Why not fix the cause: broken-by-design operating systems?

    8. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 0

      No! This will not change a thing as far as security is concerned. Most of the damage I fix for my customers is due to vulnerabilities/features(?) in M$ software. Since M$ is championing this scheme their software is certainly highest on the list of "trusted" (I don't trust it now, why would I trust it after this?) software. By the time the most common virus or exploitation compromises a system, it is already at the level where the "magic" of Palladium/LaGrande has taken place. It will inherit the "trust" given that program by Palladium/LaGrande.

      The only potential this technology has is to limit what we can run on our computers. The only way to increase security is to do what M$ has steadfastly refused to do: limit the damage that malicious programs may do by restricting access to the most critical portions of the OS and DESIGN critical components of the OS from the ground up to be secure.

      Let's face it. There is a fundamental flaw in the design of Windows networking components. It likely exits in Linux and Unix, also. One of the most common vulnerabilities is "buffer overrun". This involves "tricking" software by telling it that you will send a certain number of bytes and then sending more than that. The broken code (and it most certainly IS broken if it doews the following) somehow EXECUTES the extra information sent to it! This is a DESIGN problem! It happens frequently enough that the underlying mechanism must be common to a whole lot of code in the system.

      Tell me how Palladium/LaGrande is gonna stop that!

    9. Re:I think these technologies are a good thing by Jim+Norton · · Score: 2
      Nobody is going to force users of Palladium enabled systems to actually use Palladium.

      While that MAY be the case for the short-term, i'm sure once it becomes part of the average users desktop M$ will find some excuse to "lock it down" further.

      With Palladium, etc. it will become possible for programs to keep especially sensitive data safe from malicious programs operating on the same machine. Now an attacker will have to not only subvert one of the programs that I have trusted, it will also have to defeat the Palladium system.

      What kinds of malicious programs? Define "malicious"? More importantly, how does MICROSOFT define "malicious"? Could Openoffice.org, a presumably "unauthorized" piece of software be considered malicious if it is able to open a Microsoft Word document? Food for thought.

      I don't see how this can be a bad development. At worst its neutral. At best, Palladium will allow me to do all sorts of things on my computer that I wouldn't dream of doing today because of security concerns.

      Microsoft? Neutral? Neutral EVIL, maybe! :)

      I'm not sure what you mean when you say you aren't able to do things on your PC that you won't be able to do with Palladium in place. I can think of MANY things that Microsoft would try to prevent you from doing with their implementation of Palladium (and not necessarily "illegal" acts such as copying and distributing movies and music.) Palladium is NOT about Freedom.

      --
      -- Jim
    10. Re:I think these technologies are a good thing by solman · · Score: 2

      If Palladium works as it is supposed to, a Palladium enabled application will be able to store data so that no other application can access it, even if the user trusts that application.

      This way when I install a game, I don't have to worry that it could steal my bank account information. No program would be able to access my bank account information unless it was signed by the same company as the program that stored the information originally.

    11. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 0

      Do you often store your bank account information in your home PC? What I'm usually afraid is how the company which I give it to uses it, and *their* security storing this information.

    12. Re:I think these technologies are a good thing by JonnyCalcutta · · Score: 1
      So if I save my files from , picking a random example, say Microsoft Word, I won't be able to open them in any other word processor - even if I want to?
      And since Microsoft products (or their chosen partners) will be the only ones with full access to the palladium specs that would seem very handy for Microsoft and its chosen partners.

      So in summary, either my data is tied to certain proprietary products since that is the only way the products will store data and there is no way to open them with a different product - or users can elect to pass on trust anytime they want and its no more secure for users than it is now.

    13. Re:I think these technologies are a good thing by solman · · Score: 2

      No,

      A word processor is pretty useless without the ability to share files. Nobody is going to use a word processor that prevents this.

      However, your bank will be able to store your account number on your machine such that no program not signed by your bank can access it.

      Microsoft's chosen vendors (and Microsoft itself) will not be able to access this bank account number.

      As far as whether or not it is proprietary, TCPA is the (theoretically) open platform, Palladium is the proprietary Microsoft thing that could possibly be made TCPA compliant but probably won't be. I don't support Microsoft's continual efforts at creating proprietary protocols, but I do support creating something like Palladium/TCPA.

    14. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 0

      Looks like paid testamonials are creeping into the debate.

      It is not technology. IBM already does this with their crypto units, including adding UV XRAY and tamper mechanisims inside the chip before adding epoxy coats.And their software is tested, properly. Cheezy software implementations don't cut the mustard, only buy time; xbox being a prime example.

      I suggest the real reason you don't use your computer is because you know the software is hopelessly flawed, and you are too lazy to use a hybrid system/BSD.

      Greenies should start getting angry now. Crippled PC's will need MORE ENERGY - on instuction decryption, more waste, be less recyclable, and encourage waste, as good hardware should suicide/self destruct after so many blatent attempts.
      Serves California right.

      Legitimate MS users waste hours/days and 100's of dollars on issues that could be solved by an independant software audit.
      Hardware assist will perpetuate the myth that cruddy software is ok.

      An environmental impact statement is needed.

    15. Re:I think these technologies are a good thing by pesc · · Score: 2

      This way when I install a game, I don't have to worry that it could steal my bank account information

      But you don't need Palladium to solve this problem!! If you run Linux, you can do this by using chroot. The problem is readily solvable on todays hardware. But solving this is not what Microsoft is really interested in. If they wanted security for users they could have implemented it years ago. Like other systems.

      The only thing Palladium provides is taking control away from the owner. Really! Think about it!!!

      --

      )9TSS
    16. Re:I think these technologies are a good thing by Anonymous Coward · · Score: 0

      That's the point Microsoft doesn't want people to know. Their shitty software will still produce horrible bugs and stupid e-mail virii. Some of the other things mentioned by others on here is true which is cool (keep some data away from every application except the one that needs it). It's all a matter of how you look at.

    17. Re:I think these technologies are a good thing by Kwil · · Score: 3, Interesting

      With Palladium, etc. it will become possible for programs to keep especially sensitive data safe from malicious programs operating on the same machine. Now an attacker will have to not only subvert one of the programs that I have trusted, it will also have to defeat the Palladium system.

      Yes. This is a very good thing.

      However, the problem becomes when Palladium is the de-facto standard. When you need Palladium on to run pretty much anything, including seeing grandma's last e-mail, because her system uses Palladium by default, then we have a problem.

      Palladium is a bad company's wet dream. Enron's accounting books could be completely unreadable to anything except for the computer they were created on -- "Oops! It got wiped.. sorry sir.." Those pesky e-mails that pointed out exactly how MS was trying to lean on other companies? You certainly wouldn't be able to get hold of them under a Palladium system.. even the copies over at the Netscape office could be set to "expire" and auto-delete themselves after a certain amount of time.

      Or here's a fun one, EULAs that automagically update themselves from headoffice with no warning whatsoever to the user. It's bad enough now when to download a *required* security update, you are forced to accept a change in licensing. If you don't download the update, you lose the ability to obtain support, but at least right now you have the choice. Palladium gives the content owners, (which in this case is the folks who presented the contract) the ability to change the content at any time. Do you really believe that every company out there will be willing to resist temptation?

      Plus, when it's the defacto standard, you start losing the widgets and API's that allow new software to be built without Palladium. After all, if MS can simply discontinue support for W98, what makes you think that they can't discontinue support for non-palladium equipped systems?

      "Your trying to use what API? Oh.. that was before Palladium. We deprecated that a while ago, just use our new Palladium enhanced version now. It provides better security and support. Open source developer? No problems with that. Just so long as you cough up a nickel for every person that tries to use your program, we'll be happy to set up a key for you."

      Which brings us to a point where *all* software has to be licensed through a key provider - and also a point where if the key provider decides they want more money (name me a corporation that wouldn't) they simply increase the charges and/or invalidate current keys.

      Of course, the answer for all this is, "Well don't use it! Use Linux or something." Unfortunately, this assumes that we'll have the choice. The first attack on that choice is coming in the form of legislation. When hardware manufacturers are mandated to have security protocols in their hardware. The second attack is the weight of network effects. As I said, when even grandma uses Palladium, when every major company from here to Timbuktu uses it for the "security advantage", you really lose any choice to not use it. Oh I suppose you could try and be like those die-hards who still make use of FIDO, but beyond hobbyists, you completely lose the ability to connect to the world. This can go even further when major routing points start to use it to increase the security of the entire internet. Prevent DDOS attacks from those nasty non-Palladium machines out there by dropping their packets at the first router. Only Palladium Approved Packets will be accepted, thank you. At that point, even the die-hards will be forced to move to Palladium (or I suppose they could ressurect FIDO).

      Now, will things get this bad? I don't know, this is kind of a worst case scenario, and we all know that it often doesn't get to the worst case. Unfortunately, I really don't see anything that would stop this scenario from happening.

      Finally, on a side note, if you have even a minor knowledge about proper security precautions for your computer then your banking information is likely safer being on your computer than it is being in your wallet.

      Kwil

      --

      That Jesus Christ guy is getting some terrible lag... it took him 3 days to respawn! -NJ CoolBreeze

    18. Re:I think these technologies are a good thing by Alsee · · Score: 2

      If Palladium works as it is supposed to... I don't have to worry that it could steal my bank account information.

      I wish I had Palladium when Code Red hit because it stole my... err, umm, well when Nimda hit it stole my.... ummm... well, you know! It will protect my DRM music and my DRM movies from viruses!

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    19. Re:I think these technologies are a good thing by Reziac · · Score: 2

      Sadly, I think you've nailed it down quite accurately. Once the camel's nose is in the tent, the rest of the camel soon follows.

      Oh, and FIDO (and BBSing in general) is still alive and well, for what little that's worth to the average person. The underground railway for email of the future??

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    20. Re:I think these technologies are a good thing by TRACK-YOUR-POSITION · · Score: 2

      I'm surprised that your comment isn't modded up since it makes more sense than my comment to which you replied. ;)

    21. Re:I think these technologies are a good thing by solman · · Score: 1

      Slashdot moderation is based as much on whether people agree with your views as whether your comment makes any sense. My top level comment was modded up 2 times and down 3 times, the latter not because it doesn't make sense, but because people hate to see disagreement with the official Slashdot position. Meanwhile random MS sucks posts are at +5.

  8. Ha, ha! by Anonymous Coward · · Score: 0

    Imagine a beowulf cluster of these babies!

    1. Re:Ha, ha! by tuba_dude · · Score: 1

      Beautiful! It'd be just like the US government! No communication between units, mountains of red tape (metaphorically speaking, of course), pointless rules to protect the poor saps trapped under it from themselves...

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
  9. Palladium by Anonymous Coward · · Score: 0

    I hear that the designers of Palladium used 'ls' once in a while. Perhaps it should be called GNU/Palladium?

  10. we won't have any rights for the sake of profits by DragonTHC · · Score: 0

    our freedoms are being forsaken to line the pockets of congressmen

    --
    They're using their grammar skills there.
  11. Love ya Billy! by Spackler · · Score: 5, Funny

    Bill Gates is my hero!

    1. Create an insecure operating system

    2. Profit

    3. Blame computers for your insecurity

    4. Profit

    5. Get hardware vendors to make changes to compensate for YOUR buggy software

    6. Profit

    7. Prevent any software except yours from running securely

    8. Profit (by others demise)

    9. Take away everyones choice.
    10 Profit

    11. Blame the computers some more, as you take away more freedom

    12. Profit. Profit. Profit.

    When there is a wolf guarding the hen hose, why on earth would I need the shotgun named Linux?

    1. Re:Love ya Billy! by Alsee · · Score: 2

      .
      .
      .
      12. Profit.

      Heay! Where are all the question marks?!?!

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  12. Useful services, devil is in the details by astrashe · · Score: 5, Interesting

    I was as afraid of palladium as the next guy before the details started to come out, but I think we ought to try to avoid the knee jerk reaction and think this stuff through more carefully.

    A lot of people are opposed to any scheme that can be used to thwart piracy. But in my view that's an extreme and unreasonable position, even when fair use issues are taken into account.

    For a long time it's seemed to me that the thing we ought to be working towards is an open system of distribution, one that can't be dominated by large media concerns, something that gives a guy who makes music at home the same sort of access to the market as the big record labels.

    To me, the issue is not whether or not my computer is capable of running some sort of protected DRM system -- the issue is whether or not it's capable of running alternative systems, if the existence of a palladium aware media player will break my mp3, ogg, and divx players, or my entire open source operating system. As I read these proposals, that's not the case, they won't break things.

    Microsoft has said explicitly that one of the key design goals of palladium was that it shouldn't break existing software.

    In my view, these sorts of services are useful, and we ought to be talking more about "how" then "if" they are implemented.

    In particular, we ought to be sure that software that will run under linux can provide the same sorts of services as a palladium enabled version of windows. I know that the applications themselves couldn't be truly open source (or at least you'd have to use a signed snapshot of an application that was developed using open source methodologies). But I don't think that's enough of a reason to pull back from this stuff.

    There are useful applications for this stuff.

    About a decade ago, one of the hot topics among crypto types was digicash -- cryptographic protocols invented by a guy named Chaum that try to mimic cash, especially its anonymity and security.

    One of the big problems was how to make microtransactions work when you're disconnected from the net. Imagine two palm os devices doing a transaction over infrared. Chaum's answer was to use tamper proof chips.

    Sure, on some level nothing is tamper proof, but it ought to be possible to make tampering difficult enough, expensive enough, and to cap the size of the transactions possible and the rate at which they can be made, in a way that would give people reasonable security. The NSA could hack the micropayment system, but they'd have to spend a million bucks, and all they could get back would be $50, or something like that.

    It seems to me that this kind of hardware could be seen as a more flexible kind of tamper proof chip.

    I think the goal should be that whatever hardware comes out should work with arbitrary operating systems. The trust chain should be decentralized.

    In other words, if I develop an electronic music distribution system, I should be able to develop apps for whatever OSs I choose to support, and I should be able to make my system recognize whatever signatures I feel are trusthworsthy. It ought to be possible for *anyone* to develop such a system, and to use the hooks into the hardware.

    The thing that worries me is that if all we say is "no, palladium is the devil" we won't have any voice in this stuff.

    1. Re:Useful services, devil is in the details by Anonymous Coward · · Score: 0

      You could say, Bill Gates is god and I want his beautyfull babies and you still wouldnt have a say in this.

    2. Re:Useful services, devil is in the details by Anonymous Coward · · Score: 1, Insightful

      Palladium may have some good points, but the problem is that it will lend itself too easily to doing some really bad things. This is made significantly worse by Microsoft being a monopolist.

      If Microsoft decides to "Palladize" all Office documents, competitors like Open Office can forget about ever reading an Office document ever again.

      In that same vein, if M$ decides to make IIS require a Palladium-enabled client on the other side for all its contents (even if you can turn that 'feature' off) you can kiss accessing the web with anything else than IE goodbye.

      Palladium has too much potential for abuse to be allowed to continue - especially given M$ black-as-coal track record for monopoly abuse. The potential harm clearly outways the potential gain.

    3. Re:Useful services, devil is in the details by King+of+the+World · · Score: 3, Interesting

      Firstly, I like you post.

      Secondly, although an individual system can choose not to use Palladium, how difficult is it to do so? What's the social weight against using something else? Can anyone tell me what I'm going to face if I choose to continue using Linux?

    4. Re:Useful services, devil is in the details by TRACK-YOUR-POSITION · · Score: 4, Insightful
      I agree good things can come from some DRM-type solutions in theory--the problem is that outside of theory the asymmetries of the marketplace mess everything up.

      Theoretically, if anyone doesn't like this-or-that DRM enabled feature of a product, they just shouldn't buy the product. But there's a flaw in this reasoning--just as everyone here who screams bloody murder about TCPA is probably going to have to buy a TCPA computer at some point (because that's the only kind they'll sell). Large well-organized corporations simply have vastly more negotiating power than individual consumers in deciding these sorts of things. You deciding not to buy the latest songs from the record companies doesn't phase them, but if large corporations decide not to sell products with feature X, then you'll just do without feature X, period.

      Which means, left to its own ends, the marketplace will encourage software/hardware suppliers to set anti-fair use restrictions once DRM is common. Basically they'll turn their paper EULAs into draconian DRM restrictions.

      Now, one can get on a high horse and just say "well I'll just run Linux and not purchase DRM content and never have to put up with any of that!" Yeah, we'll see how long that makes sense once all music, all movies, and many e-mails require Palladium. Most people use computers for communication--so if they refuse to buy the kind of computer that allows them to send and receive information from the kinds of computers other people buy, then your computer is going to become very useless. Palladium has far more potential to make this a reality than Microsoft Office file formats or Internet Explorer ever could. Remember, in a world of network effects, you're only as free as your neighbor.

      So, while it may be true (if we're lucky) that TCPA can be used from any OS (though as you say, applications and content would need to be re-written to support it), from a utilitarian view things are going to start sucking for ordinary users unless one of two things takes place:

      1. The government or some other entity outside the marketplace has veto power over allowable DRM policies, and uses it liberally.

      2. We can encourage all consumers to say "palladium is the devil!", because even with the advantages you describe, it would still be a very bad thing from the users point of view.

    5. Re:Useful services, devil is in the details by boy_of_the_hash · · Score: 3, Insightful

      You have obviously never been denied entry to a site because you are not using IE. What happens when you become a second class citizen on the net - because your machine is not TCPA enabled? The Open source development model that you describe is all well and good but what happens when I want to recompile my kernel? How is that possibly going to be compatible with a palladium like service? But I don't think that's enough of a reason to pull back from this stuff. If you break your own spine, you will probably never walk again, but don't let that knowledge cause you to 'pull back from this stuff'!

    6. Re:Useful services, devil is in the details by tuba_dude · · Score: 1

      Thanks for a sensible comment from the 'minority' here. However, you can't safely overlook the bad things that have come out of good ideas like dictatorships and such Oh well, whatever happens, I'll be watching with anything from disgust to interest. It'll be a rollercoaster no matter what happens.

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
    7. Re:Useful services, devil is in the details by Salsaman · · Score: 2
      In particular, we ought to be sure that software that will run under linux can provide the same sorts of services as a palladium enabled version of windows.

      That may not be possible. Microsoft has a number of patents in the area of DRM Operating Systems. Microsoft has been working towards this for *years*, don't you think they have considered every angle ?

      So sure, you might be able to run Palladium mode Linux, but you will likely have to use a signed kernel (signed by Microsoft or one of their lackeys - don't even think about compiling your own), and pay Microsoft for the privilege of using binary only security modules. Of course, they will likely set the price for all this to be higher than an equivalent Windows system.

      The thing that worries me is that if all we say is "no, palladium is the devil" we won't have any voice in this stuff.

      Palladium *is* the devil, and the only 'voice' we have is not to buy into it.

    8. Re:Useful services, devil is in the details by antirename · · Score: 2

      Will it break your current *nix OS? No, at least not if you trust the soundbytes coming out of Redmond these days. Will it break your next version? Maybe not, but there's a good chance that the developers will never make it, as they couldn't afford the fee. I think the concept is good, but given Microsofts track record and current fear of Linux we have a right to question their motives.

    9. Re:Useful services, devil is in the details by antirename · · Score: 2

      No, call your congresscritter and let them know what Bill G is up to... assuming they care, but at least it's proactive.

    10. Re:Useful services, devil is in the details by Salsaman · · Score: 1

      I don't live in the US, so that is not really an option for me. But rest assured, I am trying to point out the evils of Microsoft's plans whenever I get the opportunity.

  13. Its a damn good thing .... by bizitch · · Score: 5, Funny

    for Intel and M$ that nobody has claimed the intelectual property rights on idiocy (yet).

    --
    ---- "Logoff! That cookie shit makes me nervous!" - A. Soprano
    1. Re:Its a damn good thing .... by CatWrangler · · Score: 2, Funny

      Don't give them ideas! They may "innovate" there too.

      --

      ---
      When you come to a fork in the road, take it! --Yogi Berra--

    2. Re:Its a damn good thing .... by Anonymous Coward · · Score: 0

      There's too much prior art... all too much of which is within the patent office itself... :)

      Not that that'd necessarily stop them...

  14. wow... by Anonymous Coward · · Score: 0

    I thought they were just talking about implementing this, but I've recently started looking into buying a laptop - To my utter dismay, IBM's laptops (all of them from what I can tell), come already hardware equipped for this.

    Well, I guess IBM is going to lose about $4000 CDN in sales to me. Sorry guys, maybe make something the consumer wants and I'll buy it!

  15. Appropriate.. by kampit · · Score: 3, Funny

    LaGrande eh, named after Largo LaGrande from Monkey Island II no doubt, he's the guy who steals all of Guybrush Threepwoods money.

    1. Re:Appropriate.. by Tony · · Score: 3, Informative

      No, it's named for the city of La Grande, in the northeaast corner of Oregon. Intel codenames its processors after Oregon locations (such as Klamath).

      La Grande itself is a relatively pleasant community, in spite of my ex-wife making it her home.

      --
      Microsoft is to software what Budweiser is to beer.
  16. Who is worried? by fleppir · · Score: 1

    So, they start this initiative now, hardware filters slowly through the system and in some 10 years or so, the **AA corps finally have a market?

    I'm not losing any sleep over this. Who is going to buy DRM encoded media anyhoo?

    --
    I am the Barber of Seville.
    1. Re:Who is worried? by Anonymous Coward · · Score: 0
      I'm not losing any sleep over this. Who is going to buy DRM encoded media anyhoo?

      Have you bought any DVDs lately?

    2. Re:Who is worried? by antirename · · Score: 3

      Maybe not /. ers, but how much of your software do you buy from Walmart? Or hardware, for that matter? You might be part of the elite, but if you're outnumbered and you can't get non-DRM hardware then you're fucked.

  17. The French Surrender Reality by Anonymous Coward · · Score: 0

    'Apparently' in a final nihilistic existential-phenomenological act the French have surrender reality.

  18. But you gotta hand it to them... by Anonymous Coward · · Score: 0

    ...they sure are good at marketing.

  19. WAKE UP. AMD will still be around. by Anonymous Coward · · Score: 0

    HELLO?!?!? McFLY?!?!?!?!? You guys act as if Intel is the only CPU maker in the world. AMD?!? PowerPC?!?!?

    1. Re:WAKE UP. AMD will still be around. by prepp · · Score: 2, Informative

      actually the only big players not into this are apple and sgi..

      sun, amd amongst others are actually PARTNERS in the TCPA ALLIANCE

      im quitting computing and going back to robotics or something now..

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
    2. Re:WAKE UP. AMD will still be around. by Anonymous Coward · · Score: 0

      TCPA is fine, DRM is not fine.

      TCPA boils down to a way to verify the state of your system, DRM is a way to limit the state of your system.

  20. Bullshit-O-Meter by Anonymous Coward · · Score: 0

    1-2-3-4-5-6-7-8-9-10-...-55259285-55259286-5525987
    That is quite a high on the bullshit-o-meter scale.

  21. Guarded Secrets by Anonymous Coward · · Score: 0

    I'm never going to buy hardware that forces me to be restricted in my use of the hardware. As a consumer, I don't want some software developer using protected hardware instead of really good and solid coding techniques. I don't care how much it creates stability in the hardware, if this influences just the average joe who isn't concerned with having a website up accessed by a million people a day (or whatever people need more stability for), than this solution is going too far. I could see this being used in a corporate environment, no prob, but it should never be extended to the end user. It's like using a nuke to kill a deer. Senseless. ok that was a stupid comparison, but, hopefully my point is understandable. Once companies start protecting me "for my own good", they are victimizing me and taking power away from me, and as a citizen, I will resist it to the fullest.

  22. Mono-Palladium by Anonymous Coward · · Score: 1, Funny

    When will Icaza show us the new Mono-Palladium???

    1. Re:Mono-Palladium by Anonymous Coward · · Score: 0
      *Sigh*

      What moderater modded this up? So what, Icaza brought/is bringing .NET to Linux; he just doesn't want to see Linux left behind the curve. Seriously, why must we consistantly bash him?

      All you /. folks really need to get yer heads outa where the sun don't shine; and damn quick, before Linux gets left behind.

    2. Re:Mono-Palladium by tuba_dude · · Score: 1

      I like my head right where it is. If 'keeping up' means 'do what everyone else is doing,' (or more accurately: 'do what the people with money want us to do') I'll go back to the starting line and strap on a metaphorical bungee cord.

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
  23. It's closer than you think... by di0s · · Score: 2, Informative

    Check out IBM's new ThinkPad notebooks, "now with better 'security'"!
    I saw an ad on TV for one of those. Kinda made me cringe. I'm curious as to what kind of TCPA stuff it's got.

    1. Re:It's closer than you think... by Phoenix823 · · Score: 1

      Only IBM offers select ThinkPad® and NetVista(TM) systems with the IBM Embedded Security Subsystem, a hardware- and software-based solution. Select models now feature the TCPA-compliant IBM Embedded Security Subsystem 2.0 to provide the highest level of industry-standard PC security.

      I'd like to know what was in v1.0, what's changed and how many products with v1.0 have already been sold to (perhaps unwitting) customers?

    2. Re:It's closer than you think... by sethstorm · · Score: 0

      Well, at least it's in the high end office stuff for now, most people probably couldnt easily afford such devices, yet. But I'd still say that the 1.0 version's probably in 1) an internal development chip, 2) the standard specification, (with 2.0 being IBM's own improvements), or 3) there's stuff that's probably not in the general public knowledge yet.

      --
      Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
    3. Re:It's closer than you think... by Curunir_wolf · · Score: 1

      You obviously don't understand why IBM is anxious to have this stuff available. They aren't putting all this money into Linux because they are community-minded, it's for profit.

      You know what you need to run Linux on a 390? A $40,000 a year peice of software from IBM!

      How much do you think they will charge for a Palladium-enabled Linux Binary? Sure, you can have the source code, but your custom compile kernel won't be able to do all this neat whiz-bang stuff, because it doesn't have a trusted signature!!!

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    4. Re:It's closer than you think... by di0s · · Score: 1

      I remember hearing that the 1.0 version of TCPA uses a seperate "security chip", whereas 2.0 is supposed to have it embedded in the processor (at least from what I read about Intel and AMD)... Though this may be IBM-specific stuff.

    5. Re:It's closer than you think... by di0s · · Score: 1

      How much do you think they will charge for a Palladium-enabled Linux Binary?
      Palladium = Microsoft
      TCPA = Industry Standard
      Your chances of seeing a Palladium-enabled Linux binary are about the same as trying to sell snow to an Eskimo...

    6. Re:It's closer than you think... by Curunir_wolf · · Score: 1

      You can argue semantics all you want (although I think it is pretty much beside the point).

      Ok, you can call it TCPA-enabling if you want.

      Profit-minded entities like IBM, the UnitedLinux consortium, etc. can use this as a wayt to make money from all kinds of GPL software, without violoating the GPL.

      I still think you can call it Palladium-enabled, though, because Microsoft has the patent on the servers, so you would either have to access a Palladium product, or a Palladium-licensed product.

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
  24. Ultimate Goal by EzInKy · · Score: 1

    "The ultimate goal, the thing that we at Intel are working for -- and let me take a stretch and say the things I think that all of us in the industry should be working for -- is really bringing computing to everyone anytime, anyplace in the world."

    Ummm...no it's not, or if it is they sure have a funny way of going about achieving this goal. How does hardware that restricts the use of software and data increase the availability of computing to people who can neither afford the hardware nor the software?

    --
    Time is what keeps everything from happening all at once.
  25. Why Palladium / DRM Won't Catch On by ZeLonewolf · · Score: 1

    DIVX.

    Not the codec, but the DVD-ish format introduced by Circuit City. It flopped because average-Joe consumer saw it for the fraud that it was, and you can bet that the same will be true when consumers have the choice between a crippled DRM version of something and a non-crippled version of the same.

    DRM will NEVER, EVER catch on with John Q. Public...which is why the effort to implement it via legislation MUST be stopped.

    --
    "If at first you don't succeed, lower your standards."
    1. Re:Why Palladium / DRM Won't Catch On by op00to · · Score: 2, Insightful

      Wrong. DiVX never caught on because there were alternatives available. In this world, windows is the only show in town for most people. Forget linux, it's not even in their head, so they wouldn't think about it. Their business uses windows, their websites require windows, so why not just use windows? If it's the only show in town, you don't have much of a choice.

    2. Re:Why Palladium / DRM Won't Catch On by ZeLonewolf · · Score: 1

      You would be correct other than the fact that there are always older versions of Windows...and in the case that the new Windows.NET (or whatever they call it) is unworkable, M$ will see sales lag...

      I hope...

      --
      "If at first you don't succeed, lower your standards."
    3. Re:Why Palladium / DRM Won't Catch On by spitzak · · Score: 2
      MicroSoft is far more worried about competition from "older Windows" than it is about Linux or even Apple (Linux has about 2%, Apple 4%, but I think "my Win98 machine works" is perhaps well over 50% of the market!)

      So from that point of view, any competitive plans by MicroSoft are probably much more geared to finishing off this "competition". Getting rid of Linux is just a side effect.

      Rest assurred that the old Windows machines will not read palladium-encrypted pages either.

  26. MacOSX by Anonymous Coward · · Score: 0

    Suddenly Apple and MacOSX are looking a _LOT_ more attractive. I currently own both, but I may be forced to get rid of _ALL_ M$ and Intel products.

    Seriously, if they keep this up, I will not buy any more M$ or Intel products.

    We are the consumer, lets show them we mean business with our pocket books!

  27. Re:The sad thing is... (Linux not the answer) by zanerock · · Score: 1

    The "caring software" argument is an interesting spin. I agree, that Linux et. al will not limit users the way MS OSes will (Apple BTW, is making a stand). However, there is still *a lot* to be worried about.

    Consider that once the thing is there on the chipset, people (namely RIAA and friends) will want to use it. With the DMCA and other such laws already on the books, might not be to hard to *require* Linux to use LaGrande (via legislation) and limit your rights. Any supportted, big distro will be forced to add the stuff in or be shut down.

    Once the genie's out of the bottle, it's hard as hell to get him back in again.

  28. no meat here by l0ungeb0y · · Score: 1

    C'mon... reading that article was less informative than a longterm weather forecast, no need to read too deep here, it's mostly fluff.

    Sure, many of us including myself have extreme pause in trusting the Trusted Computing Initiatives being pushed by wintel. But, this particular article provides no new insight and is just pep-rally talk and should not be taken all too seriously.

    Maybe this article is good to raise the issue for CTO's to get some reports drafted on Alternative OS/Hardware means. Apple, though still on the higher end of the price factor is strongly against much of the DRM and "trusted" computing alliance.
    And with more focus on "Office Killers" for Linux and other OS's I think that by the time TCPA and Co. hits the streets there will be plenty of other solutions available. Time however, will tell just how many there will be.

    1. Re:no meat here by Salsaman · · Score: 2
      Apple, though still on the higher end of the price factor is strongly against much of the DRM and "trusted" computing alliance.

      I keep seeing people claiming this, but where is the evidence ? Where is the statement from Apple that they will never support DRM ? Where is it ? What happens when MS says to them - "The next version of Office for the Mac will only run in a Palladium enabled machine" ?

  29. I see it as good. by Richard_at_work · · Score: 3, Interesting

    Im actually looking forward to TCPA and Palladium. No, really i am. It will lighten the load of my job, being a support engineer.

    What im saying of course is it will have its place, on the business desktop, on the childs computer, on public accessable computers etc etc. They have already stated that there will be a option to turn it off, and to be honest all of those who say "Well yes, but what about when they remove that option?" are just scaramongering. Yes true they can remove it in the future, but will it be that easy? I dont think so, there will be too a big outcry, and there will still be large numbers of eastern computer manufacturers making PCs as we know them now.

    As i said at the beginning of my post, i am looking forward to this. Especially if systems administrators will be able to control it (and i bet they will be able to), as this creates a whole new set of security barriers to wouldbe theives etc. Imagine what the outcries were like when the first user account was created on an OS which didnt have full rights to all the system. This is jsut the same.

    1. Re:I see it as good. by Jim+Norton · · Score: 2
      They have already stated that there will be a option to turn it off, and to be honest all of those who say "Well yes, but what about when they remove that option?" are just scaramongering. Yes true they can remove it in the future, but will it be that easy? I dont think so, there will be too a big outcry, and there will still be large numbers of eastern computer manufacturers making PCs as we know them now.

      If done right (and here is where MS may falter), there won't be a big outcry if they turn the option to disable Palladium off. Never underestimate the spinelessness of the average person.

      The PC manufacturers (the ones who count, anyway) are already in their pocket. Both AMD and Intel have pledged support for Palladium. In the future there will be no PC manufacturers making "more free" PC's because doing so will prevent them from being profitable.

      I'd rather "scare-monger" (as you call it) then leave people with a false sense of security by telling them things will be alright when they won't.

      --
      -- Jim
    2. Re:I see it as good. by Richard_at_work · · Score: 1, Troll

      If done right (and here is where MS may falter), there won't be a big outcry if they turn the option to disable Palladium off. Never underestimate the spinelessness of the average person.

      Yes but it has to be done so perfectly, that i doubt it will happen. Look how many people still use word97 format .doc files, even when word has moved onby 2 versions. Try phasing them out.

      The PC manufacturers (the ones who count, anyway) are already in their pocket. Both AMD and Intel have pledged support for Palladium. In the future there will be no PC manufacturers making "more free" PC's because doing so will prevent them from being profitable.

      You really think so? In the same vein as it isnt profitable for Apple to make Macs, or Sun to make sparcs? No, there will always be an alternative, and there will always be unrestricted versions around, as people will always want them. The US isnt the world, remember that.

      I'd rather "scare-monger" (as you call it) then leave people with a false sense of security by telling them things will be alright when they won't.

      Ok, the Earth is about to be taken over by Aliens, the world is controleld by a central secret government, coca cola really is a chemical concoction which makes us susceptable to mind control. Grow up. People love to moan and winge about something, so i guess this is your something.

    3. Re:I see it as good. by Anonymous Coward · · Score: 0

      "Ok, the Earth is about to be taken over by Aliens, the world is controleld by a central secret government, coca cola really is a chemical concoction which makes us susceptable to mind control. Grow up. People love to moan and winge about something, so i guess this is your something. "

      Well, of course there is the simple fact that all those ideas have no scientific merit and require large logical leaps. The idea that MS will phase in Palladium and then make it mandatory is so translucent given our experience with MS and our experience with DRM attempts that I think its clear you're spuriously conflating wild theory and responsible skepticism.

    4. Re:I see it as good. by OeLeWaPpErKe · · Score: 1

      What palladium does

      1. It encrypts data (YOUR data)
      2. It doesn't give you the key (you have to ask the CA (ie M$) "can I please have the key to ..."

      Now imagine what will hapen in the following scenario

      1. You type in an email to a user with subject "Microsoft sucks"
      2. The recipient's system asks microsoft for the decryption key "can I please get a key for the email 'Microsoft Sucks'" ?

      They obviously won't do it the first few months, but this GIVES THEM THE OPTION TO REFUSE. Any data you trust to palladium, microsoft has the ONLY key to.

      Oelewapperke

  30. Re:WAKE UP. AMD will still be around (so?) by zanerock · · Score: 1

    Last I heard, AMD was on board. They're not really in a position to fight MS and RIAA at the moment.

    Apple, on the other hand, is not on board, so, unless things have changed last time I looked (and who knows now-a-days?) you're half right.

  31. Is there any hard info on this? by Animats · · Score: 2
    This is important. But everything I can find via Google is just rehashes of Intel's press release. Is any solid info available on this yet?

    This could be both good or bad. On the good side, it might support multiple virtual machines a la VMWare without the horrid hacks needed to make that work. On the bad side, it could mean that you can't develop code that will run on consumer machines without permission from Microsoft.

    1. Re:Is there any hard info on this? by Salsaman · · Score: 2
      VM Ware are already working with Microsoft to make sure future versions of their software are Palladium complatible.

      The obvious quid-pro-quo from MS would have to be that Palladium will not support virtual machines out of the box.

      Thus, your one good point is not even valid.

  32. It doesn't matter because... by Anonymous Coward · · Score: 0

    they have plenty of prior art.

  33. Not to worry by Badanov · · Score: 1

    There is a great body of software to due a lot of hard work being done over the passed several years, and as long as congress doesn't do anything unconstitutional by outlawing legacy systems, this new Intel position may be more for the rubber knife crowd. But we will see.

    --
    Dawn of the Dead
  34. Time for OpenSource Hardware ! by Proudrooster · · Score: 2, Interesting

    One component that seems to be missing in the whole Open Source realm is hardware control. I wonder if it would be viable or even possible for the Open Source community to co-develop, or at least be able to provide specifications to hardware manufacturers.

    Many hardware vendors are finally waking up and embracing Open Source, e.g. (3ware, Adaptec, Intel, AMD), but it seems as if the community is always fighting with hardware. If worst came to worst, we could all boycott a particular vendor and pledge as a community to buy non DRM (Digital Restrictions Managemet) devices from a competitor in volume.

    After all, DRM is NOT LAW! (Well at least not until Microsoft donates $20,000 to a couple of congressional campaigns).

    Open Source should have Open Hardware!

    Also, I am not worrying too much about Palladium or other "copy protection" type devices. They will be defeated just like every other type of "copy protection" that has ever been invented. In fact reverse engineering Palladium in compliance with the DMCA will probably be a sourceforge project.

    1. Re:Time for OpenSource Hardware ! by Anonymous Coward · · Score: 0

      check out the openbrick

    2. Re:Time for OpenSource Hardware ! by tuba_dude · · Score: 1

      After all, DRM is NOT LAW! (Well at least not until Microsoft donates $20,000 to a couple of congressional campaigns). Which brings up another way to fight it. Along with the push at hardware manufacturers, we could (either seperately or thru a *ugh* special interest group) boycott or support various campaigns based on the amounts already contributed by companies on the black/white-lists.

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
  35. Bad idea by Anonymous Coward · · Score: 0

    I've got a bit of insight on this, since I've worked at Intel on these sorts of R&D technologies in the past, and know how the company works and thinks.

    I was critical of this and other Intel programs designed to limit the abilities of the PC, and in general, give businesses more control over a users PC then the user himself. I'm sure that had a BIG reason in my being "let go".

    Even Andy Grove spoke out against LaGrande, but unfortunately was trumped by now more influential voices on the board.

    What Intel is hoping (and knows) is that all of you WILL be forced to buy a Palladium PC. Of course, you'll have it sitting right next you your NON-palladium PC. You'll probably have a KVM switch right there, able to switch between Palladium and Non-Palladium and the press of a button.

    Hell, manufacturers will probably design a way to put two PC's in one box...and Intel will have sold twice the CPU's.

    I always considered this plan very short sighted on Intel's part. Intel NEEDS to realize that people purchase PC's because of its abilities to be the greatest tool ever invented. The more you limit the abilities of the PC, and the more you allow the RIAA and film industry to turn the PC into just another sales channel, the less value the PC has overall.

    Here is a question for you: If MS/Intel made a PC that could only playback DVD movies, why would you EVER watch a DVD on a PC?

  36. Business list gone secret by Anonymous Coward · · Score: 0

    Now there's no public list about who's on TCPA and who's not... we just can't know

  37. VIA will still be around. by MsGeek · · Score: 2

    VIA is also not in the TCPA alliance. Maybe their CPUs are weak tea now, but the roadmap for the CIII architecture and beyond suggests that it can be extended and enhanced well beyond its current capabilities.

    --
    Knowledge is power. Knowledge shared is power multiplied.
  38. HEY LOOK! by Anonymous Coward · · Score: 0

    it's that fucking genius kid again.

  39. This isn't about palladium! by Oggust · · Score: 1
    This is not about palladium. It's enabling technology for that, but for a lot of other stuff as well. I'm not discussing palladium here, it's a separate thing, good or not. (Sounds bad, but I really don't know enough about it yet to tell)

    Caveat: The article had almost as little info as the slashdot story. ("demo begins and ends"? Huh?). So I don't really know what it is really about. But if Microsoft can use it to implement palladium, we can do some real cool stuff with it. too.

    This seems to be about getting better hardware suppoort for separation of different kinds. This is good stuff. That might mean stuff like:

    • Multics-style divisions within the kernel. (Think of it as a second division like between kernel- and userspace, but inside the kernel. For example maybe drivers can have their own address spaces. Right now, an error in an ethernet driver kan scribble memory inside the scsi driver. Or the mm system. That isn't so good.

      In multics they had a small piece of the kernel in the "center", called the hardcore, and everything else in the kernel interfaced with that much in the same way that userland interfaces with the kernel now.

    • Kind of part of the ealier point, but it was getting long... Maybe we can get a Reference Monitor now. This is a separate part of the kernel, (that the rest of the kernel can't see or write to) that takes all the security desicions, instead of having that stuff spread all over the code. That makes it small and verifiable. (In theory. But it should hopefully be alot easier to find bugs that way.)
    • maybe you can have subdivision between different parts of user code. (libraries vs. app code, private things in OO languages actually being private to that class, all kind of stuff.)
    • Possibly this might make doing different kinds of mandatory access control easier (sonds like it ; that's what palladium sounds like, except the Security Officer is someone who works at Microsoft) If they can do that, we can do traditional MAC.

    I have never seen such a freaking luddite reactoin to new tech here at slashdot. Geez... Were you guys this upset when they added memory protection to the 386 too? This is more of the same.

    /August

    --
    "An object declared as type _Bool is large enough to store the values 0 and 1." -- 6.1.2.5, C99 standard.
    1. Re:This isn't about palladium! by spitzak · · Score: 2
      All your "ideas" amount to there being more than 2 protected modes. Rest assurred that the idea of more levels or rings or splits in rings has been around for 30 years. This is nothing new, and people have already taken advantage of it. I believe that we don't need more than the kernel/user levels and the fact that all the user programs are protected from each other by virtual memory mapping and by all communication going through the kernel. All other solutions are equivalent to moving functions out of the kernel and into user space, a good idea that is only stopped by the annoying slowness of switching between the protected programs. You can be pretty certain that switching between Palladium processes is not going to be any faster.

      When they added memory protection to the 386, you could write software that ran in the unprotected mode. Yes, you could write a system that would lock things up so that a branch of software was unable to switch to protected mode and unable to write outside it's own memory. But you could write that system!

      The difference with Palladium is that it is explicitly designed so that nobody other than MicroSoft can write the unprotected mode part.

      Come on, think a little bit before posting next time.

    2. Re:This isn't about palladium! by Oggust · · Score: 1
      All your "ideas" amount to there being more than 2 protected modes. Rest assurred that the idea of more levels or rings or splits in rings has been around for 30 years. This is nothing new, and people have already taken advantage of it.

      Oh I know (hence the reference to multics, for example), I'm not claiming credit for these things (Well, maybe the protected OO language thing, I don't think I've seen that done anywhere.)

      I believe that we don't need more than the kernel/user levels and the fact that all the user programs are protected from each other by virtual memory mapping and by all communication going through the kernel.

      Well, that is certainly a valid opinion, but I do think more levels would be useful. Again, see the multics example.

      When they added memory protection to the 386, you could write software that ran in the unprotected mode. Yes, you could write a system that would lock things up so that a branch of software was unable to switch to protected mode and unable to write outside it's own memory. But you could write that system!

      Yeah, I'm guessing it's going to work much in the same way here.

      The difference with Palladium is that it is explicitly designed so that nobody other than MicroSoft can write the unprotected mode part.

      Palladium, yeah, I'm sure that's bad. But this story isn't about palladium. It's about cool new hardware that can run palladium. Or other things.

      Unless you think that only MS is going to be allowed to write software for this new hardware (which is ludicrous), I don't see the problem.

      /August.

      --
      "An object declared as type _Bool is large enough to store the values 0 and 1." -- 6.1.2.5, C99 standard.
    3. Re:This isn't about palladium! by John+Hasler · · Score: 1

      You really should take a look at the Hurd.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    4. Re:This isn't about palladium! by antirename · · Score: 2

      If MS hadn't announced Palladium, do you really think Intel would be working on this? Hardware needs software. Otherwise it's useless. They are building this FOR Palladium. If you disagree, please let me know what OTHER platform it's intended for at this point.

    5. Re:This isn't about palladium! by Oggust · · Score: 1
      I'm sure they did build it for palladium. So? That dosesn't mean others can't use it.

      Think intel put memory protection into the 386 so that linux could use it?

      Intel of course knows that there are other things than windows that runs on their hardware. If only MS can write (OS-level) code for this new hardware (if we assume it's even possible to prevent others, which it of course isnt.), Intel would lose a lot of customers, not to mention all the anti-trust and contractual trouble they'd be in.

      Of course the rest of us will also be able to use this hardware! And we'll be able to do cool things with it.

      /August.

      --
      "An object declared as type _Bool is large enough to store the values 0 and 1." -- 6.1.2.5, C99 standard.
  40. Does Intel like losing EU sales? by linuxislandsucks · · Score: 2, Insightful

    Does Intel like losing European Union Sales? All the countire sin this union have expressed the desire to refuse to allow TCPA in their computer systems..They hate oppression by big us companeisand they hate Intel and MS..

    --
    Don't Tread on OpenSource
    1. Re:Does Intel like losing EU sales? by Anonymous Coward · · Score: 0

      If they hate it so much, why doesn't the EU have any chip companies to compete with Intel/AMD, and where's their big OS maker? SuSE?

      I know of *NO* European CPU manufacturers. Why aren't there any? Why do Europeans continually whine about the U.S. having too much control, yet the same European folks never **DO** anything about it?

  41. LaGrande? Largo LaGrande? by vadim_t · · Score: 0

    Hopefully that means that Guybrush (RMS? Alan Cox? Bruce Perens?) will get a voodoo doll and kicks his ass!

  42. *sigh* by Squidgee · · Score: 1
    Every time I read an article about Pallidium on /. or geek.com, my heart sinks. The idea that someone could decide what you can and cannot run is just absolutely depressing to me.

    While many of you may say "I'll just not buy Pallidium-Enabled PCs", that just won't work. Eventually, every PC will be Pallidium enabled, and the only choice will be to run old hardware, and to be unable to run any new or improved programs. Sure, you'll still be able to run Linux on that Pentium 4; but all the new programs will require a Pentium 6. And if they don't, Linux won't be able to take advantage of new hardware; you are damned wether you buy Pallidium PCs or not. And the general, Windows running populus will buy Pallium boxes; they don't care as long as Word, Excel, and the rest run, and run well.

    The only hope for the /. community, and hackers in general, is that we all form a lobbying group, and lobby for Pallidium to be made unconstitutional (And for that to happen, code must be labeled "Free Speech", and there is a precedent against that. But remember, precedents can be overturned).

    While many of you are against lobbying, the only way to beat this thing is to use the power that our government allows us to have. If we don't, we're dommed to a Pallidium Controlled Future.

    Don't say I didn't warn you; the only glimmer of hope for me is my cute little iBook. The concept of a (somewhat) major computing company basing their major product on OSS shows there is hope. But who knows; even Apple may succumb to the power of DRM.

    1. Re:*sigh* by antirename · · Score: 2

      A geek special interest group is an excellent idea. I'd like to see it happen, and I'm registered to vote. Since this would take more work than a /. post, however, I'd be interested to see how many people take you up on this. I'm in, anyway.

  43. And how's your Divx box? by alizard · · Score: 2
    Getting all the new releases?

    Not likely, because the idea of DVDs that expire a few days after purchase was so bad that even Joe Sixpack wouldn't buy into it.

    If you want to give the keys to your computer to anybody but yourself, fine. Publish your static IP address, turn off your firewalls, deinstall your anti-virals, and announce here that you've done this and I'm sure your box will be 0wn3d in a few minutes. Maybe you'll even still get to use it afterwards.

    The rest of us obviously have a lot more sense and a lot less trust than you do. Are you new to the Internet? Do you actually buy products that spammers sell? Is your "herbal Viagra" working?

    "Trusted Computing" is intended to protect the vendors, not the users. We are the ones that are expected to pay for these boxes. I can't think of any actual benefits which DRM-enabling will give me in actual practice.

    If you want to buy it because it's k3wl n3w t3cHn0l0gy, go for it. And post about your experiences, in the post DRM climate, those of us still in the USA will need all the laughs we can get, and those of us who aren't probably deserve some chuckles at US expense as well.

    1. Re:And how's your Divx box? by Oggust · · Score: 1
      Erm... Did you read my post at all?

      This isn't about MS building Palladium, this is about Intel making better hardware, that have more functionality. Sure, on top of that you can build software that does bad things. Or, good things. Like, the ones I listed in the post you replied to.

      Talking about Divx and DRM... This stuff seems completely orthogonal to that.

      Am I new to the internet? No, I've been around for a while, and I happened to notice we need better security. Hence, this is a good thing. (I think it's a really weird tactic to accuse me of being naive and having bad security when I'm arguing that this new, hopefully more secure stuff is a good thing... )

      "Trusted Computing" is intended to protect the vendors, not the users.

      FYI "Trusted Computing" is certainly nothing new, or something Microsoft came up with. Google on terms such as "Trusted Solaris", "Common Criteria", "Mandatory Access Control". Oh, and it's not about giving up control to anyone else, more like the other way 'round.

      We are the ones that are expected to pay for these boxes. I can't think of any actual benefits which DRM-enabling will give me in actual practice.

      I can see that (Not wanting DRM). But DRM-capable hardware will give you benefits, since it's capable of other things as well. See my post.

      /August, was a sysadmin on a "Trusted" (TCSEC b2 rated) DG/UX box back in '95.

      --
      "An object declared as type _Bool is large enough to store the values 0 and 1." -- 6.1.2.5, C99 standard.
    2. Re:And how's your Divx box? by alizard · · Score: 2
      I read what you said. If you meant something else entirely, you really should have said so.

      Your confidence that DRM-enabled hardware will give control to its users and not the vendors is touching. I don't happen to share it and the vendors haven't really given us anything better than "trust us" as the reason why we should.

  44. Superb marketting effort! by Montreal+Geek · · Score: 2, Insightful
    Now, this is about as good as it gets.

    History is replete with Bad Things imposed by powerful entities (be it governement, warring factions, religious institution, corporations, etc). Usualy, those entities attempt to reduce resistance to those schemes by publicising them as good, advantageous, desirable even.

    Censorship is a reccuring favorite. "It would be bad to let the counter-revolutionnaries / heretics / competitors to speak against the System". Another common theme is "We have to protect the weak / children / people against harm and/or themselves".

    This is, however, the first time that I see something so obviously nefarious portrayed in such a positive light!

    The only raison d'tre of Palladium (and the underlying mechanisms) is to prevent people from using their tools to process the data of their choice in the manner they choose. Be it to prevent the "evil pirates" from listening to their CD on their computer, or *gasp* using such-and-such technology without the "safe" and "approved" program (how much are you willing to bet that "approved" software will always be commercial, proprietary and expensive?)

    This would be horrible enough to get even the general populace to react and protest... if it wasn't described as an "enhancement". "Safer" They say (for whom?). "More reliable" (at what?).

    My OS and computing environment are safe enough for the tasks I give them as it is. I don't need "help" protecting me against myself!

    We need to cry, shout and yell loud enough to be heard. The CDA was nothing compared to this, because our computer remained ours, we could always choose to obey the law or not.

    They are trying to take that choice away from us.

    -- MG

  45. What about the developing world. by datadictator · · Score: 1

    I work for a South-Africa company that developes ultra-low-cost educational computer labs for schools. We have cut the cost of a computer-extended education by over 75% allready.

    Nigeria, Zambia and Namibia are allready starting to use this. We are a profit company, but we all (including the owners) work for salaries and the net profits go into cutting the system cost even lower.

    We work in close relation with non-profits and we are really doing something good to improve the quality and availabillity of a proper education in the developing world.

    We achieved this by combining a low-cost broadband approach (satelite) with thin client systems. The children work on old 486 and p1's but the software actually runs on powerfull servers.

    Everything we did is possible ONLY because of Linux. If we were using a windows based solution, our labs would cost more than eight times their current price to build - that's just the licensing. Add the problem of windows requiring newer hardware than Linux and the cost at least doubles yet again.
    I know what I am talking about - I do this for a living.

    The point then - we have to stop paladium.

    This is but one example of how the developing countries are slowly starting to turn their economies around and breaking the cycle of destruction that started post-colonialism by using open-source systems to utilize their resouces better.

    If we cannot run Linux and open office anymore - what can we do ?
    OK so we have no plans to upgrade these pc's in the next few years anyway but what happens when we have too ?
    What will we do if none of the over 2000 labs running on this system can send mail to anybody else anymore ?
    What will we do if the internet becomes so blocked up that our thin clients fail ?
    For that matter we will not be able to upgrade our servers to paladium level because we are talking about litterally hundreds of users needing access to the SAME programs and the SAME documents on the SAME machine - and none of this is illegal not even under the US DMCA.

    I have allready begun rallying our non-profit partners and will continue to do so - our collective voice does get heard at the UN level (they in fact have paid for many of those labs). Africa cannot survive if paladium goes through.
    Bill Gates may not give a shit about that, but I do - this is my home !

    For all those here who have been telling us this is a good thing(tm) - spare a thought for Africa. We are trying to save our home - don't destroy it for the sake of the unholy wood.

    1. Re:What about the developing world. by Skjellifetti · · Score: 2

      Africa cannot survive if paladium goes through.

      Sure it can. And so can Asia and Latin America and even Europe and N. America. Linux will eventually be modified to use TCPA hardware. It will be done in an open manner and you will be able to self-sign your kernel and applications and go merrily on your way using your computer systems just like you do now.

      Palladium is simply MS's API on top of TCPI hardware. It will be an inconvenience for would-be pirates of commercial content and a headache for those of us who would like to be able to back up our legally purchased music, etc.

      But why, in God's name, would the UN Paladiumize its public documents? Or why would any 1st world agricultural research institute put DRM into the pamphlets that they give away free to farmers right now? Do you really think that anyone will tolerate a world where they cannot receive email simply because it doesn't have a Palladium approved DRM stamp?

      Africa has hunger, disease, war, and lack of education among its many problems. Get some perspective. Palladium is not going to mean a thing (pro or con) to those who seek solutions to Africa's ills.

    2. Re:What about the developing world. by Anonymous Coward · · Score: 0

      For the immediate future, you can continue to use what you are using. At a later time, you can form a developing world only internet, to get around the palladium. At a later time, you can create an Africa based semiconductor industry, and make some chips that aren't damned stupid and inefficient. These are difficult, not impossible tasks.

    3. Re:What about the developing world. by datadictator · · Score: 1

      Finally someone sees a little about what I am trying to say here.

      To clear up some points:
      I never said that the UN would paladimize it's doc's I said that the UN could have some influence in stopping this from happening.

      I said that having copyright systems on other people's machines limit WHO we can comunicate with will be a major problem.

      I said that anything which forces us to upgrade will be a problem.

      I said (based on RMS's book) that the inabillity to run ANY Software you want on new computers will be a major problem.

      --
      As to this reply, your solutions are doable - but inadequate.
      What the hell would a developing world only internet be good for ? We want to cross the digital divide, not completely segregate ourselves from the developed world.

      We need to be able to reach an equal footing to europe and america, not make the rift bigger.

      Sure we can build chips here - we have the know-how and the infrastructure allready - but who can buy them here ? They are useless unless we can sell them to the rest of the world as well. Voila - problems if everybody else expects a chip with built-in encryption levels which we cannot get to duplicate because of export restrictions.

      ----------
      The point is however broader than that, this effort will broaden the digital divide by increasingly placing technollogy out of reach of the developing world (and I don't mean just Africa I use it as an example since I live here and travel all over this continent seeking to improve things)

      Have a look at http://netday.org.za to get a feel for what we are doing.
      Paladium will also pose a very real threat to privacy and freedomn - maybe some Americans believe that they can prevent it being used for that. What about the many developing countries where these rights are not even recognized. Do you honestly believe that Robert Mugabe would NOT use this software to further erradicate freedomn in Zimbabwe. I know he would do it in an instant - just like so many others.

      Sometimes Americans can be total hipocrites ( a stereotype I know and I appologize to the innocent) on the one hand you have people proposing laws to ensure the freedomns of people in the developing world by make net censorship impossible. On the other hand you have companies and the goverment pushing a technology that will leave the freedomn of all computer users completely up the whim of goverments.

      This is bad for the developing world. .NET is horrible for our countries because even if you ignore it's other ramifications, it still requires you to be online to work - do you realized how easilly being online for more than an hour a day in South-Africa can cost you the equavelent of $2000 per month ?
      This is worse - because it would leave so little alternative.

  46. turn off? by SpoonMeiser · · Score: 1

    True, you can turn it off, but then you won't be able to view TCPA encrypted media...
    So, "secure" data using TCPA transmitted between people or companies will require trusted apps to read it.
    Now, do you suppose free software will be able to become "trusted"? Given that it's constantly changing and often has little or no funding? I'm thinking that if TCPA becomes widly used, it's going to have a huge negative impact on free software... not that MicroSoft care.

    --

    --
    Hollywood representatives have publicly stated that skipping commercials is "stealing."

  47. Who is paying for this??? by dcavanaugh · · Score: 3, Interesting

    When companies invest R&D money into bigger hard drives, faster CPUs, video gizmos, and slicker GUI interfaces, we all understand the motivation -- increased sales.

    From what I have heard about "LaGrande" and "Palladium", there are benefits for the "gatekeepers", but no benefit for end users. Nobody is projecting increased sales because of these lovely DRM "features". Indeed, many are wondering if people will buy this stuff at all. This would be like McDonalds working on a way to make greasier french fries, because it would help the lard industry.

    So my question is this: "Who is bankrolling this operation?" If Intel/AMD/M$ are really spending their own money on this, it's a mass outbreak of corporate stupidity. Is Saddam Hussein attacking our tech industry with some kind of "dumb-down" bio-warfare weapon?

    My conspiracy theory is that the "LaGrande/Palladium" boxes will be blown out at firesale prices, subsidized by someone who really wants this stuff to be deployed -- kind of like Xbox on a massive scale. The payback will have to come from the victims^h^h^h^h^h^h^h^h customers -- endless fees and hidden surcharges built into everything they do.

  48. You don't know what you are talking about by spitzak · · Score: 2
    There already is hardware support to protect programs from each other. In case you have been under a rock for the past 30 years, all modern machines have virtual memory mapping and kernel and protected mode (and perhaps some other modes). These have in fact been quite well debugged, I have never heard of a virus that works by fooling the processor microcode into switching into kernel mode.

    For protecting from malicious (or more likely buggy) programs, everything Palladium promises is there right now. But machines are contuously hacked (Linux as well as Windows). Why? Because of a thing called bugs. Palladium is not going to stop bugs. It will instead sign bugs and say they are "trusted". Big deal!

    Palladium's purpose is to make sure the owner of the computer can't insert "bugs", and the user cannot fix "bugs", no matter how hard they try or want to do it.

    1. Re:You don't know what you are talking about by solman · · Score: 2

      How does protected mode protect my bank account information, which is sitting on my hard disk? It doesn't.

      Encrypt it you say? Then where do I store the key when my program isn't runing? Either I put it on the net (which requires that I be connected to access anything) or I put it on my hard drive (which leaves us back where we started).

      THIS is the problem that TCPA, etc. are designed to solve. If the owner of the computer can access information, then a malicious program that he installs can access that information too.

      |> Palladium is not going to stop bugs. It will instead sign bugs and say they are "trusted". Big deal!

      Palladium will also make sure that signed bugs from the video game I installed can not access data stored by the signed program my bank gave me. This IS a big deal.

    2. Re:You don't know what you are talking about by Nicolai+Haehnle · · Score: 2, Insightful

      *sigh*

      What you want to do _is_ possible on current hardware. A current-day operating system _could_ implement a signature on executables, and then only allow access to your bank account info to the signed banking program. You don't need special hardware to do this.

      Now obviously, the signature (=trust) on the application is worth nothing if you don't trust the operating system.

      Now let's assume that you trust the operating system in the form that it was installed on your computer. Let's further assume that the OS has means of protecting itself from running applications if the OS itself is loaded. Those are fairly safe assumptions to make, actually.
      So the only way that the OS could be turned malicious (trojaned, whatever) is by booting a different OS on the computer and manipulating the OS from there. However, that is only possible with physical access to the computer.

      So what it boils down to: If your computer is reasonably physically secure - which is the case for virtually all home PCs at least - you can always trust your operating system. Even with current day hardware.

      q.e.d, what you want to do is possible.

      Now, the modified hardware changes one important thing. It can sign the operating system.
      We've just established that this isn't necessary for any reasonable security objectives, right?
      Then why do they want to implement a system which makes signing the OS possible? Well, it's quite simple I think. "They" want to be able to trust the operating system. But since "they" don't have physical access to your computer, "they" need a signature in order to be able to trust the OS. Once they have the signature for the OS, they can then trust the OS to establish trust of applications.

      And the only reason I can think of that "they" would bother to trust your computer and the applications _you_ run is Digital Restrictions Management.

    3. Re:You don't know what you are talking about by solman · · Score: 2

      What you describe is possible in theory, but virtually impossible in practice. It requires that all disk access be accomplished through higher level routines controlled by the OS.

      Capability based systems like EROS have achieved a limited version of this only after many years of effort.

      The consesus seems to be that retrofiting capability based security onto Linux would be monumentally difficult if not impossible.

      If Microsoft asked the EROS folk to add capability based security onto Windows, it would take them days to stop laughing.

      So Microsoft can try to do something that is virtually impossible using just software, or they can use hardware to accomplish the same thing at far less cost, and with greater verifiability. It sounds like an easy choice to me.

    4. Re:You don't know what you are talking about by spitzak · · Score: 2

      If you knew what you were talking about, you would know that capability systems have the ability to grant capabilities from one object onto another. A third party can do this. The entire design of Palladium is to insure that there is no third party.

    5. Re:You don't know what you are talking about by solman · · Score: 2

      You are factually in error. A signed Palladium application CAN share data with third parties. If Universal pictures sells me a movie, their signed movie player WILL be able to transfer the bytes of that movie to another party. [Of course they aren't going to do this, but they can.]

      It will NOT be possible for a third party to obtain access by copying the file, nor will it be possible for a signed application to grant another application access by giving that application a string of bits. But the latter is hardly necessary given the requirements of the system.

  49. Great... by Servo · · Score: 2

    Well, I feel good that I'm running on AMD at least. Next best thing will be when I can switch to Apple equipment.

    --
    A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin
    1. Re:Great... by sethstorm · · Score: 0

      Well, it'll eventually not matter, given that the major companies will switch over, regardless of your chosen platform...

      --
      Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
    2. Re:Great... by Servo · · Score: 2

      In that case, time to switch over to the Timex Sinclair :)

      --
      A slip of the foot you may soon recover, but a slip of the tongue you may never get over. -Benjamin Franklin
  50. Could this be a Good Thing? by Tokerat · · Score: 3, Interesting

    From what I understand, all that will basically happen (besides a few hardware changes to accomodate) is that new commands will be added to the Intel CPUs to allow a portion of memory to be designated as "protected", and I assume possibly even only accessable with a public key perhaps? So, a program can allocate a hardware-locked portion of RAM.

    This would not stop Linux from running. Linux would simply not utilize the feature (or, it could even be added to Linux), and run it's own memory management scheme with software as it does now.

    It will not stop your MP3s from playing. They'll just play in a protected address space. Or maybe they won't depending on your player software.

    This will not stop your DVD ripper from ripping. An alternate driver and ripping program designed to simply not use a feature designed to provide hardware security for applications is not a violation of the DCMA (even if the ripping of a DVD is, which is a different question).

    This will stop someone from using an external program to cheat at a game (the game locks off its memory, the cheat program cannot change the data).

    This will prevent someone from, say, running a malicious program which essentially "core dumps" your RAM at a specific time, maybe when opening your e-mail reader?

    This will possibly stop things like Outlook viruses, as Palladium/LaGrande-aware applications are hardware-isolated into their own address/execution space and cannot interefere with other applications.


    Did I miss something? Should I really believe M$ is dumb enough to make a move which will cause outcry and backlash from the most tech-savvy of users all the way down to the e-mail granny, at a time when the DOJ, along with every man, woman, and l33t-preteen on the planet is breathing down their necks in anger?

    C'mon people, I hate MS too, but they where smart enough to get this far, even if they did hire Balmer...I think that's an obvious move to NOT be making, if they value their asses (assets?) at all.

    Please correct me if I'm wrong, and please post links.

    --
    CAn'T CompreHend SARcaSm?
    1. Re:Could this be a Good Thing? by Anonymous Coward · · Score: 0

      Thank you! Finally someone who can see through all the FUD from the /. crowd. I'd say to mod the parent up, but no body will.

    2. Re:Could this be a Good Thing? by Todd+Knarr · · Score: 4, Insightful

      It will not stop your MP3s from playing. They'll just play in a protected address space. Or maybe they won't depending on your player software.

      I think you misunderstand the use of the protected area. Your MP3s will be encrypted. the keys to decrypt them will be stored in the protected area. Only "trusted" programs will be allowed access to the protected area, so only "trusted" programs will be able to get the keys and decrypt the MP3s. One requirement for "trust" will be that the player provides no way to save the unencrypted datastream anywhere. Possibly it might not even send the stream to a sound card unless that sound card was also "trusted".

      The fundamental problem isn't even the word "trust", it's who can trust the computer. This whole thing isn't intended to insure that you can trust your computer or the software on it. It's to insure that other people (eg. the RIAA, MPAA, Microsoft) can trust your computer. Trust it, that is, to do only what they tell it it can do and nothing else. If you wonder why MS would want that, think back a couple of years to their floating of the idea of annual subscriptions for Windows licenses. Now imagine the glee when they discover a way to guarantee that, if they impose that, you the user can't do a thing to bypass their check of whether you've paid or not because the hardware won't let you touch that data.

    3. Re:Could this be a Good Thing? by antirename · · Score: 2

      Yes... You should believe that... Because most people are stupid and timid and lazy and won't fight back, even if they are smart enought to realize that they are being fucked over. You place WAY too much faith in the general computing population.

  51. Paranoia! Pd does not keep Linux out of Africa by rogersc · · Score: 1

    Paranoia! Palladium does not stop Africans from using Linux. It would make more sense to complain about Rambus making computers more expensive.

  52. I'm not buying it! by Anonymous Coward · · Score: 0


    I don't care what they say.. if the hardware I buy, or the OS, or the software for that matter is 'protected' I WILL NOT BUY IT!

    It's MY MONEY.

    I get to choose what to buy. Now, I've been using PCs (windows mainly, some Freebsd, some linux) for over a decade. If I face the future where a "PC" MUST be hardware protected then I would easily buy a Mac. There is no question what is worth more to me: MY privacy vs THEIR restrictions.

    This is absolute crap! In the future I'll have two machines, or 1 machine with two configurations:
    Config/Machine 1: This machine will never in its entire life see the net. It will be able to see a machine that is linked to the net but it itself won't connect at all (oh, Norton 2002 users: You're screwed here. Buy the software, and the damn thing won't work without an internet connection. Take it back, and the shop says that it works)
    Config/Machine 2: This machine will have access to the net. It will have (at least) a working and configured _personal_ firewall (ie: local firewall like Tiny Personal Firewall that blocks individual programs). This machine will be setup with 3 disks/partitions in it.
    Partition 1: Main OS (assume 1 OS atm)
    Partition 2: Data (may also have data on another computer on the network)
    Partition 3: Restore partition

    Basically, partition 1 will be backed up (ghosted :) ) to partition 3 regularly. The machine can then be backstepped however many steps are required if something goes wrong (hack/crash/whatever).

    So.. some dick writes a new worm or virus? FINE. reghost partition 1 in the morning.

    This situation assumes that I'd still like to use windows. FreeBSD is a much better alternative. Trust me.

  53. Microsoft will not have any keys by rogersc · · Score: 1

    Palladium is not a scheme for Microsoft to archive your crypto keys. Your crypto keys will on your motherboard where only you can get them. Microsoft wouldn't want the responsibility of holding keys for people.

    1. Re:Microsoft will not have any keys by Salsaman · · Score: 2
      If I send an email to you, using Palladium, and I want it 'for your eyes only', then I must obtain your public key in order to encrypt it.

      In order to check whether I am allowed to obtain your public key, my machine will consult a license server, which could be run by Microsoft or a third party. If everything is OK, the license server will instruct your machine to send me your public key. The license server will check the subject of the email to make sure I am not a spammer. It sees that the title is "Microsoft sucks" and marks me as a spammer, and refuses to grant permission to get your public key.

      Far fetched - of course, and I am not saying it will necessarily work like this. But the point I am making is, once you hand control of your machine to MS, you no longer have any say over what it does. MS don't *need* to even know what your keys are in order to lock you in/out.

  54. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  55. MOD PARENT UP! by manyoso · · Score: 2

    This is the most incisive post I have seen on the issue of Palladium. This is a post for the history books!

    Great job man!

  56. Now all they have to do is find by Archfeld · · Score: 2

    people stupid enough to buy it. It won't be the Financial industry or the HealthCare industry, M$ has seen to that. The University clients seem to be wiser and discovering Linux faster than anywhere else, what market do they have to 'penetrate' beyond the average AOL user ?

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
    1. Re:Now all they have to do is find by Salsaman · · Score: 2

      People were stupid enough to buy WinME. I rest my case.

  57. Is this really necessary? by chewmanfoo · · Score: 1

    Why don't these engineers ask, "why are we doing this?" There's got to be more important work that needs to be done somewhere.

    1. Re:Is this really necessary? by Anonymous Coward · · Score: 0

      Posting anonymously obviously.

      My company was recently considering lending our expertise to various TCPA related work at a certain chip manufacturer, but we (the engineers) steadfastly refused as a group.

      Luckily, it didn't come down to a stand off, as management lost interest in the deal. Still, it would have been interesting to see what happened. Would it have come to threats? Would any of us have caved in? How would management have responded to someone who has actual ethics - something they would have limited experience with and understanding of?

  58. Re:The scariest part (Palladium == 1984) by Anonymous Coward · · Score: 0


    Check out this scary faq about Palladium:

    http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

  59. genie has to go back in the bottle. by Anonymous Coward · · Score: 0

    it is this simple.
    Computers coupled with the Internet puts too much
    communications power in the hands of the people.
    Our centralized power structures ( aka the powers
    that be ) have being trying to geld this ever since they realized it had snuck past them.
    Back... in...( huff,puff..strain.) the ... bottle
    you damned ....Genie.

  60. Comment removed by account_deleted · · Score: 4, Informative

    Comment removed based on user account deletion

  61. 1984 by mackstann · · Score: 1

    this is "the man" (whitey) keeping us down.

    this is whitey, trying to keep information from us.

    knowledge == power.

    whitey wants to keep his power.

    whitey wants more power. it has to come from somewhere.

    it will come from you.

    dont give whitey more power. forget about laws and politics and money. see it as a human. you are one person, and other people are trying to keep information from you, so that they can have power over you. intellectual property is a joke, it is only a means of gaining more power. power power power. coming out of your ass.

    why cant mankind rise above this garbage?

  62. Always look on the bright side of life ;-) by Anonymous Coward · · Score: 0

    Most slashdot post look at this from the "Disney is coming for my computer, and Microsoft is bringing them there" angle but I see no reason for Microsoft palladium to be the only application of TCPA. Much as I would like to point out practical possibilities, I cant make heads or tails of the TCPA spec, but at least a "Asymmetric encryption co-processor" and hardware random generator sound useful for most normal (as in non-disney) crypto projects like openssl, gpg and fast-ipsec. Imagen a gigabit Ethernet ipsec enabled router of of the shell hardware with no extra costs as the extra logic comes with the processor at a "normal" price with development paid for by Disney! Even distributed crypto cracking projects might benefit. Ofcourse fun projects are only possible as long as the security and randomness can be proven, no need to directly trust Microsoft, Disney and hpaq yet. But keeping in mind Disney will not like it when Intel and friends make mistakes, excidental or otherwise, things may go very smoothly ;-).

    Also there might be a real political benefit here as well, no politician will go and ask for TCPA power and import/export to be regulated just so worldwide snooping agencies have an easy way in, and even if one does, Disney backed politicians will fight them with Disney money backed campaigns to "safe the future of digital "entertainment""! This might even improve export control on other crypto products. Also by the time normal crypto projects are developing this hardware is likely to be so widespread that fighting it is no longer possible. (A sidenote on the snooping agency thing, if distributed cracking with normal Intel/amd chips is works they will probably be first. [insert tinfoil hat level comment here on the "bania" (low energy x86, perhaps all engery to the crypto part mode is posible in the next chip?) being mostly developed by Intel in Israel, the Israeli government increasing funding for Intel which may or may not be part of the settlement politics and the spooky history of Israeli high tech companies selling stuff with military/spying applications to the civilian market without going bankrupt here, and add an imagen a beowulf of these line])

    I don't see all the implications of the whole "protected storage"/"protected execution environment" and these may be the parts that prevent people not trusted by disney from using this stuff. However they may also make cheap certificate authorities possible. TCPA might keep the root cert and signing code secure/temper resistant and make sure nothing funny is going on in the rest of the system (OS and hardware).

  63. So i'll be paying more money for nothing by Anonymous Coward · · Score: 0

    Its nice to know that these new enabled devices will cost more, because they will be "new" and advertised no doubt all over. When we buy a DVD player (or DVD disc), what percentage of the total price i pay is going towards retarding (also known as encrypting and scrambling, storing keys) the DVD format? They have to pay licenses to use these things, or otherwise they won't be protected.

    I like how lately the new concept in America (and countries that support this) is guilty until proven innocent. We are all going to pay more for this new special hardware and software, because it is assumed we will all pirate, and do insecure things with our PC's. Last time I checked, I can still buy a knife and use it using my own descretion, I can still buy a marker and do whatever I want with it.

    These assumptions are horrible to make, because people have legit uses for these things, and their computers as well, and what I do in my house is fine, as long as I do not get caught. They might as well put us all under house arrest and handcuffs as soon as we're born, at the rate things are going.

    And has anyone noticed that people migrating from older systems will have issues bringing their old data from their older PC to the new enabled TCPA technology enabled machines? Or has this been addressed already?

  64. Ahem by xant · · Score: 2

    A trusted PC interface means that those-that-publish will be able to do so electronically without knowing that it's going to be pirated the next day.

    Horseshit. This isn't what it's intended to do, and believe me, it won't do this. If I make a copy of your software using dd, I've copied the whole thing, encryption and all. Anyone who runs my dd'd copy will have perfectly functional software. Or did you think TCPA would suddenly cause all unprotected computers to disappear?

    Neither do I consider a program being able to lock its own files a bad thing--since MS would be shooting themselves in the foot operatability-wise if it's impossible to tell the program to move the files to "public space."

    Oh, FUCK. Are you kidding? This is Slashdot, I assume you've heard of open source. To get a program signed, you have to pay someone to use their code signing keys. Signing it yourself doesn't work, because the OS doesn't trust "your" keys. That means every piece of open-source software that wants to run on these platforms has to pay to move into public space. They won't do it.

    The software I write is paid for by my organization, and I'm still running into the problem of code signing and paying to make something public. My project's task is to automate Office XP. Office XP won't run macros that aren't signed, which means I have to do one of two things: 1) pay to get a certificate to sign my code or 2) tell the user to install the self-signing certificate, ignoring the very loud warnings that blare when they attempt to do so.

    --
    It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    1. Re:Ahem by SavingPrivateNawak · · Score: 1

      I think your dd'ed disks will not be identical, as HD might contains a unique key put when manufacturing it, key that could be used to decrypt the files...

      (This might poses some interesting problems for RAID...)

    2. Re:Ahem by Planesdragon · · Score: 2

      A trusted PC interface means that those-that-publish will be able to do so electronically without knowing that it's going to be pirated the next day.

      Horseshit. This isn't what it's intended to do, and believe me, it won't do this. If I make a copy of your software using dd...


      Who's talking about Software? Software should be open and free, just like engineering principles.

      The files created by the software, on the other hand, should be able to be locked to one specific program. And it should lose access to those keys if it is simply copied off of the OS install.

      (Can you tell me a legitimate reason to dd an installed piece of software, that isn't covered by one of the apps that MS bundles allready? Palladium is a low-level system change, which means that dd won't work on it.)

      Anyone who runs my dd'd copy will have perfectly functional software. Or did you think TCPA would suddenly cause all unprotected computers to disappear?

      MS has stated, again and again, that Palladium will not suddenly make old PCs obsolete. But its security features will require new hardware, which means that (assuming that they do it right, which they do about 60% of the time) Palladium-apps on an OS install lacking Palladium middleware won't use most of the Palladium features--and the software will be smart enough to know that, and so not certify itself to other PCs that are handing out "trusted PC only" content.

      This is Slashdot, I assume you've heard of open source. To get a program signed, you have to pay someone to use their code signing keys. Signing it yourself doesn't work, because the OS doesn't trust "your" keys. That means every piece of open-source software that wants to run on these platforms has to pay to move into public space.

      You're right, but for the wrong reason. OSS won't need to pay for a certificate to sign itself; people smart enough to use OSS are smart enough to work without a certificate.

      What the OSS folks will have to pay for is a license to include a source code free bundle that works with the Palladium system. MS's agreement says that they have to do this, provided that the OSS companies can demonstrate a model that won't compromise security--which closed-binaries are the only way to do that.

      They won't do it.

      Of course they will. Maybe not all of them, but at least some will pay the fees so they can have software that really, trully works with the latest version of Windows. These will likely be the same (large) OSS developers that pay the RAND fees to get the Win32 or SAMBA specs.

      The software I write is paid for by my organization, and I'm still running into the problem of code signing and paying to make something public. My project's task is to automate Office XP. Office XP won't run macros that aren't signed, which means I have to do one of two things: 1) pay to get a certificate to sign my code or 2) tell the user to install the self-signing certificate, ignoring the very loud warnings that blare when they attempt to do so.

      I work in an office of six people, and the five others have their skill levels max out at using excel or photoshop. ALL of the automation done in the office is done by me, and I get it done well enough.

      And even the worst of them can understand directions like "when this doc gives you this window, hit that button."

      And you forgot 3) : change the macro security setting on Office, and use other means to block the random macro viruses.

  65. Trade our freedom for some rubbish music & mov by Anonymous Coward · · Score: 0

    Please mod the parent (Alsee) up.

  66. With Palladium/TCPA The Users No Longer Decide by frank_slashdot · · Score: 1

    The user still decides what software is trusted or not.

    This is completely false. With Palladium/TCPA the corporations that produce restricted hardware, restricted software and restricted media decide what is trusted on consumers' computers and what it is not.

    That is what Palladium & TCPA are indented for: To confine the consumers' abilities in respect to their hardware and software, by creating a system of restrictions, which they call it "trust" in order to fool consumers into buying restricted hardware & software.

  67. "Trusted" Computers can break your security by frank_slashdot · · Score: 1
    You are not right. Restrictive "Trusted Computers" are those that can break your security

    Read the TCPA / Palladium FAQ here:
    http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html

    23. But isn't PC security a good thing?

    The question is: security for whom? You might prefer not to have to worry about viruses, but neither TCPA nor Palladium will fix that: viruses exploit the way software applications (such as Microsoft Office and Outlook) use scripting. You might get annoyed by spam, but that won't get fixed either. (Microsoft implies that it will be fixed, by filtering out all unsigned messages - but the spammers will just buy TCPA PCs. You'd be better off using your existing mail client to filter out mail from people you don't know and putting it in a folder you scan briefly once a day.) You might be worried about privacy, but neither TCPA nor Palladium will fix that; almost all privacy violations result from the abuse of authorised access, often obtained by coercing consent. The medical insurance company that requires you to consent to your data being shared with your employer and with anyone else they can sell it to, isn't going to stop just because their PCs are now officially `secure'. On the contrary, they are likely to sell it even more widely, because computers are now `trusted'.

    Economists have noted that when a manufacturer makes a `green' product available, it often increases pollution, as people buy green rather than buying less; we may see a security equivalent of this `social choice trap', as it's called. In addition, by entrenching and expanding monopolies, TCPA will increase the incentives to price discriminate and thus to harvest personal data for profiling.

    The most charitable view of TCPA is put forward by a Microsoft researcher: there are some applications in which you want to constrain the user's actions. For example, you want to stop people fiddling with the odometer on a car before they sell it. Similarly, if you want to do DRM on a PC then you need to treat the user as the enemy.

    Seen in these terms, TCPA and Palladium do not so much provide security for the user as for the PC vendor, the software supplier, and the content industry. They do not add value for the user, but destroy it. They constrain what you can do with your PC in order to enable application and service vendors to extract more money from you. This is the classic definition of an exploitative cartel - an industry agreement that changes the terms of trade so as to diminish consumer surplus.

    No doubt Palladium will be bundled with new features so that the package as a whole appears to add value in the short term, but the long-term economic, social and legal implications require serious thought.

    24. So why is this called `Trusted Computing'? I don't see why I should trust it at all!

    It's almost an in-joke. In the US Department of Defense, a `trusted system or component' is defined as `one which can break the security policy'. This might seem counter-intuitive at first, but just stop to think about it. The mail guard or firewall that stands between a Secret and a Top Secret system can - if it fails - break the security policy that mail should only ever flow from Secret to Top Secret, but never in the other direction. It is therefore trusted to enforce the information flow policy.

    Or take a civilian example: suppose you trust your doctor to keep your medical records private. This means that he has access to your records, so he could leak them to the press if he were careless or malicious. You don't trust me to keep your medical records, because I don't have them; regardless of whether I like you or hate you, I can't do anything to affect your policy that your medical records should be confidential. Your doctor can, though; and the fact that he is in a position to harm you is really what is meant (at a system level) when you say that you trust him. You may have a warm feeling about him, or you may just have to trust him because he is the only doctor on the island where you live; no matter, the DoD definition strips away these fuzzy, emotional aspects of `trust' (that can confuse people).

    Remember during the late 1990s, as people debated government control over cryptography, Al Gore proposed a `Trusted Third Party' - a service that would keep a copy of your decryption key safe, just in case you (or the FBI, or the NSA) ever needed it. The name was derided as the sort of marketing exercise that saw the Russian colony of East Germany called a `Democratic Republic'. But it really does chime with DoD thinking. A Trusted Third Party is a third party that can break your security policy.

    25. So a `Trusted Computer' is one that can break my security?

    Now you've got it.

  68. Please mod the parent up by Anonymous Coward · · Score: 0

    Please mod the parent up.

  69. DIVX failed because of bad marketing by Anonymous Coward · · Score: 0


    Wrong.

    DIVX has failed because of poor marketing. Microsoft and other big corporations will unleash a massive marketing/PR/disinformation/advertising campaign that will make sure that Palladium/TCPA will succeed fooling people into buying restrictive hardware and restrictive software.

  70. RMS is nuts by rogersc · · Score: 1

    Aha, RMS is the source of your confusion. RMS has his own personal reasons for hating Palladium. There is a long list of things that he hates. There is nothing in Palladium to keep Africans from using computers. It sounds like you are against any new technology because it might potentially add expense or be misused.

    1. Re:RMS is nuts by datadictator · · Score: 1

      Well I certainly never expected to be acused of being a ludite. I am a techno-geek of the first water. Which is exactly why I am opposed to paladium. Not just the potential for misuse but the severe potential for destroying innovation. The impact this could have on hobbyist programmers is frightening.

  71. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  72. TCPA tech basics by apweiler · · Score: 1

    German mag c't had an extremely good article about the technical stuff behind all this, at http://www.heise.de/ct/02/22/204/ - if you understand German, or want to try babelfishing it... and it's nice to see how critical they are of this, as it's one of the biggest and most respected IT magazines here.

  73. Could be hacked! by ExEleven · · Score: 1

    When you think about it, this technology could be "hacked" because if you think about it... All you have to do is put some software on your Gateway (for example) that doesnt let the fritz chip send anything to Microsoft.

    But you could make it send fake auth keys to the TCPA servers and all that stuff.

    I also ditched XP because i am furious with Microsoft for this. And even if i like games that are not availible on Linux i decided to make a stand. People who can not make sacrifices are a bit selfish. And i will also switch from PC to Compaq Alphas, or Sparcs or somthing. Even if the PC was a cheap nasty peice of hardware. Actually, id probably go with a 2nd hand G4 for now, and upgrade it.

    But heck; We all need to either protest or just make sacrafices to avoid this crap.

    Note: I have nothing against Anti Piracy...

  74. Re:The sad thing is... (Linux not the answer) by oconnorcjo · · Score: 2

    ...However, there is still *a lot* to be worried about.

    Consider that once the thing is there on the chipset, people (namely RIAA and friends) will want to use it. With the DMCA and other such laws already on the books, might not be to hard to *require* Linux to use LaGrande (via legislation) and limit your rights.
    ...

    That has nothing to do with what intel is doing but what legislators are doing and that is a completely different story and irrelevent to what intel is implimenting.

    --
    I miss the Karma Whores.
  75. Re:The sad thing is... (Linux not the answer) by zanerock · · Score: 1

    What you say is probably what many believe, but it is also foolish. These things do not exist in a vacuum. What corporations do/want to do and what laws get passed (either via the legislature or from the bench) are, will be, and have always been tightly intertwined.

    What is maybe less common, historically, but which is a fairly obvious possibility given the current political climate and policies of the government, is that capabilities introduced by technology will begin to drive legislation.

    There are two primary factors that I see behind this. First, is the simple enablement. The government is less likely to pass laws (or interpret laws to the effect of) limiting peoples rights without a clear way to enforce the law. DVD encryption and the DMCA are an example of this. Why didn't the government do this with VHS? There was pressure to do so, but the industry could not propose any means of enforcement. If the government passed laws that were simple to break and impossible to investigate or prosecute, then respect for laws in general would begin to break down. Especially when there exists a strong and ever-present temptation to break the laws for immediate gain.

    The DVD consortium, however, proposed a viable (albeit weak) mechanism to protect their medium and proposed a comprehensive plan to enforce it. There were holes, but it was enough to allow congress to do what they always want to do, help out corporations.

    There were many other factors behind the DMCA, and I'm not saying that DVD encryption schemes and policies were sufficient, nor even necessary, but they were a factor, though probably not even the largest (at least not directly).

    The other main drive, which has already been alluded to, is industry support. When large companies get together and commit to a technoloy, the government knows that the spin and marketing will get behind whatever it is they are doing. This allows them to do things that, without such support, would be largely unpopular and hurt their chances at getting re-elected. But, with all the money that the government knows will be put behind such self-serving efforts, they can have their cake and eat it to; that is, pass laws detrimental to the rights of their constituency for the benefit of their corporate backers, and still appear to be serving the public interest.

    This is a very realy possibility with the LaGrande/Palladium/etc. effort. Besides the work of Intel and MS, the real effort is to make DRM (an misnomer which is already part of the spin and marketing campaign) is a larger effort supported by AMD, RIAA, Hollywood, Sony, etc. With all the money behind the thing, you can bet that not noly can congress be assured of billions being spent to alter or obscure the public perception of the truncation of their rights, but also in millions of dollars of campaign contributions, lobbyists, and outright bribes flowing into their pockets if they, the congress, plays ball with the industry effort.

    So, to say that what Intel is doing has nothing do with what legistlators are doing, or that the objectives, goals, and actions of the two are irrelevant, is both short sighted and dangerous. In stating such a thing, you are failing to make even the first, and most obvious connections.

    If nothing else, consider this: it is the goal of Intel/MS/etc. and (the bulk of) congressional reperesentatives/senators to increase their power/make money. LaGrande/Palladium/etc. is a mechanism by which they both can do precisely that. So, they will, at the expense of the people.

    I am not saying that your assertions or conclusions are without basis. Not at all. They have a strong basis. But, what you fail to realize is that that basis is rooted in the governmental/corporate infrastructure itself, and so necessarily and naturally will bias the basis, and thus your perceptions, to serve it's own interests. You should be very wary of such entaglements.

    You might want to look into the legal history of America, and critical thinking skills. If you would like, I would be happy to suggest a number of excellent titles in both areas.