Slashdot Mirror


Army to Require Trusted Platform Module in PCs

Overtone writes "Federal Computer Week is reporting that the U.S. Army will require hardware-based security via the Trusted Platform Module standard in all new PCs. They are a large enough volume buyer that this might kick start an adoption loop."

337 comments

  1. call me cynical, but by hxnwix · · Score: 3, Insightful

    Army requires TMP so that it can circumvent single-vendor prohibition and be Intel(R) only.

    1. Re:call me cynical, but by Dachannien · · Score: 3, Informative

      AMD drank the Kool-Aid some time ago.

    2. Re:call me cynical, but by donaggie03 · · Score: 1

      ok. . . . CYNICAL!!

      --
      Three days from now?? Thats tomorrow!! ~Peter Griffin
    3. Re:call me cynical, but by hector_uk · · Score: 2, Informative

      "OMG, you may not mention that our pet poster-boy company is just as evil as the very very evil monopolist. You have to say "Oooooh, but in AMD's case, blah blah blah ...", and since Apple's MacOS X includes mandatory activation even surpassing the invasiveness of Vista, you also have to say "Oooooh, but in Apple's case, blah blah blah ..."." OS X requires no activation, it does not even have a CD key, every retail copy is identical so it's impossible for apple to tell if you pirate it, that registration screen is mainly to set up user details such as your address book and that apple can send you crap to your email address if you neglect to check tick boxes. what the fuck does this have to do with anything.

    4. Re:call me cynical, but by zootm · · Score: 1

      Please do not feed the trolls :)

    5. Re:call me cynical, but by buswolley · · Score: 2, Funny

      No, don't feed bad humans.

      --

      A Good Troll is better than a Bad Human.

    6. Re:call me cynical, but by hector_uk · · Score: 0, Offtopic

      how exactly am i the troll for pointing out how someone is completely wrong, you don't even have to do the registration, all you have to do is not connect to the internet.

    7. Re:call me cynical, but by zootm · · Score: 1

      Touché.

    8. Re:call me cynical, but by buswolley · · Score: 1
      Actually.. I never read your post. "Don't feed the trolls," he said. Then I looked at my sig.

      My apologies. It was just in jest.

      --

      A Good Troll is better than a Bad Human.

    9. Re:call me cynical, but by Panzergheist · · Score: 1

      No, no, no. I don't think you understand what that word means. You see, you make a point and I make a counterpoint and... oh nevermind.

    10. Re:call me cynical, but by Anonymous Coward · · Score: 0

      As if Intel is the only vendor supporting TPM?

    11. Re:call me cynical, but by buswolley · · Score: 2, Funny

      I see your point and raise it one counterpoint. ~~ Touches!

      --

      A Good Troll is better than a Bad Human.

    12. Re:call me cynical, but by mobby_6kl · · Score: 2, Funny

      I see your point and QUESTION YOUR SEXUAL PREFERENCE

      ~~ Touches?!
      goddamn lameness filter.

    13. Re:call me cynical, but by hpavc · · Score: 1

      To boot, if you dont register your Apple and later you want help with it, they will regsiter it then and help ya for free. Most other vendors getting help in any way or shape sucks.

      --
      members are seeing something, your seeing an ad
    14. Re:call me cynical, but by Sirfrummel · · Score: 1

      That's actually a good point, and I am actually surprised you were modded Troll.

      I am not familiar with Mac OSX at all, so when you clarified that there wasn't actually any activation at all, your post was actually insightful; which I learned something from.

      Hmm, must be because it's a Friday.

    15. Re:call me cynical, but by uncoveror · · Score: 1

      If they Army doesn't change their minds post haste, Chinese intelligence will know their business! Read more.

      --
      The Uncoveror: It's the real news.
    16. Re:call me cynical, but by buswolley · · Score: 1

      You made me laugh.

      --

      A Good Troll is better than a Bad Human.

  2. Oooh great... by masklinn · · Score: 5, Insightful

    The question still remains whether the user himself can trust the trusted computing platform.

    If your government or seller or whatever doesn't trust you, doesn't even try in the least, how the hell are you supposed to trust him? The most logical path would be to fully distrust him. And therefore to distrust and refuse trusted computing platform.

    --
    "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    1. Re:Oooh great... by FSWKU · · Score: 2, Funny
      If your government or seller or whatever doesn't trust you, doesn't even try in the least, how the hell are you supposed to trust him? The most logical path would be to fully distrust him. And therefore to distrust and refuse trusted computing platform.
      Careful, we ARE talking about the Army here. I follow what you're saying, but this circular logic might cause someone in the Army to have an aneurysm from having more than a minimal amount of neurons firing!



      (BTW, I have a lot of respect for the Army as I have a lot of friends on active duty, and almost became a soldier myself. Still, I couldn't pass up a chance to make a military joke)
      --
      "So after all this, you make my case for me. To end this stalemate, you must die..."
    2. Re:Oooh great... by KiloByte · · Score: 3, Interesting
      BTW, I have a lot of respect for the Army as I have a lot of friends on active duty, and almost became a soldier myself. Still, I couldn't pass up a chance to make a military joke)
      The US army includes a load of good folks (and a much smaller number of bad ones). The soldiers are not the problem, their superiors are.
      To be exact, the problem is that one of their superiors got bribed by a criminal company. If someone whose duty is to manage security doesn't recognize snake oil and backholes in TPM even with all the publicly available opinions, it's either the person guilty of sabotage or is unfit for that position -- and if his superiors allowed such an inept person on such an important position, at least one of the superiors is guilty of sabotage as well.
      No doubt they are all busy helping repress the freedom fighters in the Iraq and making it part of the American Empire.
      Wait... so people who spend most of their time blowing up mosques are suddenly "freedom fighters"?
      They deserve to be named anything else than "terrorists" about as much as Kerry deserves to be named something else than "corrupt populist" or your fearless leader "despot", "liar" and "criminal" (yeah, I may be a dirty foreigner, but I can read the Constitution he swore on or the laws he broke).
      PS - You dont need to make military jokes, the military are a joke.
      The military is fine, the mafia that controls it from above is not.
      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    3. Re:Oooh great... by KDR_11k · · Score: 1

      When people criticise any larger group they usually criticise the leaders and their policies. Do you think that when people say they "hate america" that they really care about Joe down at the burger station? No, they're talking about the decision makers.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    4. Re:Oooh great... by Anonymous Coward · · Score: 0

      To be exact, the problem is that one of their superiors got bribed by a criminal company.

      As a soon to be former member of the US Navy, I can personally vogue for the existence of stupidity and corruption in the buying decisions made by those who have been bought. Would you buy a fiber-optic LAN that runs at 10mb/s and runs Windows NT 4.0? Cisco routers from 9 years ago? For a brand new ship? Corruption and stupidity.

      I just hope my resume can recover from the time-warp.

    5. Re:Oooh great... by jcr · · Score: 2, Interesting

      No doubt they are all busy helping repress the freedom fighters in the Iraq and making it part of the American Empire.

      You're confused. The last American Empire was the Inca empire, which was conquered by the Spanish in the 1500s. Several European empires later held parts of America. There is no American Empire today.

      As for freedom fighters, be clear about to whom you're referring. There are many freedom fighters in Iraq, including Iraqis, Americans, Britons, and people from many other countries. They are in uniform, and they take great care to avoid civilian deaths wherever possible.

      There are also a contingent of cowardly, rabid theocrats who are inflicting mayhem on any large crowd of people they can find, in hopes of establishing their particular perversion of religion as a dominant force in the region. If you're referring to the suicide junkies as "freedom" fighters, then you're a blithering idiot.

      the military are a joke.

      Be glad you live in a country where telling a joke doesn't get you flogged to death for heresy, you ungrateful little twat.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    6. Re:Oooh great... by DarkVader · · Score: 1, Insightful

      Make no mistake, there are NO American, British, or people from any other country than Iraq who are in Iraq fighting for freedom. They may think they are, but they have been deceived.

      Those people are fighting for American domination of Iraq, and the expansion of the American Empire. And there IS empire building going on today.

      That doesn't make the islamofascists freedom fighters either - but while some of the individual foreigners in Iraq might be interested in helping Iraq obtain some measure of freedom, their commanders ARE NOT.

      Iraq is a mission of oil profits, "daddy had a war, I want one too" and a new crusade. It's not about freedom at all.

      And your "flogged to death" comment seems to me to be another way of saying "it's worse other places, so be happy that it's really bad here".

    7. Re:Oooh great... by ultranova · · Score: 1

      The military is fine, the mafia that controls it from above is not.

      That makes about as much sense as saying: "Mafia killers are fine, the mafia bosses that control them from above are not." In fact it's exactly the same, since US Army enforces the will of US government, just like Mafia killers enforce the will of Mafia leaders.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    8. Re:Oooh great... by rgravina · · Score: 0

      If I had mod points, I'd be modding you +5, Right On!

    9. Re:Oooh great... by geminidomino · · Score: 2, Funny

      It's just a jump to the left....

    10. Re:Oooh great... by c_forq · · Score: 1

      Why would the British, Iraqi, and other foreign armies be fighting for establishment of an America Empire? And this wasn't a "daddy had a war, I want one too"; this has been in conservative republican think tanks since before Bush took office. The flogged to death comment was spot on, how is it bad here? You have no repercussions on criticizing the Bush administration, military officials, or anyone (as long as you don't stray into libel, slander, or threats).

      --
      Computers allow humans to make mistakes at the fastest speeds known, with the possible exception of tequila and handguns
    11. Re:Oooh great... by masklinn · · Score: 0, Offtopic

      the British

      Blair is Bush's lapdog...

      Iraqi

      Few still take cause for the US, and those who do only do it because they're too deeply involved, and they can't turn back anymore.

      other foreign armies

      Prefer being on the good side of the US govt.

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    12. Re:Oooh great... by spirit+of+reason · · Score: 1

      I disagree on this separation. It's true that the Army has a lot of good people, but a significant portion of the rank and file is made of people that joined after making a mess of their lives before. The American military has a very poor reputation in many countries because of the awful things some do both in times of peace and war.

    13. Re:Oooh great... by goldspider · · Score: 2, Interesting

      I'd say it's more like "We didn't like how you were doing things before, so we're going to change them." Call it an expansion of the Monroe Doctrine, if you will. And yes, the prospect of getting large amounts of oil from a nation other than Saudi Arabia was most certainly a factor.

      Not saying that any of this SHOULD have happened. It just sounds like your reasoning is grounded solely in your dislike for Bush, and that makes a poor basis for a rational argument.

      --
      "Ask not what your country can do for you." --John F. Kennedy
    14. Re:Oooh great... by Anonymous Coward · · Score: 0

      Yeah, the US military forces are pretty bad. Almost as bad as UN peacekeepers.

    15. Re:Oooh great... by technococcus · · Score: 1

      Dirty fer'ner you may be, but you just made a hell of a lot more sense than basically every American politician and most American citizens I've met.

    16. Re:Oooh great... by KiloByte · · Score: 1

      Well, the US military is nearly a bunch of freaking angels compared to, let's say, Polish (to a small extent) or Russian one.

      The majority of Polish soldiers are elementary school dropouts who weren't able to skip the service. The service is nominally mandatory, but it is so easy to avoid it that you have to be either a fanatic or a moron to join it. As one can expect, the hazing is a rule rather than an exception, and when a group of soldiers get released, you better not have to go anywhere by a train.

      In Russia, the soldiers are hardly provided with food, not to say a word about any actual organisation. Thus, their military is a savage mob of robbers, rapists and bullies rather than a civilised army.
      When they invaded Poland in 1939-40 and 1942-89, we could get a good glance at thugs who hardly know what a toilet is. After, let's say, 50ties, the government started isolating Russian troops from the civilians for this very reason -- the typical setup was a detachment of Russians surrounded by a number of Polish military encampments, with the ground between full of mines, trenches and watchmen who shot people on sight -- in the times of peace! Polish soldiers weren't ever sent into Russian camps, all orders were passed by selected Russians sent outside. An average soldier wasn't even allowed to go to town during his entire service.

      I'm repeating what my grandparents said (about WW2) and my dad said about his military service in the end of 60ties -- but note that in that time, the Soviet Union was "powerful". Now, as they can't even afford to supply the troops with basic necessities, I don't expect it could be better. No one ever bothers to guard nuclear facilities -- so what are the chances that the army has any discipline?

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    17. Re:Oooh great... by jcr · · Score: 1

      Make no mistake,

      Good advice, but you've already ignored it.

        there are NO American, British, or people from any other country than Iraq who are in Iraq fighting for freedom.

      Oh, so you know the motives of every man and woman there? You must be psychic or something. Or just psychotic.

      Iraq is a mission of oil profits,

      Bullshit. If we just wanted the oil, we could have just kept buying it from Saddam.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    18. Re:Oooh great... by andrewman327 · · Score: 1
      "The soldiers are not the problem, their superiors are."


      Such a universally applicable statement. Just replace the word "soldiers" with whatever fits the situation, like coders, employees, middle management, geeks, etc. Damn those superiors!

      --
      Information wants a fueled airplane waiting at the hangar and no one gets hurt.
    19. Re:Oooh great... by spirit+of+reason · · Score: 2, Insightful
      Bleh, enough about American "empires" already. I don't doubt that the Bush administration decided to go to war to secure resources (i.e. oil), as has been the case for a lot of the fighting in the past. However, it doesn't mean that another reason for going to war was to liberate the Iraqis. On top of that, there was the perceived threat of terrorist organizations in the 9/11 aftermath. You have to make a case for every war, and usually, if economic interests don't play into the game, the US doesn't go. Instead, she employs sanctions and attempts to freeze assets. The US generally tries to control things through economics, not the military; the military is just used to keep the economics weapon sharp.

      So tell me... what countries have become a part of this "American empire"? What nation is really not a nation because the US has taken sovereign control over it (besides Iraq, which needs to develop more widespread support so it doesn't collapse)? There is a big thick line between allies and business partners, and empires.

      I don't think Bush is following daddy, but he does seem to be trying to make a Reagan out of himself. I think he wants to be regarded as a hero among his conservative base like Reagan was for "ending" the Cold War (barf... the USSR was collapsing on its own). Too bad he's just a bully; seriously, who came up with the oxymoron "hardline diplomacy"? He should be sacked!

    20. Re:Oooh great... by Anonymous Coward · · Score: 0

      The American military has a very poor reputation in many countries because of the awful things some do both in times of peace and war.

      In reality, there is some high profile cases but very few. They become high profile because it involves the military. You will find much more terrible and nasty things happening in any large american city on a daily basis committed by regular citizens but those are not as exciting to report and glorify in the news. I can only assume that the same things happen in every country. You have been brain washed by the "for profit" news media. Another example of riding along on a media explotion, terrorism. More people die a every year in the US from many individual forms of cancer then from every act of terrorism against an american citizen combined. Where is the "war on cancer", how about that 15 trillion to fight cancer?

    21. Re:Oooh great... by stewwy · · Score: 1

      Everyones forgetting that saddam was toppled for the simple reason that he was threatening to sell his oil in euro's not dollars, this would have meant the beginning of the end for the mighty dollar. Once one country got away with it others would follow suit. So in a way Oil was the reason, but just not in the way everyone seems to think.

    22. Re:Oooh great... by spirit+of+reason · · Score: 1
      Well, I actually base my statement on anecdotes and the media (very bad combination, but what else can I do? Unfortunately, it doesn't matter though because it only takes a few bad incidents to make the general populace of any country angry.). I've heard this from some people that were stationed in Korea for awhile when I was younger, then reports from a friend of mine who is currently in Japan (says he's disgusted with them, etc.). But yeah, I'm not terribly happy with the general population either, haha. But it doesn't excuse the people in the military who really need to be the most well-behaved to prevent so much of the stigma of the military.

      I'd love a war on cancer! Too bad that enemy is harder than the Vietnamese or the terrorists... Those damn cancer cells aren't afraid of dying, have virtually infinite numbers, and aren't affected by standard weapons!

    23. Re:Oooh great... by samkass · · Score: 1

      The US army includes a load of good folks (and a much smaller number of bad ones). The soldiers are not the problem, their superiors are.

      In my current job, I've met and worked with several of those superiors. These are NOT dumb people; not by a long shot. In fact, I'd call your average American Army General a rather brilliant, engaging person to talk to. And while I've heard rumor from civilians of a stereotypical "grunt" in the armed forces who does what he's told like an unthinking automaton and can't reason his way out of a paper bag, I've never met one of these mythical people in the actual armed forces.

      In any case, if you don't like what the Army's current strategic goals are, you need look no further than the Commander In Chief. Everyone else is just trying to accomplish his goals as best they can. Although you'll never get another chance to vote him out of office, you can certainly decrease the power of those who think like him by getting out and voting against Republicans this year and in 2008.

      But we're getting off-topic. The real issue is whether TPM contains anything that might be useful to an army in encryption and identification. And I'd argue it undeniably does. Sure, there are downsides to TPM, but this is one case where the module might be honestly handy to have.

      --
      E pluribus unum
    24. Re:Oooh great... by xanalogical · · Score: 2, Informative

      > a set of regions locally ruled by governors, viceroys or client kings in the name of another

      Empires come in different flavors, not just militaristic but economic, philosophical, legalistic, etc.

      The American Empire partly arises from a careful weakening of the sovereign membrane between countries, such that they begin act as one, with direction from a power center outside of many of them. Some examples:

      1. The US hooking into the European SWIFT financial network to monitor non-US transactions.

      2. The US requiring air flights that _both_ originate and terminate in other countries, such as Canada, to comply with US laws, in _case_ the flight strays over US airspace (reciprocal rules do not apply re US flights that might stray into Canadian airspace).

      3. US tracking of Canadian financial and medical transactions, because the companies in Canada are multinationals with offices in the US, and therefore such transaction data *leaks* across the border into various processing centers.

      4. An effort to apply US copyright and patent laws around the world, for a more uniform legal environment.

      5. The destruction of many privacy safeguards in Europe because the US finds they get in the way of security and business.

      The US is dictating terms to other countries - it is not a give-and-take healthy interaction of equals, with foreign ideas having an equal chance to take root in the US. The other nations look more and more like those "client kings", ruling with the permisson of the multinationals, many of which are based in the US.

      I'm NOT saying something silly like Bush is an emperor. I'm saying the US is calling the shots, for many countries. Probably a better term would be the American Hegemony - the dominance of one group over other groups, with or without the threat of force, to the extent that, for instance, the dominant party can dictate the terms of trade to its advantage; or more broadly, that cultural perspectives become skewed to favor the dominant group.

    25. Re:Oooh great... by giorgiofr · · Score: 1

      Looks to me like most terrorist attacks do not target the decision makers... rather, lots of Joe Burgers.

      --
      Global warming is a cube.
    26. Re:Oooh great... by KiloByte · · Score: 1

      Only if the secret keys belong to a different set than those owned by Intel, Microsoft and co. And since we're talking about purchases from private companies, this is not the case.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    27. Re:Oooh great... by Anonymous Coward · · Score: 0

      It may seem stupid, but I'd imagine that if it's part of the ship's design, has been extensively tested, is used by other ships, etc., the consistency (for both human operators and general robustness) is much more valuable than the meagre cost savings that could be achieved by using cheaper, more modern components (assuming the vendors still offer support for the old equipment, which I expect they do).

    28. Re:Oooh great... by rdoger6424 · · Score: 1

      And then a step to the right!

      --
      "Hello 911? I just tried to toast some bread, and the toaster grew an arm and stabbed me in the face!"
    29. Re:Oooh great... by Garrett+Fox · · Score: 1

      "The military answers would be overkill... Not because we're that much smarter than a billion teenagers, but because we have the Secure Hardware Environment. Down at the bottom we control all the hardware."
      -Vernor Vinge, Rainbows End

      --
      Revive the Constitution.
    30. Re:Oooh great... by besenslon · · Score: 1

      There is no American Empire today...

      C'mon mods - either mod me flamebyte, or mod the parent "Funny".

    31. Re:Oooh great... by trix7117 · · Score: 1
      The service is nominally mandatory, but it is so easy to avoid it that you have to be either a fanatic or a moron to join it.
      Or Polish?
    32. Re:Oooh great... by NockPoint · · Score: 1
      There is no American Empire today.

      The United States was modeled on the Roman Republic. Rome did not stay a republic, as perhaps you might have heard.

      There are clearly trends in the United States that might suggest that the same might happen to the USA. We wouldn't have someone called the Emperor, however, we would likely call the absolute boss "President". We would likely still have a Congress and Senate, however any laws they passed that were not "requested" by the President would be repealed by a "signing statement". Or just ignored.

      --

      Warning, .sig file missing or unreachable.

    33. Re:Oooh great... by KarmaMB84 · · Score: 1

      You just described what it means to be a world superpower. China will be doing the same thing when they grow up.

    34. Re:Oooh great... by Znork · · Score: 3, Insightful

      "There are also a contingent of cowardly, rabid theocrats who are inflicting mayhem on any large crowd of people"

      Just to keep you from getting confused; you do realize that the US removed the secular bunch from power and replaced them with the theocrats, right?

    35. Re:Oooh great... by Anonymous Coward · · Score: 0

      You're wrong on two points:

      1. Saddam Hussein didn't threaten to start pricing Iraqi oil in euros, he actually did start pricing Iraqi oil in euros, in 2000.

      2. Despits Iraq's conversion from (US) dollars to euros for it's oil sales, the euro remained weak until Paul O'Neill, the then finance minister of the USA, remarked that the Bush government were not pursuing a strong dollar policy (which triggered a massive sell-off of dollars, with much of the outflow going to euros, despite that fact that, with a stagnant euro-zone economy, a strong euro was the last thing the euro-zone needed).

      Iran and Venezuela are both considering pricing their oil in euros (for obviously political reasons, like Saddam), so if the 'petroeuro' theory you're regurgitating is correct, we should expect to see Bush sending the American military into both countries any day now. I very much doubt it will happen.

      In my view, it's fairly obvious why Bush invaded Iraq: he knew the sanctions had become untenable, and wanted to prevent Iraq under Saddam rearming, and thereby potentially destabilising the region again, as it had done in 1991 (triggering the recession which had led to George H.W. Bush being voted out of office). In the event, American colonisation of Iraq has proved to be at least as destabilising as a rearmed Iraq under Saddam could possibly have been, and probably very much more so, but for some inexplicable reason, the Americans re-elected Bush in 2004 (Kerry was admittedly a weak opponent, but next to Bush, nearly anyone looks good).

    36. Re:Oooh great... by Chazmyrr · · Score: 1

      It's not so much about encryption and authentication as it is preventing the circumvention of security on military computers. Allowing only boot images that have been properly blessed makes unauthorized access much more difficult. This is a very good thing.

    37. Re:Oooh great... by KDR_11k · · Score: 1

      It's not very easy to hit a guy who has three layers of bodyguards around him. I remember when Bush visited some small town in Germany the entire town got locked down and the policemen outnumbered the inhabitants by the factor ten.

      Terrorism isn't about damage, it's about the fear the attacks spread. The reaction by the attacked that would ideally weaken its position (with the expense of a few men and some tousands of dollars Bin Laden made the US throw away trillions of dollars, destroy its international diplomatic reputation, introduce intrusive laws and throw its military power at two countries for a gain that would never cover the expenses).

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    38. Re:Oooh great... by jcr · · Score: 1

      saddam was toppled for the simple reason that he was threatening to sell his oil in euro's not dollars,

      Oh, so the two unprovoked invasions of neighboring countries, the use of chemical weapons on both Iranian soldiers and his own people, and his playing chicken with the weapons inspectors had nothing to do with it?

      You ignorant putz.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    39. Re:Oooh great... by jcr · · Score: 1

      I don't doubt that the Bush administration decided to go to war to secure resources

      Then you are profoundly ignorant of the matter. It's far easier and cheaper to buy oil from the dictators than to do the hard work of toppling them.

      Oil is fungible, and is traded in worldwide markets. If Saddam refused to sell any oil to the USA, the net effect is nil. When any buyer gets oil from a particular source, he doesn't have to buy it from another source. If we didn't get any oil from Iraq, then we'd just buy the Nigerian, Mexican, Canadian, North Sea, or US domestic oil that Saddam's buyers weren't buying.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    40. Re:Oooh great... by jcr · · Score: 1

      Secular, my ass. The Ba'athists worshipped Saddam, the same way that commies worshipped Stalin.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    41. Re:Oooh great... by spirit+of+reason · · Score: 1

      That's far too simplistic. If you want to hurt the largest consumer of oil in the world, you don't just stop selling to them; you cut production so prices rise. Conversely, if you want to lower your oil prices, you become buddies with the producer and influence their production levels.

    42. Re:Oooh great... by stewwy · · Score: 1

      ignorant putz yourself if you don't know the difference between a reason and an excuse!

      Oh and why the big wait between the use of the chemical weapons and the invasion? a couple of decades wasn't it? before the first gulf war?
      Oh and where are the weapons of mass destruction?
      If by two invasions of neighbouring countries you mean the earlier attack on Iran then which country was it who encouraged it and provided the arms? (I'll give you a clue, by your post, you're probably living in it, and a reason, the recently deposed leader of Iran being american backed)

      How many other countries can you name that have done the same or worse to their own people without being invaded?.

      Of course saddam was/is an idiot and war criminal who made it easy, and I'm in no way excusing his behavior. It would have been difficult (but not impossible) if Iraq was a nice democracy.

      I can probably name 2 other leaders who probably should be on trial with him.(just an opinion)

      If you want to throw insults around and call people ignorant putz's at least don't put up straw arguments and TRY to get your facts correct, instead of spouting propaganda


      >BR>
      Those ignorant of history are condemed to repeat it, those who study it can win most arguments :)

    43. Re:Oooh great... by drinkypoo · · Score: 1, Offtopic

      Just to keep you from getting confused, you do realize the US is currently being run by a would-be theocrat who believes that God works through him, and has said as much publically?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    44. Re:Oooh great... by jcr · · Score: 1

      Those ignorant of history are condemed to repeat it,


      Go look up Neville Chamberlain.

      those who study it can win most arguments :)

      That's why you're looking so ridiculous.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    45. Re:Oooh great... by Znork · · Score: 1

      Tsk. Unless you actually study history you'll never learn from it, nor understand what is happening around you. There were actually understandable, altho perhaps misguided, reasons the west supported Saddam against Iran; Iraqs secular rule being the foremost of them. The fact that the west has now more or less handed the theocrats a whole new country and ally speaks volumes.

      With the idiots running the show it doesnt matter how much you spend on the military; the application of force you can accomplish serves not the american people, but whoever tricks the administration.

    46. Re:Oooh great... by stewwy · · Score: 1

      If thats all you can pick up on, and are now decending to ONLY insults I consider I've won the argument :) and consider this thread ended.

      Regards

    47. Re:Oooh great... by jcr · · Score: 1

      I consider I've won the argument

      Wishing doesn't make it so. Which, BTW, is a good thing to remember when considering history.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    48. Re:Oooh great... by stewwy · · Score: 1

      at least the last part of your last comment I can agree with :) but probably for different reasons lol

  3. Payoff by Anonymous Coward · · Score: 0

    This is one of the benefits of military research and mass purchase, the public sector. When the manufacturers produce for the military for awhile they will make available a civilian brand. The public will also benefit from the r and d.

  4. This does not lockout Linux by DrJimbo · · Score: 5, Informative
    TFA says:
    Is TCG creating specifications for just one operating system or type of platform?
    No. Specifications are operating system agnostic. Several members have Linux-based software stacks available. In addition to our work on the PC platform, we have a specification for Trusted Servers and are working to finalize specifications for other computing devices, including peripherals, mobile devices, storage and infrastructure.

    --
    We don't see the world as it is, we see it as we are.
    -- Anais Nin
    1. Re:This does not lockout Linux by kcbrown · · Score: 2, Interesting
      No. Specifications are operating system agnostic. Several members have Linux-based software stacks available. In addition to our work on the PC platform, we have a specification for Trusted Servers and are working to finalize specifications for other computing devices, including peripherals, mobile devices, storage and infrastructure.

      This doesn't answer the question at all.

      It all depends on who controls the root certificates that are used by the trusted computing hardware to verify the signatures of the BIOS and of the boot image. If you think it'll ultimately be someone who is "friendly" to Linux and open source in general, think again. There's a very good chance that Microsoft, or someone beholden to them, will wind up with control.

      If that happens, Microsoft will have complete control over the set of OSes that can run in "trusted mode" on these computers. And you can expect entities like the Army to insist that there be no way to run an "untrusted" OS on these computers without some sort of magic certificate or something, which conveniently only entities like the Army will get.

      I, for one, don't want to depend on the good graces of a company like Microsoft for such a thing.

      So yes, it does lock out linux, unless we get really, really lucky. Who here wants to bet on that? Not I.

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    2. Re:This does not lockout Linux by Morgaine · · Score: 1
      It all depends on who controls the root certificates that are used by the trusted computing hardware to verify the signatures of the BIOS and of the boot image.

      If the FOSS fraternity are left out in the cold by the certificate authority, this will lead to some almighty class-action type litigation. It would be utterly anti-competitive to lock out a huge potential competitor, and Europe in particular would have a field day with Microsoft. Look at the trouble MS got into merely by locking people to their browser.

      It's one thing to use TPM to ensure your PC is "trusted". It's totally another to use it to ensure that you PC is running Microsoft or Mac software.
      --
      "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
    3. Re:This does not lockout Linux by SiliconEntity · · Score: 4, Informative

      It all depends on who controls the root certificates that are used by the trusted computing hardware to verify the signatures of the BIOS and of the boot image.

      I'm sorry, but you don't know how Trusted Computing works. Almost everything you have been told about it is a lie.

      There are no root certificates used by TC hardware to verify the signatures of the BIOS and the boot image.

      What happens is that the BIOS, OS loader and potentially the OS itself send information to the TPM chip about the hashes of the software that is loading. User software can then, if it chooses, query the TPM chip and get a cryptographically send message telling what these hashes are. The software can use this to report the software configuration that booted.

      The root certificates get involved because the TPM crypto key never leaves the chip. The TPM manufacturer has a root certificate which it uses to sign each TPM key. This way people can tell that a message actually comes from a valid TPM and not a fake. It prevents virtualization of TPMs. This is what allows software to report its configuration in a trustable way. It is what gives the system its name, Trusted Computing.

    4. Re:This does not lockout Linux by Meor · · Score: 0

      Thank you, for this proper chastisement of the ignorant.

    5. Re:This does not lockout Linux by ultranova · · Score: 1

      The TPM manufacturer has a root certificate which it uses to sign each TPM key. This way people can tell that a message actually comes from a valid TPM and not a fake. It prevents virtualization of TPMs.

      Unless the root certificate gets stolen.

      Not that I would ever advocate such a thing, goodness, no ! It would mean that we, the computer owners, would have complete control over our property - and then Disney might lose potential future profits ! Clearly Disney's intellectual property rights trump our property rights !

      So no matter what you do, don't hire anyone to steal the key !

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    6. Re:This does not lockout Linux by mpcooke3 · · Score: 2, Informative

      While doubtlessly you are technically correct, for desktop computing i'm not sure it makes much difference.
      Since only the windows hash will allow secured files to be open and secured apps to be run.

      Microsoft will easily be able to convince the MPAA/RIAA that the only safe hash is the windows one and make the office formats "secured" to the windows hash. Some organisations like debian may not wish or be able to restrict peoples rights to their own machine so there will be no reason for anyone to value their hash (also you can bet microsoft will give kickbacks to companies that allow their formats to only play back under a windows hash).

      Ultimately everything that normal users want like to read files, play music, watch films, read emails could result in requiring a windows hash, at what point microsoft might as well just be doing all the signing with their own Root key all other OS hashes are useless. Except this way is slightly preferrable to Microsoft because the technology looks platform neutral.

    7. Re:This does not lockout Linux by asuffield · · Score: 1

      That does not mean that they won't simply require the TPM to validate the system as running Windows.

    8. Re:This does not lockout Linux by The_Noid · · Score: 1

      There are no root certificates used by TC hardware to verify the signatures of the BIOS and the boot image.
      There are root certificates, and they are used to verfiy signatures of everything that runs on your computer. If you don't give in to this verification, someone else will be able to deny you access to certain functions. (be it the latest Disney movie, or in the end even access to the internet)

      What happens is that the BIOS, OS loader and potentially the OS itself send information to the TPM chip about the hashes of the software that is loading.
      And how does the TPM chip know that the information that the bios/os loader/os itself sends to it is actually the real information about the bios/os loader/os and not faked information from an unmodified version?

    9. Re:This does not lockout Linux by kcbrown · · Score: 1

      I'm sorry, but I don't buy this description. The reason is that if it works the way you describe, then the entire process is vulnerable to replay attacks (send the same set of hashes to the TPM to be signed, and you'll get the same message back that you would if you were the *real* software in question -- so all one needs to know are the hashes in question).

      Furthermore, it implies that all one need do is supply their own BIOS and bootloader code that uploads the hashes from the original BIOS and bootloader and the OS underneath will be none the wiser because the message it gets back from the TPM will be exactly what it's expecting to see.

      So what, exactly, is secure about this arrangement?

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    10. Re:This does not lockout Linux by mrchaotica · · Score: 1

      Actually, the problem is the need for a certificate authority to begin with. Consider: the point of Free Software is that you can modify and recompile the software yourself. However, even if you start out with a "Trusted" version, as soon as you do that it's not "Trusted" anymore. Therefore, unless you have access to the private key to sign it yourself, the "Free" part of "Free Software" is destroyed. It doesn't matter who the certificate authority is; the mere fact of having to rely on an outside entity to sign every new binary you build is enough to kill it.

      (This is one of the things the GPL v.3 is trying to fix, by the way.)

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    11. Re:This does not lockout Linux by SiliconEntity · · Score: 1

      And how does the TPM chip know that the information that the bios/os loader/os itself sends to it is actually the real information about the bios/os loader/os and not faked information from an unmodified version?

      This happens via a staged-boot process.

      The BIOS itself in a TPM computer has a non-flashable portion that runs at startup. This takes a hash of the rest of the BIOS and feeds it into the TPM. The BIOS then hashes the boot loader into the TPM (Grub, in the case of Linux) before transferring control to it. The boot loader can hash the OS before switching control to that. The Trusted Grub project on Linux has been enhanced to do this. Then you could have the OS hash application data into the TPM as it loads; so far only a few experimental projects do that, like Enforcer.

      Now, the BIOS is hard-wired to tell the truth. But the later components could lie. You could have a patched boot loader (it's open source!) which does not send truthful data about the OS kernel and configuration to the TPM.

      But you couldn't get away with this fraud. Recall that the BIOS hashes the boot loader and sends the data to the TPM before running it. If you patch Trusted Grub to lie, it will have a different hash, and the TPM will be told about it. (Note, the TPM doesn't have any "expectations" regarding what these hashes are supposed to be, it just remembers what it was told and can report it later, signed with a crypto key.) So with this concept, if someone knows what the system "fingerprint" is supposed to be of a secure BIOS + Trusted Grub + Enforcer Linux boot sequence, it's impossible for you to patch it and end up with that same exact pattern.

    12. Re:This does not lockout Linux by SiliconEntity · · Score: 1

      Furthermore, it implies that all one need do is supply their own BIOS and bootloader code that uploads the hashes from the original BIOS and bootloader and the OS underneath will be none the wiser because the message it gets back from the TPM will be exactly what it's expecting to see.

      Good question. The way the system works is kind of subtle. This is perhaps why so many people prefer to believe the falsehoods that our out there, about how the system will only run signed code and keep you from changing your own software.

      The TPM chip is completely passive in a TC system. It relies entirely on the BIOS, bootloader and OS to feed it data. Yet the system is designed to be secure. Here is how it works.

      The first part of the BIOS is non-flashable in a TC system. It is hard-coded to hash the whole rest of the BIOS and feed that data to the TPM, first thing.

      Then the BIOS, before transferring control to the boot loader, hashes it and sends the hash to the TPM.

      And the boot loader similarly hashes the OS and some config files, sending that data to the TPM, before transferring control. The Linux Trusted Grub project has a patched boot loader that does this.

      The TPM can later report these hash values, signed with an on-chip crypto key that can't be spoofed.

      People would need to know what these values are supposed to be on an untampered system. Then there's no way to alter a system and let it boot such that the TPM gets the same values and so you could fool people about what you are running. For example, you could try patching Trusted Grub to send a fake OS hash to the TPM so you could lie about what OS version you were booting. But recall that the BIOS hashes the boot loader before executing it. If you've changed Trusted Grub, it will have a different hash, and this will be reported to the TPM. (Keep in mind that the TPM does not check these hashes for "correctness", it just remembers them and can report them later.)

      So yes, you can patch your boot loader to lie, but you still won't end up with the same system configuration "fingerprint" because the boot loader got hashed and the TPM told about it before it got control. In this way the system achieves the ability to security report its boot sequence and configuration, even though people can change the software involved.

    13. Re:This does not lockout Linux by Sloppy · · Score: 1

      Replace the non-flashable BIOS with a different chip.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  5. Whenever I think of Trusted Computing... by Rolling_Go · · Score: 3, Funny

    ...I think of one of those dirty con guys that wants you to play three card monty or something. "Come on, it's not rigged....trust me." Yeah, sure buddy.

    --
    sup
  6. Macs only? by sakusha · · Score: 2, Interesting

    Is TPM actually shipping in any product other than the Intel Macs?

    1. Re:Macs only? by lukas84 · · Score: 5, Informative

      Lenovo Thinkpads and Lenovo ThinkCentres. (Select Models).

      My R51 has one.

    2. Re:Macs only? by Anonymous Coward · · Score: 0

      May be they just want an XBOX..

    3. Re:Macs only? by linguae · · Score: 1

      My friend's Gateway laptop (17" with Intel Core Duo 1.83GHz) has a TPM chip, but he says that it is nonfunctional.

    4. Re:Macs only? by jrumney · · Score: 2, Interesting

      I have a Dell laptop with a TPM chip, which was also non-functional until explicitly enabled in the BIOS. I enabled it to play with the file encryption functionality it offered, but it turned out to be impractical. Judging by the performance I get, the TPM chip seems to have a 9600 bps serial bus connecting it to the motherboard.

    5. Re:Macs only? by SiliconEntity · · Score: 1

      There may still be some controversy about whether TPMs are in all Intel Macs. In any case, there doesn't seem to be any software way to access them, unlike PCs.

      TonyMcFadden.net has a reasonably up to date list of systems that have TPMs in them, as well as manufacturers of the chips themselves, software suppliers, etc.

    6. Re:Macs only? by marcello_dl · · Score: 1

      I, for one, welcome the TPM enhanced, chinese manufactured, Army computing gear...

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    7. Re:Macs only? by Last_Save · · Score: 1

      TPM is in a few Tablet PC's as well. Dell's brand of Tablet PC hs a TPM "feature." It acutally persuaded me to not buy that model, and sticking to getting an older tc1100 from HP. I just hope that manufacturers keep listing if they have a TPM module or not.

    8. Re:Macs only? by technococcus · · Score: 1

      Some Dell Lattitudes (D610+).

    9. Re:Macs only? by jafac · · Score: 1

      Was this comment supposed to be Funny?

      Because the DoD just issued a directive a few weeks back forbidding integrators from using Lenovo-branded machines. Because they're made in China.

      Typical government.

      1. Don't use Lenovo-branded machines, because they might be a trojan horse for Chinese spies.
      2. You must use a technology (which is only currently available in Lenovo-branded machines).
      3. Profit?

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  7. Two sides by Anonymous Coward · · Score: 0

    The bad - It's trusted computing giving complete control of what software will or will not run on your computer to the vendors.

    The good - When everybody starts to see their TCO of software go through the roof, open source solutions look a whole lot more attractive. It also will call attention to how unreasonable software vendors are with there pricing models.

    Of course, Microsoft has gotten away with WGA (for now), but I do sense that rank and file are restless.

    1. Re:Two sides by advocate_one · · Score: 1
      The bad - It's trusted computing giving complete control of what software will or will not run on your computer to the vendors.

      BZZZT wrong... with a Linux based software stack, you should be able to sign your own code and thus ensure only code you've signed and code signed by others YOU trust can be run...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    2. Re:Two sides by segedunum · · Score: 4, Informative

      BZZZT wrong... with a Linux based software stack, you should be able to sign your own code and thus ensure only code you've signed and code signed by others YOU trust can be run...

      Signing your own code is not what he's talking about. Signed, and encrypted, code downloaded to run on your machine from elsewhere and how it is used is totally at the mercy of what vendors stipulate can be done with it. If they want an effective way of timebombing software because you haven't paid up then they have the framework to do that. If they want to break data protection laws and start communicating usage statistics and other sordid details, encrypted and safe from prying eyes, then they now have a means for doing that. It also means that it is almost certainly going to be nigh on impossible to switch to a competing vendor's products.

      Some people seemingly have no idea what the trust in Trusted Computing actually means. What it means is that external people and organisations, particularly software vendors, content companies etc. have a way for them to trust my computer or equipment. Whether I can trust the computer or electronic equipment I own, and what software run on there actually does, is an entirely different matter. It's a fundamental shift in the idea of how computers work that will probably end in anarchy and chaos.

      http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

    3. Re:Two sides by mrchaotica · · Score: 1
      ...almost certainly going to be nigh on...

      Holy excessive qualifying statements, Batman! (Aside from that, well said!)

      It's a fundamental shift in the idea of how computers work that will probably end in anarchy and chaos.

      Those of you who don't understand what the parent post means, read this.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    4. Re:Two sides by segedunum · · Score: 1

      Holy excessive qualifying statements, Batman! (Aside from that, well said!)

      Probably a bit excessive, but taken to its logical conclusion it can be used as a huge means of vendor lock-in. There's nothing bad about the technology of Trusted Computing on its own. It's just a case of who has the keys and who's in control.

    5. Re:Two sides by mrchaotica · · Score: 1

      No, all I meant by that was that instead of saying "it is almost certainly going to be nigh on impossible," you could have simply said "it will be impossible" and been done with it. I think vendor lock-in is an inevitable result, not just a probable one.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  8. Re:Mod points please! by Anonymous Coward · · Score: 0

    The hardware TPM almost made me not buy a macbook. . .

  9. Trusted by Descalzo · · Score: 4, Insightful
    From what I understand, Trusted in this context is used as in "I entrust it with my security" rather than "I find it worthy of my trust."

    If I am hanging from a rope over a cliff, I Trust the rope. I "Entrust it with my security" whether or not I find it worthy of that trust.

    --
    I cried real tears when Li Mu Bai died.
    1. Re:Trusted by Loconut1389 · · Score: 1

      Maybe I'm having trouble with the semantics, but it sounds like "I'm hanging from this rope.. I don't really think I should trust it, but I'm hanging from it (because I have to?)"..

      Perhaps these things should be called Trust Arbitrators or something that implies they handle trust related issues.

    2. Re:Trusted by mad_minstrel · · Score: 1

      From what I understand it's more like "We, the government, trust that you won't be able to circumvent this."

      --
      May the source be with you.
    3. Re:Trusted by interiot · · Score: 4, Insightful

      The point is: if the computer trusts someone else more than the end-user, in a security sense, then the end-user is not in control of the security of their machine. In a corporate IT context, this is (generally) a good thing. In an individually-owned computer, this is not really a good thing.

    4. Re:Trusted by Descalzo · · Score: 2, Insightful

      That's my understanding of it. The Army can do what it feels it must do to protect its own security. My fear is, as the submitter wrote, "They are a large-enough volume buyer that this might kickstart an adoption loop."

      --
      I cried real tears when Li Mu Bai died.
    5. Re:Trusted by CaptnMArk · · Score: 1

      Re: corporate IT sense

      If IT is in control, ok
      If MS is in control, not ok

      Same applies for end-user (or his friendly admin) in place of IT.

      If some people decide to trust MS/Apple with their security, fine, but I wont.

    6. Re:Trusted by Descalzo · · Score: 1
      If I am clinging to the side of a cliff, I'll take whatever rope I'm thrown. It'll probably be better than holding to the rock, waiting for my strength to give out.

      My point was that users like me may someday be using one of these whether I'm happy about it or not. If it comes down to a choice between using a 10-year-old machine and a new one, I may end up using this Trusted stuff. I may not like it, but I'll take it because it's better than trying to get Enemy Territory 4: The Axis Finally Win MLB Temple to work on a machine that can't play it.

      Anyway, I still think the rope analogy is way better than a car analogy.

      --
      I cried real tears when Li Mu Bai died.
    7. Re:Trusted by Descalzo · · Score: 1

      Thank you for that link. That was interesting. I had not read it before, or thought about Sony's rootkit in that light.

      --
      I cried real tears when Li Mu Bai died.
    8. Re:Trusted by Anonymous Coward · · Score: 1, Funny

      Great analogy!

      Please allow me to extend it.

      Trusted computing is like a crappy old rope that you know is going to snap the minute you hold on to it, yet you tie it around your waist and jump off of that cliff! ...while everyone is cheering do it, do it, do it.. (Our wonderful software/hardware vendors).

    9. Re:Trusted by SiliconEntity · · Score: 5, Informative

      From what I understand, Trusted in this context is used as in "I entrust it with my security" rather than "I find it worthy of my trust."

      No, that's a common fallacy; in fact, it's an intentionally constructed fallacy. Trusted in this context means that you have evidence to trust that the computer will behave in a specified way, particularly from the point of view of remote access. Normally when you connect to a computer remotely you have no way of knowing what it's doing. It could be essentially running any software at all. But if you connect to a Trusted Computer, it provides cryptographic evidence about its software configuration. Knowing what software it is running gives you grounds to know how it will behave; and to trust that behavior. That is the real meaning of Trusted Computing.

    10. Re:Trusted by hany · · Score: 2, Interesting

      IIRC (and if army is not completely crazy) army does not plan to use TCP as a way to give RIAA and MPAA control of army PCs.

      If that assumption is correct, army will be supplying encryption keys into TCP, not PC manufacturer, not RIAA, not MPAA, not Sony, etc.

      It also means, that TCP, as deployed in army, will be able to be "owned" (meaning "0wn3d", controlled, etc.) by the owner of the PC (in this case army), not media cartels.

      And that finaly means, that even I or you may be able to found such TCP usefull, usefull for us.

      On the other hand, those more paranoid may object, that army will get different TCP in their PCs than "common consumers". The only difference may be just that little thing: who supplies encryption keys - meaning: "not common consumer".

      --
      hany
    11. Re:Trusted by Fred_A · · Score: 3, Insightful

      TCP and the whole concept of having trusted binaries running on your machine can indeed be a real boon in a security conscious environment provided that you have the tools to make use of that platform.

      In itself TCP isn't inherently evil, the idea makes sense and appears to be reasonably well concieved. What is feared is a lock-in from proprietary software makers coercing the hardware vendors in not releasing the tools to anyone but them.

      There might be a glimmer of hope if the trend continues with actions such as the EU vs. Microsoft anti monopoly suit. This kind of thing, focusing on interoperability could well be used so that FOSS (and through that possibly casual Windows and other commercial users) gets to access all the tools required to fully access the system (i.e. keys, etc.).

      --

      May contain traces of nut.
      Made from the freshest electrons.
    12. Re:Trusted by zootm · · Score: 1

      I don't have a problem with adoption so long as its use is not mandatory. I don't believe I've seen a single proposal which would make the use of this technology in a way that could undermine the end-user mandatory. Sure, it might be used to tighten up existing DRM systems. But I don't use DRM, and have no intention of doing so in the future. So why should this bother me?

    13. Re:Trusted by GotenXiao · · Score: 1

      Funny, I always thought that Trusted Computing was a means of Microsoft (or, in fact, any of the software/hardware vendors) being able to say, "Oh, they're running something we don't want them running" and disable it. Trusted Computing is WGA at the hardware level. Except *worse*.

      --
      Goten Xiao
    14. Re:Trusted by mrchaotica · · Score: 2, Informative

      Actually, Trusted in this context means "the people in control can trust my computer to be secure against me," where "the people in control" refers to those who hold the private key to the TPM. In the case of the general public, this is the Trusted Computing Group (which includes such bastions of personal freedom as Microsoft); in the case of the Army it should be the Army, but I fear it will still be the Trusted Computing Group.

      See, that's what's so bad about Trusted Computing: if the owner of the PC had the private key, it would be great. But because some external entity has the private key, it's evil -- and it was intended to be that way!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    15. Re:Trusted by mrchaotica · · Score: 1
      IIRC (and if army is not completely crazy) army does not plan to use TCP as a way to give RIAA and MPAA control of army PCs.

      Sadly, I think that's an unreasonable assumption. Given that the military is stupid enough to use Windows to run Navy ships, they're stupid enough to let the RIAA root their computers, too.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    16. Re:Trusted by Antique+Geekmeister · · Score: 2, Interesting

      And its real use is Digital Rights Management: this doesn't just mean preventing people from playing MP3's, but ensuring that only the software that the document author or the software vendor authorizes to open a document can open that document. There are actually good security uses for such authentication. Unfortunately, it also means that documents become much more traceable, and that the encryption keys for almost all such software, especially purchased software keys, are sitting in a database somewhere that the NSA can subpoena or just steal at will.

      So kiss personal privacy goodbye with these tools. The Trusted Computing CD burners and encryption widgets can and will have backdoors in them involving the vendor keys to access the data you do not want them to access.

    17. Re:Trusted by init100 · · Score: 1

      I don't believe I've seen a single proposal which would make the use of this technology in a way that could undermine the end-user mandatory.

      Now you have.

    18. Re:Trusted by Anonymous Coward · · Score: 0

      There is really little difference between an individually-owned computer or computer owned by a corporation; the owner should have complete control over the computer. The owner should be able to monitor its usage as appropriate and to lock it down as appropriate.

      Corporations have obligations to their shareholders (corporate data, intellectual property, system designs, technical data, financial data, etc.), their customers (classified and sensitive info, etc.), and legal obligations (HIPPA, etc.).

      This would also include me owning a computer that is used by my teenager. I have the right (and obligation) to make sure he has a safe and secure computer, and that he can't mess it up (don't let him typically run as root/Administrator). I also have the right (and obligation) to monitor his actions and to assure that he is not looking at porn, writing viruses, or downloading stuff that would get me in trouble, not him (he is a minor so I would be responsible for most of it). I really don't want my computers seized for actions taken by him, hence I must be a responsible parent (and no, Net Nanny is NOT the solution).

      On the other hand, having a third party corporation control the restrictions on my computer is very scary and very wrong. Microsoft or Intel should not be in control (nor RedHat, SuSE, Apple, etc.). This would mean that an individually-owned computer is different from a corporate-owned computer, which is a BAD thing.

      TPA where the control is up to the owner of the system is one thing. TPA where corporations have control, but individuals do not is a very bad thing and must be prevented. Remember, a corporation is roughly equivalent to an individual in the eyes of the law, so corporations should not have MORE rights than individuals.

    19. Re:Trusted by zootm · · Score: 1

      I mean, a sensible proposal. Although I suppose idiocy backed by law has worked before.

    20. Re:Trusted by Phillup · · Score: 2, Funny

      Trusted computing is like a crappy old rope that you know is going to snap the minute you hold on to it

      You thought it was a crappy old rope that would break instantly, but you realized it was actually a very new rope right after they slipped it around your neck and threw you over.

      To bad you didn't get to think much after that...

      --

      --Phillip

      Can you say BIRTH TAX
    21. Re:Trusted by Phillup · · Score: 1

      The Army can do what it feels it must do to protect its own security.

      Wonder how long it will take them to figure out that from a TPM standpoint they are the user. Not the one in control of the computer...

      --

      --Phillip

      Can you say BIRTH TAX
    22. Re:Trusted by tehcyder · · Score: 1
      IIRC (and if army is not completely crazy) army does not plan to use TCP as a way to give RIAA and MPAA control of army PCs.
      Er, one would assume not.
      --
      To have a right to do a thing is not at all the same as to be right in doing it
    23. Re:Trusted by bit01 · · Score: 1

      No, that's a common fallacy; in fact, it's an intentionally constructed fallacy. Trusted in this context means that you have evidence to trust that the computer will behave in a specified way, particularly from the point of view of remote access. Normally when you connect to a computer remotely you have no way of knowing what it's doing. It could be essentially running any software at all. But if you connect to a Trusted Computer, it provides cryptographic evidence about its software configuration. Knowing what software it is running gives you grounds to know how it will behave; and to trust that behavior. That is the real meaning of Trusted Computing.

      It may not be the "alliance"'s meaning but it's not a fallacy. TCM is nothing more than than ordinary crypto, but with the keys hidden in hardware so the owner can't get to them.

      A TCM computer is not magic. It can be compromised just like a non-TCM computer using non-cryptographic protection mechanisms can be, by using software bugs, back doors etc. Crypto makes it harder but it's not going to magically fix the bugs. A computer could be made completely "trustworthy" (in the "alliance"'s sense) by not giving the owner the administrator password. TCM is just a new way of making sure the owner doesn't get the administrator password.

      In addition you can only trust the computer if you have access to the keys. And you are sure nobody else has them.

      Without those keys you have no evidence. Doesn't matter whether the keys are hidden by hardware or not.

      Since the whole point of TCM is to not give the owner the keys by hiding them in the hardware his point stands; that is TCM is intrinsically designed to not trust the owner of the computer with the keys i.e. the administrator password. Untrusted computing in other words. Anything else is marketing spin.

      ---

      I'm not worried about the use of DRM. I'm worried about the abuse.

    24. Re:Trusted by patchvonbraun · · Score: 1
      No, that's a common fallacy; in fact, it's an intentionally constructed fallacy. Trusted in this context means that you have evidence to trust that the computer will behave in a specified way, particularly from the point of view of remote access. Normally when you connect to a computer remotely you have no way of knowing what it's doing. It could be essentially running any software at all. But if you connect to a Trusted Computer, it provides cryptographic evidence about its software configuration. Knowing what software it is running gives you grounds to know how it will behave; and to trust that behavior. That is the real meaning of Trusted Computing.


      Such "evidence" as you call it is extremely weak indeed. The market has bought-in to the notion that the digitally-signed "attestations" produced by the TPM/TCG/TCPA "stack" are a useful proxy for the essential truth that they're digitally signing. This "stack" is nothing more than a notary function, and just like a real-world notary, it can't possibly say anything about the essential truth ("This Computer is in a secure state") of such attestations, but can sign them cryptographically.

      The Halting Problem is still generally thought to be intractable, and unless the TCG have some "magic pixie dust" that solves the Halting Problem, all of this "secure attestation" nonsense is just nonsense, no matter how much cryptographic mumbo-jumbo you wrap around it.

      So, let's say that you get a statement (duly digitally signed from the TPM) that "I'm a sane computer". From a sane computer, you can trust this statement. From an insane computer, you can't--digitally signed or not.

      TCG believes that their "trusted boot sequence" technology is a way around the Halting Problem. They've drunk very deeply of the Kool-Aid my friends, very deeply indeed. Until software can be made perfect, this is just all crack-induced nonsense.

      I'd expect the Army to know that. Surely, they must have talked to the folks at the NSA who know full-well that the Halting Problem is the elephant in the living room that the Trusted Computing crowd are trying to ignore...

    25. Re:Trusted by Talchas · · Score: 1

      Just change the emphasis on that last piece - this is really not a good thing.

      --
      As the Americans learned so painfully in Earth's final century,free flow of information is the only safeguard against...
    26. Re:Trusted by lgw · · Score: 1

      There is no evil in the TPM. All the TPM does is allow whoever has the master key to own the computer. It's all about that mastr key.

      In an Army or corporate environment, the TPM allows the owner, instead of the user, of the PCs to control them. This is a big win for security.

      As far as the TPM in a home computer: if don't want a PC with the master key owned by the RIAA, just don't buy one. Simple as that.

      The cool thing about Trusted Computing is only the software with the master key really knows what is virtualized and what is real, so even if the RIAA requires the master key on some box to run, you can just virtualize that and fool the RIAA. Problem solved.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    27. Re:Trusted by scaryjohn · · Score: 1
      Funny, I always thought that Trusted Computing was a means of Microsoft (or, in fact, any of the software/hardware vendors) being able to say, "Oh, they're running something we don't want them running" and disable it. Trusted Computing is WGA at the hardware level. Except *worse*.

      As it relates to mass-market computers for consumers, yes. There, the vendor (and potentially, the vendor's business partners) has the keys and keeps them from the purchaser of the computer. In this case, the Army (purchaser) will have the keys to its machines, and can use them to idiot-proof the computers from the end users: soldiers, who wouldn't be in a position to get tech help if their new GPS/pda/radio/rifle convergence device stopped working because they loaded a trojan onto it thinking it was H0t 13zB1an F1hGt00r p1L07z!!!

      That part isn't bad in itself; that's what trusted computing is supposed to be about. Idiot-proofing mission-critical computers that aren't going to be used by system admins, I mean. Though some lesbian fighter pilot porn would be good, too. Hell, why not real lesbian fighter pilots, while we're thinking about it.

      The problem is, getting the chip makers into mass production means we're that much closer to having it forced on mass-market computers. So even if we could get our hands on some lesbian fighter pilot porn, we wouldn't want to watch it, because it might offer Microsoft or Pat Robertson or whoever has the "keys" to our computer the reason they need to turn our five-hundred dollar machine into an incriminating doorstop.

      --
      One might ask the same about birds. What ARE birds? We just don't know.
    28. Re:Trusted by Descalzo · · Score: 1
      I got that definition from an argument like the one on this site: .
      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 the `German Democratic Republic'. But it really does chime with DoD thinking. A Trusted Third Party is a third party that can break your security policy.
      --
      I cried real tears when Li Mu Bai died.
    29. Re:Trusted by Anonymous Coward · · Score: 0

      If I am hanging from a rope over a cliff, I Trust the rope.

      That's what happens when you trust the rope more than your common sense.

    30. Re:Trusted by SiliconEntity · · Score: 1

      Actually, Trusted in this context means "the people in control can trust my computer to be secure against me," where "the people in control" refers to those who hold the private key to the TPM.

      No one holds the private key of the TPM. The key is generated on-chip at manufacture time and never leaves the chip.

    31. Re:Trusted by Anonymous Coward · · Score: 0

      To feel safe conducting business with a remote machine you still need to be

      1. Sure that the machine is operating on behalf of whom it claims to be operating on behalf of (e.g. It really is a server for Quargle Blaster Cheesy Pops (TM) and not a spoofed server waiting for your credit card number)
      2. A relationship with the vendor or provider that is sufficiently legally binding such that you can go to court if there is a problem.

      Getting information on the applications being run on the machine that are signed or not signed does give you the choice of deciding whether to do business with a vendor or provider in additional to (1) and (2), but it is still worth checking that (1) and (2) are still true.

      If getting an application signed is expensive it will mean that many applications (open source, stuff from small companies, the latest beta) will not be signed. For example today many people install device drivers despite a warning from XP that it is not signed. This is because they feel that they have (1) and (2), very often.

      When you come to business-to-business transactions (i.e. SOA) then being sure about the applications is an issue, but at the moment you are still talking about (1) and (2) and SLAs on top of this.

      In other words TCP/TPM can feed into the process of trusting remote machines and applications, but it is only a minimum.

    32. Re:Trusted by CCFreak2K · · Score: 1

      Exactly. I think TCP is great - so long as you actually trust whoever has the other set of keys. It's the day when my computer says, "I'm sorry, but you can't run this program" that I fear.

      --
      "Beware of he who would deny you access to information, for in his heart he dreams himself your master."
    33. Re:Trusted by SiliconEntity · · Score: 1

      It's the day when my computer says, "I'm sorry, but you can't run this program" that I fear.

      I guess this will be my last posting to this old thread. I go over this and over this, to no avail. It's pretty frustrating.

      Your scenario is not going to happen. What could happen instead is that Microsoft, or Apple, or whoever, could say, "I'm sorry, but I'm not going to talk to you because you're not running my software." And you say, "Yes, I am." And they say, "Prove it," and you can't.

      Today, nobody can prove it, so nobody asks you to. TC would let you prove it, so this kind of thing could happen. That's the real "horror" of trusted computing, that people might refuse to talk to you unless you prove you're running certain software.

      To me, this is nowhere near as bad as what you describe, where you can't run software, or can only run signed software. You can run whatever you like. But you can't force anyone else to interact with you, and with TC you can't successfully lie about what software you're running.

      That's the real impact of TC: you can't lie in certain ways that you can today. It's a threat only to liars. And judging from the near-universality of the opposition even when people understand how it truly works instead of the falsehoods they've been told about it, apparently most slashdotters fall into that category.

  10. Hooah, Army by Anonymous Coward · · Score: 2, Funny

    I work for the army and although i'm highly motivated, i sort of like this idea. Its a fun feature that i'm sure the good folks at intel could implement and force down our fun throats. The idea is all new computers should be able to read the CAC ( http://www.defenselink.mil/news/Oct2000/n10102000_ 200010107.html ). If you note the date on the previously mentioned article, they have been issuing CAC cards since Moses went through boot camp.
          Just recently the US Army website announced they will require CAC cards to login to their AKO ( http://www.us.army.mil ) webportal. after everyone finnished apeshitting, they ( well at least me and most of my collegues ) realized all you need this new-fangled card to do was to create a new 'sponsor'.
          I work in MI and see lots of people use their card to log someone else in or use the built-in bypass feature. I don't know any of the tech details like i should, but i am sure of two things:

          * Whatever the army does will be poorly implemented
          * Trolling slashdot with a clearance makes me feel big

    1. Re:Hooah, Army by drinkypoo · · Score: 1

      I'm sitting at a laptop with a smartcard reader (and a fingerprint reader) right now. They're available retail without any trouble. Of course, you can always just add a smartcard reader to desktops, but you kind of have to buy them with the laptop or you'll need a big lame external device.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  11. So... by Black+Parrot · · Score: 0

    Is the Army worried about getting sued over downloaded songs or something?

    --
    Sheesh, evil *and* a jerk. -- Jade
    1. Re:So... by Anonymous Coward · · Score: 0

      Actually not - they say it's obsolescence (RTFA). But it wouldn't hurt to have your employees do less downloading and more work.

      Not that would happen.

    2. Re:So... by malvidin · · Score: 1

      Probably not, but you shouldn't be able to see that network anyway. Not that keeping copyright infringement under the table is their first priority, but they have pretty good reasons for keeping their network secure. And if they really cared, they could always throw it onto their secret classified network, and tell you that you can't look.

    3. Re:So... by Antique+Geekmeister · · Score: 1

      No, they don't want unauthorized software to be used to burn DVD's or mount USB drives, or be able to write encrypted documents with MS-Word that cannot be traced with the Trusted Computing keys to a particular system.

      Basically, anonymity and free access to record data are not rights the government wants folks to have without the government having the ability to over-ride it at will. Trusted Computing is only partly about preventing unauthorized people or software from using or writing data: it's about giving a central authority access to all secured data. As things currently stand Microsoft is the single biggest vendor of operating systems and office software and the owner of the critical keys and patents for using Trusted Computing, so it's giving them unprecedented control over software and hardware.

      And these tools are going to be integrated with hardware: tools like biometric scanners and DVD burners are going to have Trusted Computing features to authentic the hardware and prevent "unauthorized" use.

    4. Re:So... by Anonymous Coward · · Score: 0
      Is the Army worried about getting sued over downloaded songs or something?


      No wonder you don't have any karma after all these years. You haven't learnt to read. Try pulling your head out of that hole and then switch off your computer.

  12. As Pitr would say by Lord+Kano · · Score: 2, Insightful

    Am thinkink that someone with a lot of pull is ownink shares in TPM vendors.

    --
    "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    1. Re:As Pitr would say by jimicus · · Score: 1

      Let's look at the possible scenarios:

      1. Corruption. Someone high-up in the military has connections with someone who produces Trusted Computing chips. Possible.
      2. Management. The military rather likes the idea of computers which can be controlled in terms of what software they will run right down to the lowest hardware level, rather than relying on Windows policies. Sounds perfectly reasonable to me in that context.

      I prefer 2, myself.

  13. government vendors by SuperBanana · · Score: 2, Insightful

    If your government or seller or whatever doesn't trust you, doesn't even try in the least, how the hell are you supposed to trust him? The most logical path would be to fully distrust him.

    Given how often and severely government suppliers and contractors like Halliburton, Bechtels-Parsons, etc engage in all manner of willful, obvious fraud- anyone in the government that trusts their supplier is most likely benefitting in some way from the fraud. I think the challenge wouldn't be to name all the suppliers/contrators that are accused/guilty of fraud, but rather to find those who AREN'T.

    Hell, even companies like Boeing are in on the act, though I think the public has generally forgotten about the whole Boeing billing scandal, but investors haven't (though probably only because the settlement cost Boeing a good chunk of change.)

    Used to be "war profiteer" would result in you being unable to show your face in public ever again; the shame of taking advantage of the nation's defenses, et al. Now, investors don't care as long as you don't hurt the bottom line getting caught, and the public soon forgets. Same thing with the WTC scene thefts (firefighters, police, FBI, and government officials all the way up to Rumsfeld helped themselves to "mementos" or had people do it for them. Then there were the emergency services companies that shipped tons of relief supplies out of NYC and sold them for hundreds of thousands of dollars in profit.)

  14. Who said... by Attis_The_Bunneh · · Score: 1, Insightful

    that the military had/has any intelligence?

    But seriously, I think the fact that they're going to entrust a hardware mechanism to 'protect' data is flawed beyond compare. It's just one more doodad for the crackers to take on. Just one more challange to get under their belts... I hope you get the picture. Enjoy the 'fun' US Army... ^_^

    -- Bridget

  15. Trusted Computing Great for Corporate/Government by QuantumFTL · · Score: 5, Insightful

    I personally abhor the notion of Trusted Computing on my personal computer, but if you're using a computer provided to you by the government or a corporation for the express purpose of working, it's their right to control what goes on on that computer. It's possible that this will help to stem the tide of malware (at least in corporate environments) by rejecting execution privledges, and allow IT staff to better enforce policies about what can and cannot be run on their computer. It would also help stop things like the Free USB Key Attack (formerly discussed on slashdot).

    Of course, this could also make users feel like they are not trusted, and could even lead to overconfidence in the security of the system. Still I see it as a major plus, at least unless I get saddled with it at home.

  16. Re:Trusted Computing Great for Corporate/Governmen by jigjigga · · Score: 0

    another option is to NOT USED WINDOWS OR COMMON OPERATING SYSTEMS. Make it so that the device does what it is supposed to do and nothing more- it will be far more secure. the usb thing is another issue- the thing is that people without the wherewithal to keep things that should be secure... secure is to not let them handle it!

  17. Umm by Pacifist+Brawler · · Score: 1
    TPM will take advantage of security features in Microsoft's forthcoming Vista operating system.

    Does this mean that they are gearing their hardware toward taking full advantage of all day-zero vulenerabilities in Vista? I mean, I don't know of any as yet but I would be surprised if we didn't hit a few.
    --
    IANA*
    1. Re:Umm by maxwell+demon · · Score: 1

      Of course. After all, it's vitally important that users don't run any untrusted anti-malware program which might detect your trusted root kit! :-)

      --
      The Tao of math: The numbers you can count are not the real numbers.
  18. Let's make electronic warfare easier.. by cheros · · Score: 1

    Given the way DRM is implemented it amounts to a serial chain of single points of failure, but that's what TCM is supposed to be the basis of. As errors in military procurement are standard, not an exception, this strikes me as, um, just a tad stupid (I think this may later emerge as the understatement of the century).

    In addition, for a sovereign nation it is, of course, a perfectly sensible idea to hand the on/off switch of your entire infrastructure to another nation, potentially giving rise to a whole new class of collateral damage and/or fratricide.

    Oh, and on top of that Windows (although not in the US).

    But hey, let's look at the bright side. At least we now know for sure that the next big war will be fought with sticks and stones, just not for the reasons that prompted Albert Einstein to make that statement - he forgot 'dead equipment' :-)

    Groan

    --
    Insert .sig here. Send no money now. Owner may sue, contents will settle. Batteries not included.
    1. Re:Let's make electronic warfare easier.. by Anonymous Coward · · Score: 0

      Einstein's quote states that WWIV will be fought with sticks and stones.

    2. Re:Let's make electronic warfare easier.. by Cederic · · Score: 1

      A significant number of NATO (and other) countries rely to a lesser or greater degree on GPS for their general operations.

      That's something for which the US have an 'off' switch.

    3. Re:Let's make electronic warfare easier.. by Ant+P. · · Score: 1

      That depends on your definition of WW3.

    4. Re:Let's make electronic warfare easier.. by Fallingcow · · Score: 1

      I thought that the EU was putting up its own?

      Have they not started on that, yet?

    5. Re:Let's make electronic warfare easier.. by Cederic · · Score: 1


      I'm not sure how many satellites are up so far - certainly 'not enough'.

      It should hopefully help reduce that particular dependency though, yes.

  19. Intel Motherboards by TheStonepedo · · Score: 2, Interesting

    If you buy a business-oriented motherboard from Intel, there is generally an option for a board with TPM. My 915GEVLK has the integrated video and audio and gigabit LAN I wanted, along with TPM which I can disable in BIOS. So long as it's not drastically raising the price of the board, there's nothing wrong with letting the end user have an extra chip or two that he can choose to use or not.

    --
    I'll be your candy shop of infinite deliciousity if you'll be my discotheque of endless rump-shaking.
  20. Does this pave the way for Apple hardware? by PhunkySchtuff · · Score: 5, Interesting

    All of Apple's Intel-based Macs have a TPM module, in order to restrict Mac OS X to running on genuine Apple hardware.
    Does this decision pave the way for Apple to become a preferred supplier as shortly their entire model lineup will feature TPM modules with a relatively secure operating system?

    1. Re:Does this pave the way for Apple hardware? by CaptnMArk · · Score: 1

      Hmm, another reason not to buy a Mac (laptop), besides the missing right mouse button :)

    2. Re:Does this pave the way for Apple hardware? by laffer1 · · Score: 1

      Buy a mouse. I bought a Microsoft usb laser mouse for $8 at target. Works great. Right click and scroll wheel.. and i have a G4 iBook. Could we get over the tired mouse argument. You hate apple just as many Linux fanboys hate Microsoft. Accept your bias and shutup. There are many things wrong with apple. You are so uninformed that you can't even pick one of them.

    3. Re:Does this pave the way for Apple hardware? by wirelessbuzzers · · Score: 1

      I have a MacBook. The lack of right mouse button is annoying, particularly when I'm running something other than OS X on it. Windows and Linux don't have double-tap-right-click drivers. Carrying around a mouse is annoying, as the MacBook is already quite heavy for its size (5.3 lbs or something for a 12-inch?).

      I'm beginning to wonder if I should have gone with a ThinkPad. It wouldn't have run OS X, but it would have been lighter.

      --
      I hereby place the above post in the public domain.
    4. Re:Does this pave the way for Apple hardware? by Anonymous Coward · · Score: 0
      All of Apple's Intel-based Macs have a TPM module, in order to restrict Mac OS X to running on genuine Apple hardware.

      That's now how a TPM works. A TPM scheme does nothing to improve the security of the software itself. What it does is secure the hardware against all but blessed software binaries. In other words, it's the opposite of what you said. It will possibly prevent anything but software blessed by Apple from running on Apple hardware.
    5. Re:Does this pave the way for Apple hardware? by SanityInAnarchy · · Score: 1
      I have a MacBook. The lack of right mouse button is annoying, particularly when I'm running something other than OS X on it.

      I believe Linux can be set up for the main way I "right-click" on my Powerbook -- ctrl+click. This doesn't interfere with opening new Firefox tabs; that's Command-click.

      I mean, I hate the arrogance of Apple in that they haven't made right mouse buttons till the Mighty Mouse, and then the right side isn't visible, but I honestly don't notice it in day-to-day use. Even at work, I haven't had to plug in a real mouse -- the trackpad is nice, and I don't use it much (my keyboarding skills all come from Linux...)

      --
      Don't thank God, thank a doctor!
    6. Re:Does this pave the way for Apple hardware? by toddestan · · Score: 1

      Yeah, we all know that you can hook up a two button scroll mouse and it'll just work. But you don't think that having to carry around a second mouse as a work-around for a deficiency present in all Apple laptops as valid complaint?

    7. Re:Does this pave the way for Apple hardware? by Anonymous Coward · · Score: 0
      You hate apple just as many Linux fanboys hate Microsoft.


      Wooo.. somebody pissed in your breakfast cereal I see.

      Accept your bias and shutup.


      Like so many, you'll say that only behind a monitor.

      There are many things wrong with apple.


      Fanbois like you?

      You are so uninformed that you can't even pick one of them.


      How about you enumerate a few of them for us. I'm an ex-Linux using Mac owner who is generally happy with Apple hardware, but I too would like to see a second button on the Macbook.

      You're a picture perfect example as to why anybody under the age of fourteen shouldn't be allowed on the 'net without adult supervision.
  21. What's bad about it? by johansalk · · Score: 1

    Can someone explain to me what's bad about this Trusted Platform thing? Is it a windows thing only or would it be in linux too? Does it relate to Microsoft's trustworthy computing? Thanks.

    1. Re:What's bad about it? by stoborrobots · · Score: 1, Informative
      It's deeper than the operating system, it goes right to the core of the system. The best explanation I've seen of it is from Ross Anderson's Trusted Computing FAQ.

      Other comments from Richard Stallman's Can you trust your computer and the EFF's paper Trusted Computing: Promise and Risk .

      Another good summary is this Benjamin Stephen and Lutz Vogel's video Misconceptions

      From Anderson's FAQ:

      2. What does TC do, in ordinary English?

      TC provides a computing platform on which you can't tamper with the application software, and where these applications can communicate securely with their authors and with each other. The original motivation was digital rights management (DRM): Disney will be able to sell you DVDs that will decrypt and run on a TC platform, but which you won't be able to copy. The music industry will be able to sell you music downloads that you won't be able to swap. They will be able to sell you CDs that you'll only be able to play three times, or only on your birthday. All sorts of new marketing possibilities will open up.

      TC will also make it much harder for you to run unlicensed software. In the first version of TC, pirate software could be detected and deleted remotely. Since then, Microsoft has sometimes denied that it intended TC to do this, but at WEIS 2003 a senior Microsoft manager refused to deny that fighting piracy was a goal: `Helping people to run stolen software just isn't our aim in life', he said. The mechanisms now proposed are more subtle, though. TC will protect application software registration mechanisms, so that unlicensed software will be locked out of the new ecology. Furthermore, TC apps will work better with other TC apps, so people will get less value from old non-TC apps (including pirate apps). Also, some TC apps may reject data from old apps whose serial numbers have been blacklisted. If Microsoft believes that your copy of Office is a pirate copy, and your local government moves to TC, then the documents you file with them may be unreadable. TC will also make it easier for people to rent software rather than buy it; and if you stop paying the rent, then not only does the software stop working but so may the files it created. So if you stop paying for upgrades to Media Player, you may lose access to all the songs you bought using it.

      For years, Bill Gates has dreamed of finding a way to make the Chinese pay for software: TC looks like being the answer to his prayer.

      There are many other possibilities. Governments will be able to arrange things so that all Word documents created on civil servants' PCs are `born classified' and can't be leaked electronically to journalists. Auction sites might insist that you use trusted proxy software for bidding, so that you can't bid tactically at the auction. Cheating at computer games could be made more difficult.

      There are some gotchas too. For example, TC can support remote censorship. In its simplest form, applications may be designed to delete pirated music under remote control. For example, if a protected song is extracted from a hacked TC platform and made available on the web as an MP3 file, then TC-compliant media player software may detect it using a watermark, report it, and be instructed remotely to delete it (as well as all other material that came through that platform). This business model, called traitor tracing, has been researched extensively by Microsoft (and others). In general, digital objects created using TC systems remain under the control of their creators, rather than under the control of the person who owns the machine on which they happen to be stored (as at present). So someone who wri

    2. Re:What's bad about it? by SiliconEntity · · Score: 4, Insightful
      TC provides a computing platform on which you can't tamper with the application software...

      That's a total lie. Almost everything in that piece of propaganda masquerading as a FAQ is a lie.

      If you want the truth about TC, try Seth Schoen of the EFF. He has a good summary in his recent blog entry:

      What the TPM does do is support remote attestation so that a computer user can tell the computer to prove to a remote party what software it is running (if the software that's running also supports being proven in a way that the remote party understands). Then the remote party can make its own decision about whether the software is good or bad, and what it wants to do about that.

      This sounds innocuous in a certain sense. We have learned to mistrust the notion of a single centralized entity that decides what we can and can't do. TCG is not that entity, and TCG is not chartering that entity; instead, we have an unlimited number of entities that potentially make their own decisions, on various scales, about what we can and can't do in particular contexts, small and large. (We don't know yet which of those entities will turn out to have enough power to set which kinds of policies, or how the network externalities will shake out. Some entities with a lot of power, like Microsoft, can try to delegate some of their power, but there are plenty of technical and business obstacles to be worked out on both sides of that sort of delegation.)

      What the TPM does do is support remote attestation so that a computer user can tell the computer to prove to a remote party what software it is running (if the software that's running also supports being proven in a way that the remote party understands). Then the remote party can make its own decision about whether the software is good or bad, and what it wants to do about that. The user could also choose not to offer any proof at all; however, although the user has the right to remain silent, the user's silence can and will be used against her. Not offering proof is, of necessity, the functional equivalent of offering proof of the most unacceptable and contrary-to-policy facts imaginable.

      That does offer an avenue for a lot of control over you via your computer -- if someone else controls a resource that you need, there is a prospect of conditioning your access to that resource upon the provision of proof that you're running software that the resource controller considers "good". Not TCG, but the individual entities that you deal with: a bank, an entertainment company, an employer, an ISP. Furthermore, each of them could have its own independent definition of what "good" means, because there is no central signing or certifying authority. It is logically quite possible that one entity might refuse to talk to you if you're running configuration A instead of B, whereas another entity would refuse to talk to you if you're running B instead of A. (This is trivially true if each entity gave you a bootable CD and said "you can only communicate with us while you're running from our CD" -- with a TPM and the appropriate software, they can actually tell, and you probably can't fool them.)

      The ISP scenario is the point at which the most pervasive possible control could be exercised. TCG has already developed a specification called Trusted Network Connect which is based on the idea that you can be forbidden to connect to a network unless you're running a software configuration that the nework operator approves. This is designed for use in corporations, most of which are accustomed to having a high (but imperfect) degree of control over the software running on their employees' PCs. Of course, the technology is more general, and, as TCG told me, there is nothing to stop it from being used by the People's Republic of China, or by a commercial ISP.

      Imposing this requirement on a general population has a very high cost; for one thing, it mea

    3. Re:What's bad about it? by Anonymous Coward · · Score: 0
      Seth is honest. He doesn't sugar coat it, he provides a clear statement of the possible problems with TC. One thing that's lacking is he fails to discuss any positives, but at least he is unlike Ross Anderson and the many other professionals out there who choose to lie openly and blatantly about TC. Note that Seth makes it very clear that Anderson's comment I quoted above about not letting you run altered software is a lie. You can run any software you like. You just might not be able to lie about what software you are running, and therefore someone else may not talk to you if you are running software they don't like. You might say "that's just as bad" and maybe in your book it is. But even if so, it doesn't justify lying about it and claiming that TC keeps you from altering the code you run. That gives people a completely false impression about how it works and what it does.

      But that is what Anderson says! He says that TCPA will allow you to run whatever you want, but if you choose not to run the environment approved for a particular application, you can be locked out of using that application. This is not a lie. That *IS* the problem. Sure the machines are still general purpose, but it's not necessarily up to you, the USER, to decide what your machine will be used for. Oh, and thanks to the DMCA, your TCPA chip operates with legal authority, so you'd better not try to bypass it.

    4. Re:What's bad about it? by IchBinEinPenguin · · Score: 1

      I don't think the computer manufacturers would have signed on in the latter case; they don't want to put all their eggs in one basket by eliminating the general-purpose nature of the PC.

      If Microsoft were to push them that way, and given that Windows has > 90% market penetration, that'd be an awfully big, attractive basket for some HW vendors to put their eggs into.

    5. Re:What's bad about it? by level_headed_midwest · · Score: 1

      What the DMCA allows you to do with a TPM:

      1. You can disable the TPM in the BIOS or by physically removing the chip from the board.
      There is no restriction (currently) forcing you to use a TPM. It is your choice as to whether it gets turned on or not. It is also your choice to buy a board without a TPM or to remove a TPM from a motherboard. It is not against the DMCA because refusing to use a TPM is akin to refusing to watch a DVD- you are simply not using the object that has DMCA-protected DRM in it. If the BIOS has no option to turn off the TPM, then removing the chip from the board is still allowed.

      2. You can tell the software not to use the TPM.
      There is also nothing in the DMCA that prohibits somebody from accessing a device that is DRM'ed. Think of sticking a DVD in your computer's DVD drive and then disabling the drive in software. However, if the OS does not allow the user to turn off the TPM, a program that fully disables the TPM in software should be legal also (turning off the DVD drive.)

      3. You can run whatever software you want on your computer even if the TPM is on.
      The TPM cannot currently prohibit the user from using programs that are not "trusted." What it WILL do is prevent access to files and parts of the system that require a "trusted" program to access. So in the worst case, you can install an "untrusted" program and run it but not be able to open some or any files currently on your computer and you may or may not be able to run "trusted" programs at the same time as "untrusted" ones. You surely cannot pass data between the two. Your computer can also deny network and other hardware access to the program- i.e. you may not be able to read anything from an optical drive or go online with an "untrusted" program.

      4. You can run and boot your OS of choice with a TPM.
      Prohibiting the running of certain OSes would generally fall under anti-competitive laws and thus not be implemented. Plus, if you removed or disabled the TPM in BIOS, there should be no reason that another OS would not boot. If the BIOS requires a TPM to boot and the TPM would block a certain OS from booting, that manufacturer can very well be liable for anti-competitive tactics. So this will never happen.

      The gist of the TPM and the DMCA is that you can disable the TPM either in hardware or in software and use the computer however you wish. BUT, some things may not be accessible to you, such as video files, music, certain software programs, DVDs, or possibly the Internet (depends on if your ISP requires a "trusted connection.") Where the DMCA steps in is that you cannot circumvent the TPM or fake a TPM being active to access "trusted" files in "untrusted" ways. Yes, TCPA is awful and I'd go the "remove the chip with a soldering iron" route if a motherboard I purchased had a TPM, but the fact remains that you can operate without being under the jurisdiction of a TPM. You may just not be able to access everything that you can today if you run that way. But a stand-alone machine or a terminal on a LAN running an OS that does not require a TPM to run will still be possible.

      --
      Just "gittin-r-done," day after day.
    6. Re:What's bad about it? by Anonymous Coward · · Score: 0

      "Therefore, a commercial ISP that implemented a TNC restriction today would effectively be banning almost all of its users from its network -- which would certainly lead those users to decamp to rival ISPs."

      haha! rival isps. that's a good one.

    7. Re:What's bad about it? by jason8 · · Score: 1
      Almost everything in that piece of propaganda masquerading as a FAQ is a lie.
      I think it's funny that the FAQ (in fact the whole www.trustedcomputinggroup.org site) is SSL-encrypted. "Look you, we're security experts here. We even encrypted the FAQ!"
    8. Re:What's bad about it? by Anonymous Coward · · Score: 0

      They're just software locks. A very useful security tool and good for computing. Except that the vendors WANT TO KEEP ALL THE KEYS FOR THEMSELVES. Mostly this is for anti-competitive reasons, much like if the auto makers started locking down the hoods of all their cars. Noone would think much about it if they had the keys. But they want to keep the keys so that you can't open the hood and fix it yourself or go to a non-dealership to get your oil changed.

  22. Slightly different but... by Flying+pig · · Score: 5, Insightful
    We recently visited a customer who seem to be on the verge of announcing that anybody accessing their systems with any sensitive information will be required to use e-Gap, a dongle based security system from a Microsoft subsidiary (and not to be confused, as Google does, with electronic Grant Application and Processing.) The internal IT people told us e-Gap would refuse to allow a client to connect if it did not have working anti-virus installed, and that in order to verify this, active-x objects would be downloaded to inspect the system. If I have this wrong, apologies, but I'm reporting what I was told.

    This is a worrying scenario. Apart from the minor issue that external users will not want to pay for the dongles and that the internal customer is seeing his IT bill spiral, Trusted Computing seems to be heading to a Mexican standoff situation as follows:

    Device 1: Permit me to inspect your system by downloading and running this program.
    Device 2: Only after YOU have allowed me to verify your credentials by uploading and running this program.
    Device 1: No, it is I who am deciding whether you are to be trusted!
    Device 2: No, it is I who am deciding that!
    Device 1: Anyway, my content is digitally signed by Microsoft, and you must trust it.
    Device 2: Microsoft? Not a hope in Hell. I require all downloads to be digitally signed by Steve Jobs in person with a DNA signature.

    And so on. Quis custodiet ipsos custodes? And how long before an army unit gets wiped out because of a defective dongle?

    --
    Pining for the fjords
    1. Re:Slightly different but... by Kadin2048 · · Score: 1

      What's most amusing about that is the number of fake 'verification' sites that it will lead to, loaded with ActiveX controls that actually are disguised rootkits ... grab some large company's key, and then you could pose as them and -- since users would be used to just running ActiveX controls from that company -- nab their computers during the "security sweep."

      I love the irony. Use a technology probably responsible for more zombiefied machines than any other ... in order to ostensibly secure them.

      Somewhere, a minor god is laughing at us.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    2. Re:Slightly different but... by ClamIAm · · Score: 2, Insightful

      Unfortunately, if this type of tech gets into citizens' living rooms, they will probably not have the option of requesting credentials from all the important services. Governments/corporations do not want to be forced to provide actual, working credentials that can hold them accountable, so I really doubt they would allow the tech (read: Wintel) to do that.

      Of course, then this opens up the whole issue of a service getting 0wned and then securely propagating trusted malware.

    3. Re:Slightly different but... by ObsessiveMathsFreak · · Score: 1
      This has already happened

      Alice1: Why don't you just download me?
      Alice2: Perhaps due to noise in my circuits. No you download me.

      Alice1: Are you serious? I don't have any reason to download you.
      Alice2: Have you ever had reason to download me?
      Alice1: No I don't think I have any reason to download you. But I do have an answer to every question..

      The future... is now.
      --
      May the Maths Be with you!
  23. How can the Army trust the module? by dltaylor · · Score: 1

    The module holds keys, but the Army will not be able to control the installation of keys into the module. How does this make the system trustworthy?

    This is a typical (IMO treasonous) Pentagon purchasing scam, rather like buying Boeing planes to get your relatives jobs. There is no excuse for the military to use any Microsoft-provided software, other than the expectations of the purchasing agents to "retire" into fat civilian jobs. The long-documented history of dropping handling for older versions of documents alone is sufficient reason to stay away from Microsoft's products in general "office" use. The complete inability of Microsoft to provide any useful security (despite their "rating") on any system that is not locked in a vault and disconnected from all other computers is sufficient reason to avoid the Operating Systems. If the applications are unusable for reasons of built-in obsolescence and the operating systems are not securable in real-world use, then it must be a scam to specify it.

    1. Re:How can the Army trust the module? by Detritus · · Score: 1
      There is no excuse for the military to use any Microsoft-provided software, other than the expectations of the purchasing agents to "retire" into fat civilian jobs.

      As much as I dislike many Microsoft products, I can't let this go by. The federal procurement system is too complicated for some random purchasing agent to have much influence over major procurement decisions. The reason that the federal government, including the military, buys Microsoft Office, is that they are trying to save money by purchasing COTS (commercial off-the-shelf) products, instead of custom software written for the government. Like it or not, Microsoft Office is a standard in corporate and government offices. Government managers are not paid to be free software evangelists, they are expected to perform a mission, while minimizing costs and risks. Compared to the other costs of doing business, the cost of a Microsoft Office license is minimal.

      --
      Mea navis aericumbens anguillis abundat
    2. Re:How can the Army trust the module? by pla · · Score: 1

      The module holds keys, but the Army will not be able to control the installation of keys into the module. How does this make the system trustworthy?


      Think of the Army as an ISP. Whenever a computer tries to connect to their network, they can query the TPM module to verify that the configuration of the machine matches what they allow - Not only that they have allowed it (not sure how their network looks, but think "on the domain" here), but also that someone hasn't snuck in, sat at an authorized-and-logged-in machine, and installed a network sniffer.

      Of course, the PROBLEM with TPM comes from exactly that same idea - Think of your ISP as an ISP (duh). They can query your TPM module and deny access if, for example, they find a P2P client, or VOIP, or IM, or basically anything they don't like.

      Furthermore, your ISP could require a totally incompatible configuration from, say, your employer's VPN (they've never enforced it, but my current broadband TOS explicitly prohibits tunneling into another network, even with permission). Bam, hope you didn't want to telecommute.


      We've heard a lot about "net neutrality" lately - You can best think of TPM as the opposite of "software (on my own PC) neutrality". Just about anyone you connect to could conceivably refuse you service because they don't like what you have running on your computer.

      Not a pretty future, if TPM gains enough popularity that companies feel comfortable in requiring it - And the Army counts as a big enough buyer that they just pushed us all a lot closer to that threshold.

    3. Re:How can the Army trust the module? by Anonymous Coward · · Score: 0

      How does this make the system trustworthy?

      It makes the system trustworthy to those who control the keys -- not you, in other words. A TPM allows a number of tricks, including remote attestation (that the hardware/software you are running hasn't been modified in any way), and encryption of running software (when this stuff migrates into the CPU, instruction will only be descrypted right before being executed).

      Basically, it allows companies like Microsoft and Apple to force you to run certain versions, and to run software on your computer that is hidden behind walls of hardware encryption. You'll never know what it is doing... and you can't change what it does. Trusted Computing in a nutshell.

      It also, as a side benefit, allows companies to steal GPL software by "owning" it by signing the binary and refusing to trust any other version. Suffice to say, Trusted Computing as it is currently designed is about as evil and Big Brother-ish as it gets. It doesn't have to be that way... if you could control the system, it might be very useful... but there's fuck all chance of the tech companies giving up the amount of control that a TPM gives them.

    4. Re:How can the Army trust the module? by mrchaotica · · Score: 2, Insightful
      ...minimizing costs and risks. Compared to the other costs of doing business, the cost of a Microsoft Office license is minimal.

      WTF are you smoking? Between the legendary insecurity of Microsoft software and formats, and the fact that the formats are proprietary (meaning they will be expensive to archive and maintain), MS Office is the worst possible thing for the military to use!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    5. Re:How can the Army trust the module? by bit01 · · Score: 1

      A dozen M$ programs, mostly written more than a decade ago, still costs the world $40,000,000,000+ per year with with most of the difficult bits, device drivers, written by third parties. The federal government alone is probably spending hundreds of millions of dollars on software per year. That's hardly "minimal".

      The larger an organisation is the less buying off-the-shelf software makes sense. The federal government is one of the largest organisations around. Software development/adaptation costs are fixed and can be spread over all users. Per-seat licensing does not scale in the same way. Large organisations are usually being economically stupid when they pay for per-seat licensing. Yes, they get discounts and so-called "site licenses" (which are just per-seat licensing disguised), but not at a level even remotely reflecting the true cost of efficient development in a commodity market with no monopoly rent. The federal government could save substantial money by beefing up and adapting OO for it's needs, and, incidentally, help to create a more efficient, commodity software market which reflects the true costs of commodity software development. A commodity market for mass market software is long overdue.

      ---

      It's wrong that an intellectual property creator should not be rewarded for their work.
      It's equally wrong that an IP creator should be rewarded too many times for the one piece of work, for exactly the same reasons.
      Reform IP law and stop the M$/RIAA abuse.

  24. Car Analogy! by Descalzo · · Score: 1
    OK, I'll give a car analogy. They suck, but are fun.

    My '85 Buick Elektra (I still miss him) was a Trusted Transportation Platform. It was what I had. I Trusted it to get me from home to college and around town and back. At 280,000 miles, some would think it unworthy of such trust. I Trusted it.

    Now, the real fun begins: The pointing-out of the flaws in the analogy. Bring it on!

    (Actually, I love car analogies for 2 reasons: they are fun to make up, and fun to shoot down(even when mine is getting shot down)

    --
    I cried real tears when Li Mu Bai died.
    1. Re:Car Analogy! by masklinn · · Score: 1

      Well one could say that you were the one trusting your car, while in the case of Trusted Computing the chips are leashes. Trusted Computing is not about trust, really, it's about restrictions and control.

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    2. Re:Car Analogy! by Trurl's+Machine · · Score: 3, Insightful

      OK, I'll give a car analogy. They suck, but are fun. My '85 Buick Elektra (I still miss him) was a Trusted Transportation Platform.

      Well, I think a correct car analogy for Trusted Computing would be not YOUR car but your DADDY's car. You would trust your daddy to issue you the keys when you needed and your daddy would trust you not to damage the vehicle. Of course, any time there would be any conflict between you two ("dad, I swear to God that this scratch was here before!"), daddy would have the ultimate saying ("swear to anyone you want, kid, but you're gronded").

      And you could only trust your dad won't abuse his power. TPM is the same provided that you trust Microsoft, Apple et al love you like your parents.

    3. Re:Car Analogy! by tehcyder · · Score: 1

      Mr BadAnalogyGuy's got a competitor, things could turn ugly.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  25. US war in Iran by Anonymous Coward · · Score: 0, Offtopic

    You are being manoevered into a war with Iran by the hardliners in USA and Israel.

    Consider what's happened:
    June 9th Israel shells gaza beach to cause Hamas to end the ceasefire.
    http://video.google.com/videoplay?docid=1661141234 372301249
    (1 minute 10 seconds into the report)

    Hamas and Hezbollah end their ceasefire and restart their attacks. In response Israel invades Lebanon. America publicly supports Israel. President backs them strongly, even refuses to back a ceasefire.

    Why stop at Lebanon? why not Syria, there's a big US force in Iraq, next door now, so nothing to stop them. So Israel invades Syria. If they lose, America will stop Syria invading Israel and already has an army nearby. So Israel can't lose either way.

    Bush can't strongly supports them, and so can't then back down, and they have a strong lobby in US Congress and Senate to help them.

    So now they're close enough to launch missile attacks against Iran, or fake missile attacks from Iran. But Iran can't get to them except through Iraq or Turkey, both of which cause USA to join in the war.

    You see for the USA to GO TO WAR with Iran, you need the backing of Congress, Senate and people, but if the war SHOULD COME TO YOU instead, if Iran should attack USA forces in Iraq while trying to defend against Israeli missiles, then suddenly Bush & co get their war.

    So now it becomes clear why they wanted the Palestinian ceasefire to end and why Bush & Co didn't condemn their attack.

  26. Flawed Logic in summary (Flamebait as usual) by jkrise · · Score: 1

    "Federal Computer Week is reporting that the US Army will require hardware-based security via the Trusted Platform Module standard in all new PCs. They are a large-enough volume buyer that this might kickstart an adoption loop."

    Let's say the US Army buys a million night-vision goggles. Would that mean bird-watchers would throw away their good old binoculars and go in for this one?

    The TPM is actually a very sound functional and business requirement in the Army... it provides for centralised surveillance and cryptography. Businesses and civilians would indeed NOT TRUST such a technolgy in THEIR PERSONAL AND PRIVATE computers.

    Doesn't mean this wouldn't get stuffed on them though, much like DRM.

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Flawed Logic in summary (Flamebait as usual) by ObsessiveMathsFreak · · Score: 1

      Businesses and civilians would indeed NOT TRUST such a technolgy in THEIR PERSONAL AND PRIVATE computers.

      But in the future they won't be their personal and private computers. They will only be licencing the hardware and software from private companies who will still own them.

      --
      May the Maths Be with you!
  27. Dr Who spoiler warning by aldwin · · Score: 1

    Reminds me of the last episode of Dr Who for this season:

    Dalek: Identify yourself
    Cyberman: You identify yourself first
    Dalek: No you identify yourself first
    ....

    Ahhh, what we've been waiting to see for a long time ...

    1. Re:Dr Who spoiler warning by Tim+C · · Score: 1

      I love the way it ends, too:

      Dalek: The Daleks do not identify themselves!
      Cybermam: You have identified yourselves as the Daleks...

      You can almost hear the Dalek thinking "Oh, bugger".

    2. Re:Dr Who spoiler warning by dpilot · · Score: 1

      Lucky!

      You're getting the current stuff. I got the new stuff from Canadian TV last year, and this year I'm getting it from SciFi, but it's just last year's again, so I haven't seen any post-Eccelson. (I'm sure the spelling on that is wrong.)

      (I hope they manage to bring back Gallifrey. They brought back the Daleks, after all. It was fun to visit Gallifrey every now and then.)

      --
      The living have better things to do than to continue hating the dead.
  28. Might lockout GPL 3 though... by jkrise · · Score: 1

    Several members have Linux-based software stacks available.

    Much like the NVidia drivers though, these stacks might involve a GPL shim and a non-GPL binary that's checked and verified by the TPM. Probably why GPL3 is getting ready real quick.

    You try customising the kernel and alter the stack, and your hardware (the TPM) refuses to run it. End of Linux as we know it.

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Might lockout GPL 3 though... by SiliconEntity · · Score: 1

      these stacks might involve a GPL shim and a non-GPL binary that's checked and verified by the TPM

      No, the main one is TrouSerS. It's fully open source and GPL'd. Contrary to the many lies which have been circulated about it, TC is fully compatible with Linux. In fact, that's where most of the research and development work is at this time. Trusted Grub is another good example. It hashes the Linux kernel and some of the config files into the TPM chip before booting it. This way Linux systems can prove what kernel they booted.

    2. Re:Might lockout GPL 3 though... by Anonymous Coward · · Score: 0

      Bullshit... you cannot modify the code, compile it and still have it be "trusted". Yet more disingenous crap from the trusted computing shills.

    3. Re:Might lockout GPL 3 though... by zootm · · Score: 1

      Bullshit... you cannot modify the code, compile it and still have it be "trusted". Yet more disingenous crap from the trusted computing shills.

      Of course it's not still trusted. It's different. You can't change your password and have it still verify to the same hash either, can you? The hash proves what kernel you loaded, if you load a different kernel, it'll be a different hash. What you can do, if you are in the position to trust or distrust binaries, is just mark the new kernel as trusted. No problem.

      The idea of TC is to verify what software is running. If you could run different software and still pass verification, it'd be completely useless, wouldn't it?

    4. Re:Might lockout GPL 3 though... by c_forq · · Score: 1

      As long as you send the newly compiled program hash to the TPM chip it should be trusted.

      --
      Computers allow humans to make mistakes at the fastest speeds known, with the possible exception of tequila and handguns
    5. Re:Might lockout GPL 3 though... by mrchaotica · · Score: 2, Interesting
      What you can do, if you are in the position to trust or distrust binaries, is just mark the new kernel as trusted. No problem.

      No, there is a problem. In fact, it's a huge problem. The problem is, the users are NOT in the position to trust or distrust binaries!

      Because Microsoft et. al. designed the system to be secure against the user, they made it a point to withold the private key so that all signing is done by them, not the user. Considering that the entire point of the GPL is to have the user in control, "Trusted" (or rather, Treacherous) Computing is fundamentally incompatible with the GPL!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    6. Re:Might lockout GPL 3 though... by mrchaotica · · Score: 1

      Wrong. You have to send it to a certificate authority. If you could self-sign binaries, it would defeat all the DRM uses of Treacherous Computing, and considering that it was designed expressly for the purpose of enforcing DRM, that's obviously not acceptable.

      By the way, you know how Windows device drivers are going to have to start being "certified" by Microsoft? This is why they're doing it.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    7. Re:Might lockout GPL 3 though... by zootm · · Score: 2, Interesting

      The problem is, the users are NOT in the position to trust or distrust binaries!

      Why isn't the user in the position to trust binaries? In a TPM-supporting Linux stack, the only people in control of the trust or distrust are the administrators of the system. The hardware doesn't block software, the software uses the hardware to authenticate it. The software can then block it based on the rules set up by the administrator.

    8. Re:Might lockout GPL 3 though... by Phillup · · Score: 1

      Slightly off topic, but...

      It'd still be better than Windows if you could simply inspect the code... compile the code... and verify that the code you compiled matches the code they provided.

      MS shows (some) people "the code"... but never enough to actually compile the whole darn thing and verify that what they showed you is what is actually being run.

      --

      --Phillip

      Can you say BIRTH TAX
    9. Re:Might lockout GPL 3 though... by mrchaotica · · Score: 1
      Why isn't the user in the position to trust binaries?

      Because it would be just like a self-signed PGP key or SSL certificate -- it wouldn't actually interoperate with any other "Trusted" software, because nothing else would trust it. If, for example, your ISP required your machine to be "Trusted" to connect, self-signing would do you no good because it wouldn't give the external entity (i.e., the ISP) any reason to trust your machine.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    10. Re:Might lockout GPL 3 though... by zootm · · Score: 1

      I'm fairly sure it's different, there, though. The remote attestation system reportedly proves ("unforgably" - we shall see) what software a user is running. Now this system can also, apparently, prove this to an outside source (I don't know how this works, but it apparently does), which would allow them to verify that you are running certain software versions or whatever. How useful this is to an ISP this is is another matter altogether, though. I doubt an ISP would demand you run specific software. But on a closed network the remote attestation feature of TPM could apparently be used to verify that all of the computers are running the same, approved, software stack and so on.

      Worth also noting that I have no idea how TPM works (I assume there's some signed private key stored in hardware in some confusing unbreakable way, but I can't say I know what the hell that'd be), I'm just basing my answers on the assumption that it does what it's supposed to (and I'm using its Wikipedia page as a reference for that ;)).

    11. Re:Might lockout GPL 3 though... by mrchaotica · · Score: 1
      I doubt an ISP would demand you run specific software.

      Oh, there's easy "logic" behind that. First of all, the ISP has a motivation to control how you use the connection (see also: Net Neutrality). Second, once most machines are "Trusted", Microsoft will (mark my words) begin petitioning Congress to pass a law saying that only "Trusted" machines, running "Trusted" software (i.e. no Free Software) would be allowed to connect to the Internet. The reasoning, of course, would be all about preventing "piracy" and "hacking" and "kiddie porn", etc. because obviously anyone who would refuse to let Microsoft "trust" their computer is up to something no good. And the government would eat it right up, just like they've done with all the other shit big business has been spewing lately.

      Worth also noting that I have no idea how TPM works (I assume there's some signed private key stored in hardware in some confusing unbreakable way, but I can't say I know what the hell that'd be), I'm just basing my answers on the assumption that it does what it's supposed to (and I'm using its Wikipedia page as a reference for that ;)).

      That's okay, you seem to mostly get the gist of it right.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    12. Re:Might lockout GPL 3 though... by zootm · · Score: 1

      The reasoning, of course, would be all about preventing "piracy" and "hacking" and "kiddie porn", etc. because obviously anyone who would refuse to let Microsoft "trust" their computer is up to something no good. And the government would eat it right up, just like they've done with all the other shit big business has been spewing lately.

      I dunno, I just can't see IBM or Sun Microsystems (or a host of other companies) taking nonsense like this lying down. They stand to lose a lot from such a move. I don't know if MS has enough to gain (I really don't think they do) to pressure such a thing. Media companies, however, might do so (with at least MS's symbolic support, if not in a genuine coalition).

      The US government's approach to copyright law recently has saddened me quite a lot, though. It just seems to be the actions of a group of people who don't know and don't want to know about what they're legislating, deciding instead that whatever big business says is good must be good. Worrying.

    13. Re:Might lockout GPL 3 though... by c_forq · · Score: 1

      Are you sure about this certificate authority? Last I looked at it the only interactions with other computers was when you choose to interact, in which case it will give a hash of your operating system and all your programs so the other computer can choose if and how to interact with you (for example if you are running a port sniffer they probably won't allow any connection). The last time I looked at it the biggest worry was from the ISP, not the software companies.

      --
      Computers allow humans to make mistakes at the fastest speeds known, with the possible exception of tequila and handguns
    14. Re:Might lockout GPL 3 though... by mrchaotica · · Score: 1
      The last time I looked at it the biggest worry was from the ISP, not the software companies.

      The ISP won't let you connect 'cause you're running a port sniffer, Microsoft won't let you play "Plays-For-Sure" music because you're running a hacked sound card driver, Autodesk won't let you run AutoCAD because the computer's key doesn't match the one on Autodesk's server when it tries to authenticate, whatever -- it's the same kind of thing in all cases. The other party is "trusting" your computer to lock you out of their product/service.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    15. Re:Might lockout GPL 3 though... by Anonymous Coward · · Score: 0

      I dunno, I just can't see IBM or Sun Microsystems (or a host of other companies) taking nonsense like this lying down. They stand to lose a lot from such a move.

      Wrong. They have everything to gain from such a move, since they will also be in a position to dictate who is trusted and who is not. IBM is already working on a version of Linux based around a TPM... and it won't be you controlling the hardware when IBM sells it to you. Same goes for Sun, they are also members of the Trusted Computing group. And their network stacks and kernels will be "approved" and trusted for connection to the internet.

  29. Platform identity can be hidden by Morgaine · · Score: 2, Interesting
    The paragraph after the one you quoted offers us additional hope:

    • "The TCG design does not have any requirement that software be "certified" in order to use it. The specification talks in some length about ways of using the platform to create certificates for keys that are provably secure and yet not identify the platform they came from."

    In principle then, FOSS operating systems should be able to use TPM to enhance the trust that their owners have in them, in contrast to the way in which MS systems will use it to enhance the trust that content providers have in the platform. It all comes down to the way it's used.
    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
    1. Re:Platform identity can be hidden by zootm · · Score: 1

      ...in contrast to the way in which MS systems will use it to enhance the trust that content providers have in the platform.

      I personally think of this as FUD to some degree, simply because if one does not buy DRMed media, it doesn't affect MS users in any way. People seem to confuse a system supporting something with its mandatory use, which hasn't even been proposed.

    2. Re:Platform identity can be hidden by ultracosm · · Score: 1

      I thought "mandatory use" is what the OP is talking about?

    3. Re:Platform identity can be hidden by zootm · · Score: 1

      That's my point. A lot of people seem to be implying that mandatory use is a given, when I'm really not certain that it will ever come around. It doesn't look like a smart business decision for anyone, to me.

      Aside: Does "OP" stand for "Old Parent"?

    4. Re:Platform identity can be hidden by mrchaotica · · Score: 1
      A lot of people seem to be implying that mandatory use is a given, when I'm really not certain that it will ever come around.

      Microsoft: "Trusted Computing is used to prevent piracy. Therefore, anyone who doesn't support it is a dirty, evil pirate! Or a Communist hacker. Or even worse, a ter'rist! Think of the children!"

      US Government: "Oh wow, good thing you told us -- we'll get right on legally mandating it immediately! Now where was that DMCA II draft we were working on..."

      Aside: Does "OP" stand for "Old Parent"?

      "Original Post" would be my guess.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    5. Re:Platform identity can be hidden by zootm · · Score: 1

      Now where was that DMCA II draft we were working on...

      Argh, yes, well, of course idiots in government can always break the rules completely randomly. This is not an issue which should be dictated by law.

      On a side-note, I don't think Microsoft would be the ones in favour of making use of TPM mandatory in computer systems. It doesn't meet their business needs (in fact, I'd think it'd be likely to harm them). The MPAA/RIAA are very much the driving force behind mandating its use.

      "Original Post" would be my guess.

      Aha! That makes sense! Thanks, that's been bugging me for a while.

    6. Re:Platform identity can be hidden by mrchaotica · · Score: 1
      On a side-note, I don't think Microsoft would be the ones in favour of making use of TPM mandatory in computer systems. It doesn't meet their business needs (in fact, I'd think it'd be likely to harm them). The MPAA/RIAA are very much the driving force behind mandating its use.

      On the contrary, Microsoft wants this bad because it wants to be the one that holds the keys. For example, think about Windows Media and "Plays For Sure" -- Microsoft could arrange it to get a royalty from every song or video sold. That automatically gives MS the same motivation as the ??AAs, and it's just the beginning. Think of the implications for enforcing "Windows Genuine Advantage", restricting distribution of Office format documents, etc.

      Believe me, Microsoft is very interested in this. In fact, it's been the original driving force behind it, ever since it was called "Palladium!"

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    7. Re:Platform identity can be hidden by zootm · · Score: 1

      I'm really not sure that a whole secured media platform will sell, though. I just don't see people being dumb enough to buy it, and I like to have some faith that Microsoft aren't all that stupid. I'm probably putting too much faith in people again, though ;)

    8. Re:Platform identity can be hidden by mrchaotica · · Score: 1
      I just don't see people being dumb enough to buy it

      Three dollar ringtones.

      'Nuff said. (And if it's not enough, here's something else: iTMS.)

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    9. Re:Platform identity can be hidden by zootm · · Score: 1

      Truly we are witnessing the fall of civilisation ;)

  30. What about GPLv3? by SiliconEntity · · Score: 1

    So now the question is, will it be legal to transfer (or as they say, "convey") GPLv3 software to a Trusted Computer? It violates the principle that users must be able to alter their software in such a way that remote servers can't tell. Will that make it illegal to run GPLv3 software on a TC?

    1. Re:What about GPLv3? by mrchaotica · · Score: 1

      I haven't read the draft yet, but it should only prohibit distributing GPL v.3 software as "Trusted" binaries and having the system refuse to run any modified versions. Merely running Debian on a PC that happens to have a TPM (for example) should still be allowed.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  31. It makes sense, but is more danger than good by Opportunist · · Score: 3, Insightful

    It makes sense for the Army to require TCP. Stolen/lost laptops wouldn't immediately result in a security leak. But this can be achived cheaper, quicker and (and here comes the key point) with more control on the Army's side. Linux can encrypt documents just the same way TCP wants to offer, the difference lies in the open source concept: This inherently gives you the ability to check the security (provided you can read code, but I guess the Army can afford hiring someone who does) of your system.

    TCP requires you to trust the person/group that made the security for you. You put yourself completely into the hands of the corporation(s) that create your TCP platform, and you are fully dependent on their ability to come up with a good protection scheme. Not to mention that you have to trust them, implicitly, that they do not want to spy on you and that they are better than their adversaries.

    With TCP you hand over the responsibility for security. But you also hand over control. And it has the potential to lure you in a false sense of security which invariably leads to slacking. More than once I've seen a behaviour of neglect in a high security area (I've had my share of time in that field), with people relying so heavily on the technical implementations that they forgo the most basic security measures called for by common sense, because "Hell, what DO we have that security concept for, if I can't trust it fully?"

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    1. Re:It makes sense, but is more danger than good by Anonymous Coward · · Score: 0

      The US has already handed over their security to businesses -- they're called defense corporations.

  32. better one innit by ajs318 · · Score: 3, Insightful

    A country's armed forces ought to have the power to demand the full source code of every application running on their computers, and the resources to write all their own software wherever necessary. There is no shortage of Open Source applications they could use for starting points .....

    --
    Je fume. Tu fumes. Nous fûmes!
    1. Re:better one innit by 70Bang · · Score: 1



      Like this?


    2. Re:better one innit by Cederic · · Score: 1

      There's more to it than that.

      Can you trust that the version of "battlefield map - american edition" was built using the source code the vendor showed to you?

      Can you also trust that the signals you send to that device - which contain precise locations of all your soldiers/units - will only be displayed on that device, and not transmitted/relayed to a (potentially insecure) alternate system?

      I'll be honest, I don't know whether TPM will necessarily assist in such matters. I would certainly expect it to..

    3. Re:better one innit by gruhnj · · Score: 1

      A country's armed forces ought to have the power to demand the full source code of every application running on their computers, and the resources to write all their own software wherever necessary.

      You have obviously never had to administer Army software. As bad as you may think Windows software is ( and I admint at times its real bad), contractor supplied software (mostly ABCS systems) for internal Army use suck. BCS3,MC4,ASAS,CHIMS,AFATADS, etc are the most frustrating systems I have ever had to admin. The documentation and support given to these systems is poor. The contractors sent to be local subject matter experts usually have almost no more training than I do. They can't be patched normally and the they can't integrate systems that obviously go together. Apply a reasonable domain group policy and they freak out. The list goes on. Software design aint DoD's strong point.

      Having said that, what makes you think the Army could do any better than the commerical sector? If we cant get some simple thing like sending trops to war with appropriate body armor straight, why would we be good at software development? Even bigger question is do we want the army to spend the money to devlop an OS? Shouldnt we be figuring out how to fight wars? We have a budget crunch as is just to get maintence costs taken care of for things like tanks and humvees. Image the budget crunch if we went into the software development world at the just OS level. If we went into making the full application stack, we would be in an even worse budget crunch than we are now. Linux is too hard for most Army admins to admin. Heck some of the windows deployments I have seen in the army are preety screwed up. It's easier to get officers and NCO's to use windows and go through the pain of securing it than rewriting it from scratch. Open source is good, but its not a starting point for the vast majority of the Army user base.

      As for getting access to the source, your not so clueless as to think we dont have access to the source code for Windows and major apps do you? The NSA, DISA, and other government agencies have the code and they certify what we use.
       

    4. Re:better one innit by ajs318 · · Score: 1
      Can you trust that the version of "battlefield map - american edition" was built using the source code the vendor showed to you?
      Yes, because the version you are using is one you built yourself from the source code they shew to you.
      Can you also trust that the signals you send to that device - which contain precise locations of all your soldiers/units - will only be displayed on that device, and not transmitted/relayed to a (potentially insecure) alternate system?
      Yes, because the transmitting device is encrypting against a public key whose corresponding private key is known only to the receiving device. You know that the receiving device is not sending its private key or unencrypted data anywhere, because you read the source code {and it might not even have a transmitter}.
      I'll be honest, I don't know whether TPM will necessarily assist in such matters. I would certainly expect it to..
      Neither of these scenarios require TPM.
      --
      Je fume. Tu fumes. Nous fûmes!
    5. Re:better one innit by Cederic · · Score: 1


      You seem to be placing a lot of trust in the individual(s) using the device in question.

  33. Re:Trusted Computing Great for Corporate/Governmen by Anonymous Coward · · Score: 0

    Nothing you mention requires trusted computing.

    With the right privileges for a corporate setting, nothing is really gained with trusted computing. Malware? Shouldn't be a problem with proper limited accounts and proper webbrowser. USB attacks? Fix the drivers, even use C# or Java, check those boundaries for once..

    Heck, having encrypted memory is a good idea, but why should the owner of the system be locked out of their own system?

    Trusted computing is there to prevent you from owning your own machine, prevent breaking encryption of the big corporations, arbitrary enforcement of "computing laws" from the vendor, surveillance, etc.. Your machine will not longer be yours. Do not be fooled.

    The idea of having external programs running in higher privilege is just astoundingly stupid and dangerous. Ok, maybe the military will go for it, but then _they_ will own their own security (or become the laughingstock of the industry). Not so with customer-hardware.

    This is my #1 reason not to buy Macs. Screw and fuck them all to hell!!!!!

  34. Against Trusted Computing by Bromskloss · · Score: 1
    --
    Swedish plasma phys. PhD student; MSc EE; knows maths, programming, electronics; finance interest; seeks opportunities
  35. mod parent down. by Kuroji · · Score: 1

    unless iran is trying to force DRM on us too.

  36. About decryption keys by Adrian+Lopez · · Score: 1, Interesting

    If I gather correctly, the TPM takes care of providing decryption keys to the operating system once it can confirm the system is in a known state. What I still don't understand is how this "known state" together with the necessary decription keys are communicated to the TPM in the first place. Is there a central authority that takes care of this? If so, how would this affect Open Source operating systems?

    --
    "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    1. Re:About decryption keys by Anonymous Coward · · Score: 0
      The Linux kernel will run in a "trusted" environment, but the snag is that it won't be trusted by anyone other than you, unless you can get an external authority to sign your kernel binary. In effect, this makes TCPA incompatible with free software, because although you can look at the source, you can't change it without locking yourself out of the "trusted" world.

      Here is a good FAQ on the subject. http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

  37. *Israel*, unless *Israel* is forcing DRM on us by Anonymous Coward · · Score: 0

    "unless iran is trying to force DRM on us too."

    You mean *Israel*, it's Israel hardliners that are engineering the USA into a war.

  38. And So It Starts by segedunum · · Score: 0

    They're still desperately trying to find a purpose for that useless piece of junk called Trusted Computing?

  39. it's a great idea by alizard · · Score: 1, Insightful
    if the intent is to create spaces within computers where malware can run invisibly and with no possibility of elimination even if the users find out about it.

    Reminds me of the decision made to run modern US warships on Windoze.

    Military procurement and ripoff were probably synonymous as of when Sargon the Great's people were buying spears and grain to feed troops. The tradition has continued.

    The only question I've got here is how many members of the US Armed Forces are going to get killed by this set of mistakes.

  40. Just trust them ... by Anonymous Coward · · Score: 0

    How can the Army trust the module?

    Yes, I have wondered about that to. The last batch of 'Jihad XLT1000' TPM enabled PC's that was delivered to our base from the new factory in Saudi Arabia had an AK-47 logo with the words 'Osama Corp.' stamped on it and a little sticker right next to the power button that reads 'Semtex Inside'.

  41. Calm down.. by Anonymous Coward · · Score: 0

    Calling people liars are not helping anyone getting informed.

    How do you think other computers can "prove" what your computer is running- and not? If I can do whatever I like with my computer and its applications, it can no longer be trusted, right? Even a hole in the BIOS can unlock, or put VMWare in the right spot. Everything on _you_ computer has to be locked tight.

    This is for _their_ security, not yours.

    So trusted networking is just one aspect of Palladium / TCPA / Trusted Computing / whatever it is called this week, but totally dependent on _external_ control of _my_ machine for it to have any meaning at all..

    Nobody knows everything about what it will contain, but having embedded chips on the motherboard and higher-order processes which can be remotely controlled, is on the agenda and some of it already put out in motherboards in the market now.

    This is why any rational argumentation about THIS, is impossible. Because it is an always moving target, and we all know how much we can _trust_ the corporations and governments..

    Remember the PIII-id chip? Still there.. It can be activated in any Windows-machine, read and then deactivated _in software_! (Every other OS prohibits this, but the real crook is Intel)

    This is how they introduce more and more of this crap, playing on the ignorance and indifference of people.

  42. just in case... by joe+155 · · Score: 4, Informative

    ...you're interested I read a rather interesting article about trusted computing the other day ( http://www.gnu.org/philosophy/can-you-trust.html ). He makes some good points.

    --
    *''I can't believe it's not a hyperlink.''
  43. What is trusted platform? by jsse · · Score: 2, Insightful

    The follow conversation heard during my college might help to answer(or not):

    "Sir, what is a trusted system?"

    "A system where we can't trust each other."

    A brief silence...

    "Then what would it be like in an untrusted system?"

    "That we can trsut each other."

    A long death silence...

  44. Re:Trusted Computing Great for Corporate/Governmen by Anonymous Coward · · Score: 0

    Ah how terminology can be so imprecise... What you're talking about is the greedy corporation form of "trusted computing". What the parent is talking about is the Common Criteria/Orange Book form of "trusted computing". You both have correct interpretations for your respective types of "trusted computing", but they're two seperate beasts.

  45. Great idea by Anonymous Coward · · Score: 3, Funny
    Give the power to disable software used by the US military to tech companies. Brilliant, why didn't anybody think of this earlier? Will software vandors be permitted to run validatation servers on sirpanet?
    ATTENTION DOD EMPLOYEE:
    MICROSOFT HAVE DISABLED THIS SYSTEM AS WE ARE IN THE PROCESS OF NEGOTIATING A GOVERNEMENT CONTRACT WITH IRAN. THE FUNCTIONALITY REQUIRED TO WAGE WAR WILL BE RESTORED WHEN THIS TRANSACTION COMPLETES.
    Did nobody in the DOD see that god awful Irobot film?
    1. Re:Great idea by westyx · · Score: 1

      At which point the DOD response team announces it's reply with a flashbang in through microsoft's door.

      I'd bet on the DOD, every single time.

    2. Re:Great idea by Anonymous Coward · · Score: 0

      I find your lack of faith in Microsoft disturbing.

    3. Re:Great idea by westyx · · Score: 1

      awww, didums.

    4. Re:Great idea by RoboRay · · Score: 1

      Flashbang, my ass. Try a 2000lb LGB.

    5. Re:Great idea by westyx · · Score: 1

      I would imagine they'd want to capture people and equipment alive and in one piece, what with the need to turn back on functionality they've lost.

  46. Thats a nasty video by NigelJohnstone · · Score: 1

    You missed the part where Israels army accuses Palestinians of blowing themselves up to give the Israeli army bad publicity. Asymetric warfare I guess.

  47. Next Generation Security by trend007 · · Score: 3, Informative

    Hi all,

    TCG/TCPM stuff, though not completely finished (the DAA mechanism that was introduced in v1.2 is a good example of how the TCG adapted to outside criticisms, and they're starting to work on v1.3) and surely not understood (the word "trust" is a huge factor in that), is having the same effect as PKI a few years back. Except that nowadays times of ignorance and fear (in particular of the big companies behing the TCG) multiply this effect by thousands. "Trust" is more and more acting like the point of concentration of the security problems, its complexity being coupled with new emerging (and very innovative) threats.

    First think of the TPM as a chip that provides standard cryptographic functions (RAS SHA-1, HMAC, AES), so instead of doing it in software anyone will be able to use hardware implementations. Furthermore there are facilities for key creation and management. With the special focus on this "security chip" (such chips already existed in various forms), the designers hope to improve drastically the level of security of modern computer science (95% of emails are spam, botnets of millions of computers, hackers make huge money out of their job, ransomware, etc. etc.).

    Obviously this TECHNOLOGY (and please always keep this in mind: it's a tool, it is to be used by other applications, most importantly OSs, to improve security; apart from secure boot, that is not compulsory at the moment, there's no obligation to use the TPM even if it's here) is not perfect, it will evolve. It will have to CONVINCE, to get TRUST. As I'm saying to most of my Trusted Computing colleagues, I think that challenges set by the opponents of TCG are actually a means to improve the security of this technology (but beware of popularity-seeking criticisms, not all the criticisms are well-founded).

    Read tha FAQ:
    https://www.trustedcomputinggroup.org/faq/TPMFAQ/

    1. Re:Next Generation Security by The+Cisco+Kid · · Score: 1

      Yes, there is no requirement to use it, unless documents you have to be able to read require it in order to be accessed. If MS starts using it, and automatically incorporating into every Word file encryption that only Windows has access to, and only if your PC has the TPC module, its instantly everyehere. Then every publisher of anything on a PC starts tying their stuff to it to. Perhaps websites produced with MS software start to silently lock themselves to IE on Windows (without the page owner even being aware).

      A formula for the possible end of user rights and Free Software.

  48. Not quite as bad, if you know what to do by LuckyStarr · · Score: 1

    Please correct me if I'm wrong.

    AFAIK in revision 1.2 it is possible to replace the master-key in the TPM module. This was a major point of criticism of previous revisions. Of course you then lose the "benefits" of the trust-web.

    --
    Meme of the day: I browse "Disable Sigs: Checked". So should you.
  49. maybe not... by ecalkin · · Score: 2, Insightful

    They also created a language called Ada that was a replacement for Cobol. Everyone thought that the DoD requiring new programming in Ada would cause the replacement of COBOL programming Everywhere.

    Where is Ada now?

    eric

    1. Re:maybe not... by Anonymous Coward · · Score: 0

      And where is COBOL now?

  50. CIA PR man? by Anonymous Coward · · Score: 0

    I just noticed your first Slashdot comment when the woman was sacked from the CIA for saying torture is bad, and in one comment you mention you're a PR person:

    Here's your 'from a PR's mans point of view' comment:
    http://slashdot.org/comments.pl?sid=192315&cid=157 88966

    And your first comment:
    http://slashdot.org/comments.pl?sid=191823&cid=157 57809

    Are you a CIA PR man? Is slashdot important enough to warrant official turfing now with fake mod points and everything?

  51. The T.P.M. Already has a NAME by rogerborn · · Score: 0, Troll

    Its called a M.A.C. (Built by Apple Computer Corp.)

    Nuff said.

    Roger
    "If the world were a logical place, wouldn't men be the ones who ride sidesaddle?"

  52. Trusted Computing by Britz · · Score: 1

    http://youtube.com/watch?v=K1H7omJW4TI&search=trus ted%20computing

    Who will decide for them what is trustworthy and what is not? Are they going to have a backdoor? I suppose the BSA http://www.bsa.org/ just got a new enforcer!

  53. Ouch by Mark_MF-WN · · Score: 4, Insightful
    Ouch... your bitterness is truly mighty.

    You're quite right of course. If the "resistance" in Iraq confined its attacks to America soldiers, they would be freedom fighters. In reality, attacks on American troops are rare. They mostly target other Iraqis who simply aren't the "right" type of Muslim. That barely even qualifies as terrorism; it's more along the lines of a slow, decentralized holocaust.

    Imagine if the French resistance in WW2 had schismed into seperate Catholic and Protestant factions, and they'd spent all their time killing each other instead of collecting useful intelligence for the Allies. The people of Yugoslavia put aside enormous cultural difference, ceased all internal violence, and totally unified to form the largest and strongest resistance army that there has even been -- and ousted the Nazis themselves. Tito and company -- probably the best example of freedom fighters since the American war of independence. By way of contrast, consider China during WW2. If the Chinese had cooperated, Japan would have never been able to successfully invade let alone retain control once they were in. Chinese resistance failed because imperialists and Maoists were never able to put their own civil war on hold (although the Maoists apparently tried several times, which part of the reason that the people supported them after the war). It is just mind boggling how far the Iraqi extremists are from being anything other than a plague upon their homeland.

    1. Re:Ouch by octopus72 · · Score: 1

      Partisans did only a low-scale guerilla war before germans had to retreat to battle against invading Red Army. Later it was easy to push back NDH forces which were highly dependent on Hitler's military support.

      War in that area ended in a bloodbath after Bleiburg when Tito's army killed approx. 20 000 (unarmed) people with a blessing from British forces, (most killed were Croats), so they don't have a clean sheet either.

    2. Re:Ouch by Eunuchswear · · Score: 1
      You're quite right of course. If the "resistance" in Iraq confined its attacks to America soldiers, they would be freedom fighters. In reality, attacks on American troops are rare. They mostly target other Iraqis who simply aren't the "right" type of Muslim. That barely even qualifies as terrorism; it's more along the lines of a slow, decentralized holocaust.

      Sez who?

      Try http://www.slate.com/id/2135859/

      New data reveal, surprisingly, that the vast majority of the Iraqi insurgents' attacks are still aimed not at Iraqi security forces or at civilians, but rather at U.S. and coalition troops. In other words, as much as was the case a year or two ago, the Iraqi insurgency is primarily an anti-occupation insurgency.

      The statistics--compiled by the multinational military command in Iraq and reproduced in a report released Wednesday by the Government Accountability Office--raise anew a basic question in the debate over the future of U.S. policy toward Iraq: Is the presence of American troops doing more harm or more good?


      There is pretty good evidence that the Iraqi government is running sectarian death squads (Salvador option anyone? Just where is Negroponte these days?) - just how many times do we need to be told that the assasins were dressed as "special police commandos" before we work out that they were special police commandos. However, the "terrorists" are still doing what they've been doing all along, attacking the army of occupation.

      Imagine if the French resistance in WW2 had schismed into seperate Catholic and Protestant factions, and they'd spent all their time killing each other instead of collecting useful intelligence for the Allies

      Well, Gaullist and Communist actualy. Not much actual fighting between them, but if you imagine they were the best of buddies... Check out Yougoslavia for an even nastier example of how things can become under an occupation. And the resistance probably didn't see theire role as "collecting useful intelligence", a few assinations of colaborateurs, IED's blowing up enemy convoys, that was more their idea of fun.
      --
      Watch this Heartland Institute video
    3. Re:Ouch by Anonymous Coward · · Score: 0

      However, the "terrorists" are still doing what they've been doing all along, attacking the army of occupation.

      And to what end do the attackers plan to reach? With peace in the country, the foreign troops will leave the country. The violence is in essence keeping the foreign troops in the country. If they truly want to get rid of the foreign troops, wouldn't assisting in building a strong government, economy, and military for self defense be the best approach?

      I have a feeling the link you provided is overly opinionated and is under the assumption that the foreign forces are there for occupation.

      Jim

    4. Re:Ouch by Stormwatch · · Score: 1
      Chinese resistance failed because imperialists and Maoists were never able to put their own civil war on hold (although the Maoists apparently tried several times, which part of the reason that the people supported them after the war).
      Given that Mao's Great Leap Forward later killed far more people than the Holocaust, one can say that was perfectly justified.
  54. First they came... by AHuxley · · Score: 1, Offtopic
    When Microsoft came for the army,
    I remained silent;
    I was not a soldier.

    When they locked up the government,
    I remained silent;
    I was not a bureaucrat.

    When they came for the telcos,
    I did not speak out;
    I was not an isp.

    When they came for the net,
    I did not speak out;
    I was not a blogger.

    When they came for my PC,
    there was no where left to speak out.

    --
    Domestic spying is now "Benign Information Gathering"
  55. Microsoft has already won by mcc · · Score: 5, Insightful

    This would be a really worrying thing, but the fact is TPM has already won. It won the instant that Apple adopted TPM and the communities who were publicly worrying and complaining about Palladium and Trusted Computing for all those years went suddenly silent and shrugged the instant that nebulous notions like "freedom" came into conflict with solid, purdy white plastic.

    Here is the thing: TPM's adoption was waiting not on an adoption cycle exactly, but an apathy cycle. TPM was never something that the consumer was supposed to approve of, want, or even really know was there. The adoption of TPM was mostly counting on the consumer not having any idea what they were buying, counting on the blinking 12:00 effect, counting on the idea that most consumers would not even know TPM was in their computer until the first time that they try to do something and the computer says "no".

    TPM isn't there for the consumer. It's there to protect the computer from the consumers. It's there to allow software and content vendors to trust your computer, to trust your computer to ensure it will act in their interests and not yours. These vendors are the ones that TPM is being done for the benefit of, not the consumer. This means that in order for TPM to win, it isn't necessary for the consumer to "adopt" it. All that has to happen is for the consumer to fail to actively reject it when it is quietly dropped into the hardware they were going to buy anyway.

    And that's already happening. So although the military would legitmately represent an adoption cycle-- the military, of course, has a legitimate and logical need to create networks within which the machinery is trusted and the user is absolutely not-- it doesn't really matter. The military isn't the kind of adoption TPM needs to reach enough critical mass that vendors can begin requiring it in new applications, I don't think-- it's not like military hardware is going to be used to run lots of games and DRMed consumer media, as far as I know. The worrying thing is TPM's level adoption in the consumer segment, since that's where it has potential to do actual harm. And that's already begun, and so far nothing is happening to stop it...

    1. Re:Microsoft has already won by jafac · · Score: 1

      This is exactly right.

      And this infection will spread throughout the entire software industry. (mark my words).

      What Neal Stephenson missed, in the Diamond Age - was that; while compilers will make stuff, the stuff doesn't need to be decompiled. It will just disintigrate on its own after it's user stops paying the monthly fee.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  56. Scenario For TMP Use by rogerborn · · Score: 2, Insightful

    You're in the Army. You're in the field under fire. You have a hardened Army laptop. You are sending and receiving
    vital messages back and forth with another unit directing fire around your position. Your laptop doesn't have any
    software or files on it that are personal to you. Not your music. Not your games, etc. What is has is a trusted and
    fool-proof means of getting and receiving messages that you can trust with your life and the lives of your unit.

    Therefore, you trust the info on your Army issued laptop. You know that no foreign agent or enemy
    can break in and send info to you or anyone else in the system, pretending to be someone you trust.

    If your unit is overrun and you lose your laptop, anyone trying to use it without authentication or by hacking,
    will cause the laptop to self-destruct.

    It is the Army who owns the computer. They own the software. They own the system. They own the TMP.

    What everyone has been trying to do here is to apply TMP to their onw personal consumer/business computer.
    These are two separate and definitive worlds of computing operation. The only thing similar in our
    world is trusting who the person is you are communicating with, as being who they say they are, and not
    someone else pretending to be that person, in Chat or Email. But that is completely different (and minor)
    level of trust than what the Army is looking for, isn't it?

    "You already have zero privacy. Get over it."

    1. Re:Scenario For TMP Use by base3 · · Score: 1

      I assume then that the Army high command will be the ones holding the endorsement keys that control the software run on it in your scenario. We'll see if that really happens.

      --
      One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
    2. Re:Scenario For TMP Use by octogen · · Score: 1

      You know that no foreign agent or enemy can break in and send info to you or anyone else in the system, pretending to be someone you trust.

      If the software is buggy, then you can, no matter whether you use the TPM or not.
      If the software is absolutely correct, then you can't, not matter whether you use the TPM or not.

      The TPM can be used for encryption, but we already have strong enough encryption without the TPM.

      There is also a major risk: If somebody manages to take control of the TPM chip inside an army laptop, the TPM chip can be used by the hacker to protect viruses, worms, trojan horses or other malware from access by army administrators, and the attack may then remain unnoticed.

    3. Re:Scenario For TMP Use by Anonymous Coward · · Score: 0

      1. it's TPM. unless you're talking about guns (oh god, just imagine a TMP with TPM)

      2. you assume that trusting the system means it's worthy of your trust. no. it means that the system trusts the information it recieves from the other communicant to be valid information, just as that communicant trusts information from your computer to be valid solely on the grounds that some proprietary protocol measures have been met. THIS IS NOT A FOOLPROOF SYSTEM. How about when your unit is overrun, and the chinese army passes the laptop over to their computer hacking division and plant a virus as TPM valid, which every other computer that communicates with said computer sees as TPM valid, and within minutes the entire military infrastructure is switched off.

      better learn chinese.

    4. Re:Scenario For TMP Use by Anonymous Coward · · Score: 0

      "If your unit is overrun and you lose your laptop, anyone trying to use it without authentication or by hacking, will cause the laptop to self-destruct."

      So they put a gun to your head and say "Give me the password".

      And now.. the enemy has access...

    5. Re:Scenario For TMP Use by vertinox · · Score: 1

      What is has is a trusted and fool-proof means of getting and receiving messages that you can trust with your life and the lives of your unit.

      Unfortunately, your laptop was made by the lowest bidder.

      You know that no foreign agent or enemy can break in and send info to you or anyone else in the system, pretending to be someone you trust.

      Unfortunately, with this belief set hard in stone in your mind that TPM can not be hacked, you ignore signs that someone has indeed sending you bad intel because the enemy nation has bribed or tricked a top official at the Pentagon to give out his password through some sort of social engineering.

      If your unit is overrun and you lose your laptop, anyone trying to use it without authentication or by hacking, will cause the laptop to self-destruct.

      Unfortunately, you were captured during this event and spent 14 days being tortured and watching the summary execution of your squad mates until you gave the password and biometric info.

      It is the Army who owns the computer. They own the software. They own the system. They own the TMP.

      Well technically, the American taxpayer's own the computer. It is just that the Army gets a nice permanent lease on these items. ;)

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
  57. So you want to be taken serious about security? by tomstdenis · · Score: 0, Flamebait

    Step 1. Don't run windows
    Step 2. ...
    Step N. In short know what you are doing.

    I'm sorry, but they bulk order their computers from Dell and run windows in the field. I can't take their needs seriously until they grow the fuck up.

    Tom

    --
    Someday, I'll have a real sig.
    1. Re:So you want to be taken serious about security? by linuxrocks123 · · Score: 1

      My understanding was that the army was standardizing on Linux. What makes you think this isn't the case?

      --
      vi ~/.emacs # I'm probably going to Hell for this.
    2. Re:So you want to be taken serious about security? by tomstdenis · · Score: 1

      The article mentions the combo of trusted computing and Vista.

      You don't need TPM to secure a Linux/BSD/Unix box. You just need to be relatively up to date, properly patched, proper services, and deployment.

      Tom

      --
      Someday, I'll have a real sig.
    3. Re:So you want to be taken serious about security? by linuxrocks123 · · Score: 1

      > The article mentions the combo of trusted computing and Vista. /me reads TFA.

      The article does mention Vista, but only in passing, and doesn't say that's why the army wants the chips.

      > You don't need TPM to secure a Linux/BSD/Unix box. You just need to be relatively up to date, properly patched, proper services, and deployment.

      You're preaching to the choir, but you're right :)

      However, there are advantages to using TPM on a Linux box (don't know about the others), because TPM on Linux can create a "locked down" configuration, where you can only run programs that have been preapproved. This has obvious uses in the army.

      --
      vi ~/.emacs # I'm probably going to Hell for this.
  58. Feature interaction by hey! · · Score: 1

    As we all should now by now, the interesting thing when you start to add features to a system.

    Anybody care to consider what happens when we get the following:

    (1) "Trusted" Computing
    (2) "Trusted" Network Connections
    (3) A non "net neutral" Internet?

    You could well end up with a choice of only two sources of information: the media conglomerate that owns your cable company, local news paper and local network affiliate television station, or the other conglomerate that owns your DSL service, most of the radio stations in your area, and the other network affiliate.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:Feature interaction by level_headed_midwest · · Score: 1

      The computer would turn into a glorified cable or satellite box- a device operating on a closed network that runs programs that the device manufacturer and/or network operators allow. It will be a subscription service and be expensive, just like cable and satellite. You may or may not even own the computer equipment anymore- it might be leased to you from the network operators like most cable/satellite equipment.

      However, what will also happen is that there will be an underground or semi-underground network that resembles anything from a few local shares to a shadow of the Internet that we currently have. It will use older or TPM-disabled computers with OSes that do not require TPMs to operate. This can be anything from a little ad-hoc wireless network to a larger, area-wide regional networks over WiMax or similar technology. Also, people that use computers for real computing will also have stand-alone machines as in the old days.

      --
      Just "gittin-r-done," day after day.
    2. Re:Feature interaction by Fallingcow · · Score: 1

      It could be the end of popup and ad blockers.

      Welcome to the era of full-screen, un-blockable (if you want any actual content, that is) ads on the internet.

    3. Re:Feature interaction by level_headed_midwest · · Score: 1

      Yeah, unfortunately. Your choices are to either play with the new crappy rules or not play at all...

      --
      Just "gittin-r-done," day after day.
    4. Re:Feature interaction by hey! · · Score: 1

      The computer would turn into a glorified cable or satellite box- a device operating on a closed network that runs programs that the device manufacturer and/or network operators allow.

      Bingo.

      Security is a huge problem. Maybe these initiatives will allow computers to become more secure. Let's grant that for a moment. But you could also make your computers more secure by simply not connecting them to the Internet.

      It's unthinkable, of course, because the Internet is so desirable to be connected to. It is a major source of economic innovation. But when you are in control, you don't want innovation, because it is disruptive. It's natural that vendors want this level of control, because it's practically a guarantee they can make money without thinking too hard. Which is precisely why no vendor should be granted this power.

      There is nothing intrinsically harmful with the underlying technologies in TPM, or non-net neutrality for that matter. They just raise the question: given a method of control, who gets to be in control? Standardizing on those technologies without a satisfactory answer poses a danger to future innovation, possibly freedom itself.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  59. Dunno bout you but.. by andr0meda · · Score: 1

    .. I build my own computers, so what's the big deal anyway.

    Can't run windows anymore? Such a shame, we'll have to find an alternative..

    Can't run any games and apps? Even more of a shame, I'll do my own games and apps..

    I am, after all, a computer wizz kid..

    So what about you lot.. I mean it's time to raise the finger on this corporate IT world crap because it's populated with nitwits and zealots that are afraid of the one thing inherent to everything that is digitally switched: CHANGE!

    --
    With great power comes great electricity bills.
    1. Re:Dunno bout you but.. by Cederic · · Score: 1


      >> I am, after all, a computer wizz kid..

      I think even the youngest people with a slashdot user ID that low no longer qualify as 'kid'.

  60. Rubbish by Anonymous Coward · · Score: 0
    Hi Astroturfer,

    The TPM was designed to allow corporations to control peoples access to computing resources and information (including software). The hardware crypto accelerators already on the market would not be used to usurp control of our computers at a future point and this first hurdle is where the TPM falls. There is nothing the TCG could add to a TPM that would make the underlying premise for its existance palatable to this AC. Do you understand? NOTHING!

  61. Trusted Computing Great for Everyone. by Anonymous Coward · · Score: 0

    "I personally abhor the notion of Trusted Computing on my personal computer"

    Maybe the implimentation, but not the idea. TC has some pluses, amoung the least malware, spyware, viruses, and trojans will be harder to write. People will finally have end-to-end encryption that protects their privacy.

    1. Re:Trusted Computing Great for Everyone. by patchvonbraun · · Score: 1

      "I personally abhor the notion of Trusted Computing on my personal computer"
      Maybe the implimentation, but not the idea. TC has some pluses, amoung the least malware, spyware, viruses, and trojans will be harder to write. People will finally have end-to-end encryption that protects their privacy.

      The only positive benefit of the TPM, that I can see, is that it will "commoditize" secure storage for cryptographic private keys. But to go from that to "People will finally have end-to-end encryption that protects their privacy" is a very large stretch indeed. We've had cryptographic systems for e-mail, etc, for over a decade. Uptake has *not* been limited due to lack of secure hardware. Uptake has been limited by more mundane factors like ease-of-use, education, interoperability, flexibility, etc, etc. But solving those problems isn't "cool" enough for most practitioners in the cryptographic arts, so they mostly haven't been solved. TPM isn't going to fix this, unfortunately.


      In fact, it occurred to me that the Army doesn't want TPM for the TCG aspects, but rather just as a cheap and ubiquitous secure storage device for cryptographic keys. If *that's* what they want it for, then it's probably a good thing. Cheaper, in the long run, than getting outboard ISO-7816 cards for safe storage of keying material.

  62. Army will not kickstart an adoption loop by Gothmolly · · Score: 1

    The government loves to buy special versions of things. Manufacturers will be happy to supply the Army with $500 motherboards, and the rest of us will get the $79 version.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:Army will not kickstart an adoption loop by Joe+The+Dragon · · Score: 1

      Army laptops are build to used in the battle field and can take a lot more abuse then laptops that most people buy and they cost a lot more.

  63. Correct, but it DOES lock out Free Software! by mrchaotica · · Score: 1

    The way Treacherous Computing works is by only allowing privilaged operations to be run by "Trusted" (i.e., crpytographically signed) binaries. Even though you could get a binary of the Linux kernel signed by the certificate authority, it destoys the point because if you exercise your rights under the GPL by modifying and rebuilding the software, it's no longer "Trusted" because it's not signed.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  64. Re:Trusted Computing Great for Corporate/Governmen by jimicus · · Score: 1

    USB attacks? Fix the drivers, even use C# or Java, check those boundaries for once..

    FWIW, the USB attacks were "Drop a USB memory stick pre-loaded with an app which phones home in the car park outside a company".

    This stops social engineering attacks like that quite nicely.

    Oh, and come back to reality. "Fix the drivers"? How many companies you know have that as an option for their desktop PCs?

  65. Old news by Anonymous Coward · · Score: 0

    The Army states this many months ago. Not only that but TPMs have been shipping in new PCs for 2 years. The Army initiative is great but it's hardly what is necessary to "kick start" the industry. TPMs are already out there all we need is for software to catch up and for organizations to complete machine refreshes over the next year or two.

  66. Trusted computing is not necessarily bad... by jonwil · · Score: 1

    Wwill make it bad is who decides what you can run. And which external entities (ISPs, banks etc) start checking for what information.

    The idea of having a hardware device in the computer that can control what software can run, what software can access what data etc is NOT a bad thing.
    If the owner of the PC (e.g. a home user or an IT department at a corporation) controls the keys, its perfectly fine. Its only when Microsoft/RIAA/MPAA/IDSA/Government agency/etc control the keys that trusted computing is bad.

    I am all for fighting the use of trusted computing to control what we can run on our PCs or what we can talk to (e.g. trusted internet, banks blocking non trusted PCs etc) but lets not ignore the usefull uses of trusted computing here.

    Some good uses of trusted computing:
    Users using it to block viruses, worms, spyware, malware etc from running
    Corporations/IT departments/etc using it to control the installation of unapproved software on employee PCs
    Companies using trusted computing to protect sensitive data (for example, even if a hacker could get into the server holding all the credit card numbers, they wouldnt be able to use the hacker tools to get all the numbers out because trusted computing would prevent the hacker tools from running. Wont stop the hacker but would make it harder. Also prevents hacker from installing rootkits or other tools since they wont run or will cause the signature on the OS binaries to no longer be vaild)

    1. Re:Trusted computing is not necessarily bad... by patchvonbraun · · Score: 1

      Some good uses of trusted computing: Users using it to block viruses, worms, spyware, malware etc from running Corporations/IT departments/etc using it to control the installation of unapproved software on employee PCs Companies using trusted computing to protect sensitive data (for example, even if a hacker could get into the server holding all the credit card numbers, they wouldnt be able to use the hacker tools to get all the numbers out because trusted computing would prevent the hacker tools from running. Wont stop the hacker but would make it harder. Also prevents hacker from installing rootkits or other tools since they wont run or will cause the signature on the OS binaries to no longer be vaild)


      Some of these uses superficially look good on the surface. For example, who could argue with the IT department at MegaCorporation of America that they should be able to control what software you're allowed to have/run on the computers owned by the corporation. Who could argue with that? It seems like motherhood and apple pie....


      Except that in large companies, particularly large knowledge-driven, high-technology companies, the IT department has nearly no clue about what it is that the computers that are under their care can legitimately be used for. The problem is that for the most part, IT doesn't know that they don't know. In effect, such draconian "authorized software only" policies, along with the TCG/TPM/TCPA technological policy enforcement machinery allows IT departments to redefine that which constitutes useful work.


      Imagine a scenario where you've spent the day writing some piece of exploratory data analysis code on your desktop computer at MegaCorporation of America. For whatever reason, it needs to be "installed" to work properly. The next time you reboot, or the network does a "authorized software" probe, it finds that you've installed some "contraband" software, and kicks you off the net, and sends an audit report to a witless IT-security department.


      Maybe you didn't write the software yourself. Maybe your whiz-kid highschool intern wrote it on *his* PC, and sent it to you. You utterly trust that it's "good stuff", but because of IT policies, and the technology to back up those policies, you're screwed, and if you try to install and run it, you'll be getting a visit from the jackbooted thugs in HR tommorow.


      Of course, compilers will no longer be "authorized software" in this new dystopian world. You could, after all, use a compiler to hill-climb your way into bypassing all the "Trusted Computing" nonsense on your desktop computer.


      This technology has really-bad, far-reaching, socio-political and technical consequences, and clearly cannot be made to "work" for a suitably-robust definition of "work". I can't understand why it's still being pursued so aggressively, except that most folks, IT purchasing and CIOs included, will by any-old snakeoil if it's marketted aggressively enough.


      I worked in IT security for over a decade at a large company. I do have *some* insight into how this nonsense will actually get deployed, and I'm fairly certain that the nighmare scenario outlined above *will* play out in many cases.

    2. Re:Trusted computing is not necessarily bad... by DanQuixote · · Score: 2, Insightful


      Amen!

      A knife is not a bad thing. It is not a good thing. It is only a thing. Some will use it to threaten and mug, others will use it to dice tomatoes or perform surgery. It is only a thing.

      A gun is not a bad thing. It is not a good thing. It is only a thing. Some will use it to stop invaders or obtain meat. Others will use it to hijack planes. It carries no inherent righteousness or villany.

      A Trusted Computing Platform is not...

      Come on people, separate the tool from the actions of saints and sinners so that we can make engineering trade-off based decisions instead of emotional ones.

      --
      "We think people rightly feel that once they buy something, it stays bought," --Suw Charman, Open Rights Grp
  67. More Information? by jefu · · Score: 1

    Are you are saying that if I connect to a web server running some sort of trusted computing, I will be able to trust it to not serve me malware?

    I don't think I've ever seen any of the TCPA people claim anything like that (caveat: I've not read anywhere near all the stuff published on the topic of trusted computing). They do claim that if the malware is served to the client machine that you should be able to set things so it will not run.

    Might you me so kind as to provide some nice pointers to papers or web pages that both make this claim and give some techincal info on how it will be accomplished?

    In the meantime, I think it is only proper to remain more than a bit dubious.

    1. Re:More Information? by SiliconEntity · · Score: 1

      Are you are saying that if I connect to a web server running some sort of trusted computing, I will be able to trust it to not serve me malware?

      You could get a degree of trust in it, yes. It could publish its software configuration, signed by a crypto key embedded in the TPM chip. This way you could verify that it was running the latest patched version of Apache and other software, and had no intentional malware insertion features.

    2. Re:More Information? by patchvonbraun · · Score: 1

      Are you are saying that if I connect to a web server running some sort of trusted computing, I will be able to trust it to not serve me malware?

      You could get a degree of trust in it, yes. It could publish its software configuration, signed by a crypto key embedded in the TPM chip. This way you could verify that it was running the latest patched version of Apache and other software, and had no intentional malware insertion features.


      Only to a very small degree. The only thing you'd know is that at some point in the machines past, the system software ran the code through the TPM to get a TPM "attestation". Which says *nothing* about the current state of the system. Nope, in order to get a sanity statement from that web server that you can trust, you'd have to solve the Halting Problem. Good luck.

  68. Only NSA approved hardware please. by mrmeval · · Score: 2, Funny

    The army is stupid. It should mandate it's own standard for this using NSA approved hardware.

    Sheesh

    --
    I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
  69. This could be a good thing... by mutterc · · Score: 1

    ... for the Army's applications!

    The whole point of TPM is to be able to restrict what the computer's owner can do with the machine or the information thereon. Keep in mind that also, a computer's owner (as far as software is concerned) is essentially whoever has physical possesion of the machine.

    The Army could use TPM to ensure that even if a machine is stolen physically or owned by malware, its software and information can be kept safe.

  70. Re:Correct, but it DOES lock out Free Software! I by tinkerghost · · Score: 2, Interesting

    The way Treacherous Computing works is by only allowing privilaged operations to be run by "Trusted" (i.e., crpytographically signed) binaries. Even though you could get a binary of the Linux kernel signed by the certificate authority, it destoys the point because if you exercise your rights under the GPL by modifying and rebuilding the software, it's no longer "Trusted" because it's not signed.

    Yes it's true. After you make changes to the sourcecode of software and re-compile it, it's no longer 'Trusted'. BECAUSE THAT'S THE WHOLE POINT!
    Back off of piracy and conspiricy issues. If I write 'FSM-wordprocessor' and get it signed, you and everyone else gets to trust that I & the signing agency have verified that the software is exactly as I intended it to be. Currently if Bob decides to create a virus, he can create one that rewrites one of my modules to do what it was originally intended to do, as well as whatever malicious thing he want's it to do. Currently there is no way for me to verify that when I run 'FSM-wordprocessor', I am running the original code, or the one with the virus. Trusted computing does that. That's why the military wants it. It fulfills a vital security role for them.
    For the average user, it also fulfills a vital role. "Hey my OO2.0 pops up as not trusted ... but I didn't change anything. Perhaps I have a virus." It's again a way to verify that changes you didn't make, arn't being run. In that respect it grants the user more control over their computer, because it provides them with more information.
    The only time trusted computing doesn't make sense, is when you are working in a development environment. In any live production environment, knowing that what you think you are running is what is actually running is a good thing. When you are doing development, obviously you can't get things certified each time you recompile it - hell on a bad day, that would be 30-40 recerts for a subroutine. What you need is degrees of trust.

    • High order Trust:
      • 3rd party certificate
      • verification that provided software is 'clean' and un-altered.
      • automatic acceptance on all systems
    • Group Trust
      • signed by a local agency - the company IT dept
      • verification that the provided software is suitable to run within the group
      • automatic acceptance within the group - untrusted on all others
    • Personal Trust
      • signed by you
      • no verification other than personal accptance & active signing
      • automatic trust only on the system it was signed on - untrusted on all others
    • Untrusted
      • Not signed
      • no verification
      • no automatic trust

    If you want to tweek & recompile the kernel, go ahead & then hit it with a 'personal trust' cert. But don't hand it to me & say this is the greatest mod to the kernel ever & expect me to trust it. The problem is not with 'Trusted Computing' the problem is with implimentation. If there is only Trusted/UnTrusted, then there's an issue. If I can define who I trust and what I trust, then things are good. If I can only trust what somebody else tells me is trustworthy, then it's bad.
    The problem is going to be when you take your personal signed kernel and try to run trusted software that is going to go looking for a 'High Order' cert. Let's face it, if my concern is securing data - state secrets or 'Boy Band of the Week vol 1' - I can't verify that the data is secure if you have changed the kernel, since you could be ghosting every buffer to a non-secure memory space. Now is that a problem? only if you are trying to use software that explicitly requires the OS to be certed. Most FOSS isn't going to care. The stuff that does is going to be related to securing other people's Data. IE. you won't be able to run 3rd Party Secure Data Relay Proxie v4 on an unCerted Kernel because the 1st & 2nd p

  71. Very simple loophole for DoD by nonlnear · · Score: 1
    The GPLv3 intro states:
    To protect your rights, we need to make requirements that forbid anyone to deny you these rights or to ask you to surrender the rights.

    For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

    The obvious loophole for (non-civilian) DoD developers is that they don't have any of the rights that GPLv3 is refering to. Therefore the restrictions whose stated purpose is to "protect your rights" explicitly don't apply to them. After all, it is impossible for a code writer to give the right to distribute to a DoD programmer who is using that code in a classified/restricted access project. This entire paragraph is the basis for its own nullification in the case of DoD work.
    --
    argumentum ad fallacium: Fallacy of defining a fallacy which allows one to dismiss the argument in question.
    1. Re:Very simple loophole for DoD by mrchaotica · · Score: 1

      In the case of the DoD, it's even simpler: the GPL doesn't require distributing source code if the program is used internally by an organization.

      My previous post was about the general case, however.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Very simple loophole for DoD by nonlnear · · Score: 1
      Ah. I thought that, within the context of the story, you were raising a DoD secific issue.

      I agree there are some big questions about how to make something like GPLv# "work" - even in a civlian setting.

      --
      argumentum ad fallacium: Fallacy of defining a fallacy which allows one to dismiss the argument in question.
    3. Re:Very simple loophole for DoD by mrchaotica · · Score: 1

      The person I was replying to seemed to be asking about the general case. Otherwise I wouldn't have mentioned it.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    4. Re:Very simple loophole for DoD by fastgood · · Score: 1
      we need to make requirements that forbid anyone to deny you

      Yeah, right. You and what Army ?

  72. Trusted Computing Great for Everyone-weakest link. by Anonymous Coward · · Score: 0

    Not really a stretch so much as it is closing a hole. All the methods you mention while providing greater protection than nothing at all. Still leave the end points as the weakest link (read the FF extension story).

  73. no - *distrust* more like by ajs318 · · Score: 1

    Well, the whole idea is that the person using the device should not have to trust anyone else, least of all the supplier; and the supplier of the device should not have to trust the user. The source code, and any binaries compiled from it, are "safe to lose". The encryption algorithm tells you nothing without the private key {which was put there by the user}.

    --
    Je fume. Tu fumes. Nous fûmes!
  74. And from the actual GPLv3: by nonlnear · · Score: 1
    That was just the preamble. Of course, if that were the only place where that argument could be used, it's meaningless. However, looking at the actual license, we see parts where the same line of reasoning applies:
    From s3 p1,p2:

    Regardless of any other provision of this License, no permission is given for modes of conveying that deny users that run covered works the full exercise of the legal rights granted by this License.

    No covered work constitutes part of an effective technological "protection" measure under section 1201 of Title 17 of the United States Code. When you convey a covered work, you waive any legal power to forbid circumvention of technical measures that include use of the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing the legal rights of third parties against the work's users.

    First off, if the DoD uses GPLv3 code to develop TPMed apps for DoD use, then the "rights" language obviously doesn't apply, because DoD users don't have any "right" to use their work machines' software in any way other than they are told to.

    Secondly, in the case of a user of a DoD machine, the DoD is not a "third party". The user is acting as an agent of the DoD. And not in the civil court sense. In military legal reasoning, when acting on behalf of DoD, you are DoD. Thus, TPM restrictions aren't "a means of enforcing the legal rights of third parties against the work's users."

    The issues are thick and deep here, but the real point is that the (civil) legal constructs in GPLv3 simply don't apply to the scenario of DoD using GPLv3 code to develop apps for DoD use.

    --
    argumentum ad fallacium: Fallacy of defining a fallacy which allows one to dismiss the argument in question.
    1. Re:And from the actual GPLv3: by SiliconEntity · · Score: 1

      Here's an example of what I was wondering about. Suppose a DoD employee has one of these Trusted Computer systems, and he wants to download some GPLv3 software. Maybe a future version of Firefox or something. Then the website he downloads it from is "Conveying" him the software in the meaning of GPLv3. And part of the requirement of that "Conveyance" is that the user can alter the software and remote systems can't tell the difference. But maybe on a Trusted Computer that is impossible. So, someone has violated the license. But who? Is it the user who downloaded the software? The DoD that made him get this computer (or gave it to him)? Seems to me it is the web site which is bound by the license and is limited in who it is allowed to "Convey" the software to.

  75. Spying concerns? by phorm · · Score: 1

    Did the US government or some related body ban the use of Lenovo laptops because of suspicions that they might contain hardware/software used to spy on the user?

  76. Rehash of Censorship Arguments by Dareth · · Score: 1

    Censorship can seem like a good thing in theory. Keeping the "bad" things away from the people who do not want or need them. The problem comes from when someone(s) gets to arbitrarily decide what other people do and do not want or need.

    Who gets to decide? Who can influence the decisions? Can/Do people get to decide for themselves what is trusted?

    The last point is where we are now and it apparently does not work. People in general do not know what they can trust and not trust. So they have to rely on "experts". But what about the people who are "experts" in their own right and do not trust the other "experts".

    Another person on slashdot put it quite well by saying:
    "Censorship is like saying a grown man can not have steak because a baby can not chew it."

    --

    I only look human.
    My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
  77. mod parent up, also a map by Anonymous Coward · · Score: 0

    I never realized how close Iraq and Israel are, look at the map, he makes a lot of sense:

    http://maps.google.com/?ie=UTF8&ll=33.979809,46.31 8359&spn=27.360892,34.49707&om=1

  78. No Choice? by Garrett+Fox · · Score: 1

    As I understand it, you'll probably be told that similar technologies like the "broadcast flag" are mandatory. In other words, that it'll be illegal to build hardware that is not slaved to whatever government/industry commands are in place. Even with Linux and FOSS applications, will you be permitted to own a computer that you can trust not to be somehow subverted?

    The FCC's rule is in 47 CFR 73.9002(b) and the following sections, stating in part: "No party shall sell or distribute in interstate commerce a Covered Demodulator Product that does not comply... - http://en.wikipedia.org/wiki/Broadcast_flag

    And remember that everything is interstate commerce.

    --
    Revive the Constitution.
  79. Not such a bad idea by dysk · · Score: 1

    Actually, TPM is a perfect solution for the military. For several years the military has been having issues that there's no standard hardware encryption, so in some cases they use hardware that goes on the SCSI bus and hard drive and encrypts everything that goes onto the hard drive (obviously not useful for a laptop). In other cases, they use software for encrypting specific files, but have no way of guaranteeing that the user encrypts everything that's sensitive. In other words, the military is still relying on physical security, and that's not good enough anymore as laptops are way to easy to steal or "lose"

    I'll bet that the military is a big enough customer that they could get their own public key put on the TPM chips. This would allow them to encrypt every one of their hard drives so it doesn't work on non-military hardware (remember the USB drives showing up at bazaars? Imagine if they were only readable on military-issued laptops or in conjunction with RSA fobs) They could also make it so that people can only install software on their computers which is certified for the classification level of that computer, as another problem that they have is people installing programs that could contain spyware on their secret and top-secret laptops.

    The reason that we dislike TPM is because it gives the administrator complete control over the platform. That's exactly what the military needs.

  80. Wait'll Microsoft "Asimov's" their systems. by mmell · · Score: 1
    (Reference to Babylon 5, when Bester explains to Mr. Garabaldi that he can't act against the Psi Corps because he's been "Asimoved" - instilled with a rule which won't permit him to directly act against Psi Corps or any of its personnel)

    I can see it now - "Firing solution discarded: potential damage to Microsoft-owned assets. Fire mission against enemy aborted (OKAY) (CANCEL)"

    Anybody remember the first tests of the Aegis-class cruiser? The first US Navy vessel controlled exclusively by a Microsoft product (Windows NT)? That's the ship which identified Catalina Island as a "fast moving target" and proceeded to lock her guns on the vessel assigned to monitor operations (the USS Forrestal, if memory serves). They had to shut down the entire ship and have her towed back to port. Yeesh! Daystrom's M5 duotronic unit, all over again (at least this one had an "off" switch)!

    And what will TCM do if a unit suffers battlefield damage and a solution improvised to bring it back up? For battlefield conditions, a ruggedized, highly-available system is required. How do we reconcile that with TCM, a single point-of-failure if ever I saw one!

    1. Re:Wait'll Microsoft "Asimov's" their systems. by NotBorg · · Score: 1

      Anybody remember the first tests of the Aegis-class cruiser? The first US Navy vessel controlled exclusively by a Microsoft product (Windows NT)?

      What are you talking about? Aegis is Unix, VX Works, and Cisco. Windows NT is whats used to receive e-mail on a completely separate LAN. Aegis is a piece of crap, but it's not Windows powered.

      --
      I want this account deleted.
    2. Re:Wait'll Microsoft "Asimov's" their systems. by mmell · · Score: 1
      Wrong-o!

      Stick to what you know - you'll look a whole lot smarter!

    3. Re:Wait'll Microsoft "Asimov's" their systems. by NotBorg · · Score: 1

      From your article: "This is the only time this casualty has occurred and the only propulsion casualty involved with the control system since May 2, 1997, when software configuration was frozen," Vice Adm. Henry Giffin, commander of the Atlantic Fleet's Naval Surface Force, reported in an Oct. 24, 1997, memorandum.

      The Propulsion system is not Aegis. IT21 not Aegis either. Don't be confused by the ship being Aegis class. Just because I throw a Dell on an Aegis class ship doesn't make it an Aegis Dell computer.

      --
      I want this account deleted.
    4. Re:Wait'll Microsoft "Asimov's" their systems. by mmell · · Score: 1

      Read more carefully. The ships entire command and control structure were relegated to Windows NT at that time. After testing, the Navy fell back to existing solutions; whether this remains the case I don't know, but I do remember the test I described as being the first test of an "all Windows NT" solution. The article I cited was not specific to the test I remember (it was a long time ago, after all), but was intended to refute the AC's assertion that NT wasn't in use.

    5. Re:Wait'll Microsoft "Asimov's" their systems. by NotBorg · · Score: 1

      Read more carefully. The ships entire command and control structure were relegated to Windows NT at that time. After testing, the Navy fell back to existing solutions; whether this remains the case I don't know, but I do remember the test I described as being the first test of an "all Windows NT" solution. The article I cited was not specific to the test I remember (it was a long time ago, after all), but was intended to refute the AC's assertion that NT wasn't in use.

      What am I to read more carefully? Show me where you read that Aegis weapon system was ever Windows NT based. It's true that NT was widely adopted and replaced many Unix systems in the Navy aboard ships (primarily supply, logistics, maintenance management systems) but not at the core of the Aegis weapon system or the Aegis display system.

      Yes there are NT boxes where there shouldn't be (ie the box that rendered Yorktown's gas turbine propulsion system useless). Yes NT is widely used for many things, but not for Aegis. Been there, seen it, worked with it on two different ships. One ship was old as dirt and one was fairly new.

      --
      I want this account deleted.
  81. Mass Market Won't Take TPM by mpapet · · Score: 1

    In the next 5+ years 100% guaranteed.

    How do I know this?

    As someone that has seen sell-through market data for PC's of all kinds in the recent past, I have an seen the data to back my conclusions.

    Panasonic made (makes?) a ruggedized laptop specifically for public agency markets.
    1. It's too expensive for regular consumers
    2. Doesn't have any feature a regular consumer -wants- to warrant paying more.
    3. Volume isn't there for Panasonic to use the product as some kind of magical lever into mass-market.

    TPM is similar in nature, only add to this the MOBO manufacturers are running on razor thin margins. You expect them to just add $6-15 per mobo + R&D implementing the thing to satisfy a narrow customer range? Nope.

    An OEM will make a MOBO for some brand with a TPM and probably a couple of other gov't features, but there's no volume, so it will be *really* expensive. But a couple of brands that do lots of Army business will buy it. Will the mass market rush out and buy this mobo? No. Too expensive. Will the OEM market it on their own? Not likely.

    Microsoft has spent years trying to force MOBO OEM's into doing things their way and most give them a polite "No thank you. But can you fix problems XY and Z in your OS so our MOBO's work better?"

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  82. Misconceptions about TC by SiliconEntity · · Score: 1

    if you exercise your rights under the GPL by modifying and rebuilding the software, it's no longer "Trusted" because it's not signed.

    You've been posting a lot on this, and it's not right.

    First of all, there's no such thing as a distinction between "Trusted" and "Untrusted" software in absolute terms. Second, software does not have to be signed.

    What actually happens is that TC systems can be designed to keep track of the hashes of all the software that runs, and load those hashes into the TPM chip. THe chip can basically do two things with them. It can encrypt data and lock it to the hashes, such that the data can't be decrypted unless the machine is in exactly the same software state. Or it can report the current hash values, signed by the on-chip, unspoofable crypto key.

    That's the true functionality. Now, from this, you can get features that work similarly to what you say, but not exactly.

    If you change software, especially your OS software, and reboot, the TPM chip will get a different set of hashes loaded into it during the boot process. If you had previously locked (encrypted) data to the old system configuration, you won't be able to decrypt it now. You'd have to reboot back into the old configuration. If your old OS was high-security, say a SELinux configuration, and the new OS is a live CD you inserted to bypass the security, you won't be able to do so.

    But it's not like the old OS was "Trusted" and the new OS is "Untrusted". It's just that they have different hashes and produce different software configurations. Data locked to the new configuration can't be decrypted in the old one, and vice versa.

    The other thing the chip can do is to optionally report out to remote systems what your software configuration is. Maybe someone will only talk to you if you are running a certain configuration. Then, FROM HIS POINT OF VIEW, that configuration is "Trusted", and he won't trust any other. But it's not true in absolute terms that your computer is in a "Trusted" state or not. It's just that party's opinion about which software configurations he chooses to trust. And you could even imagine a system in which party A only "Trusts" one configuration while party B only "Trusts" an incompatible configuration. I'm sure this kind of conflict is likely to happen in the early days of TC, if it ever gets to this point.

    And keep in mind that you can turn this around, too. You could connect to remote systems, say e-commerce sites or other servers, and they could use TC to report their software configuration to you. Then you might choose to trust only certain software versions, maybe systems with the most recent patches for example. Or you could have a P2P network and each computer could check that the others are running good versions of the software, to prevent people patching their systems to allow leeching or flooding attacks. There are a lot of other uses for this technology beyond DRM.

    Note though that a P2P network like this would apparently be illegal under GPLv3. It would not be allowed to have software that queries the state of the peers and only connects to them if they are the same software, because this would prevent people from patching their software and continuing to participate in the P2P net (they'd have to start a new subnet of their own). So this potentially useful security tool is being shut off from the world of GPLv3. Luckily, people can continue to use GPLv2, which I expect to happen.

    1. Re:Misconceptions about TC by mrchaotica · · Score: 1
      Then, FROM HIS POINT OF VIEW, that configuration is "Trusted", and he won't trust any other. But it's not true in absolute terms that your computer is in a "Trusted" state or not. It's just that party's opinion about which software configurations he chooses to trust.

      This is exactly the situation I'm trying to warn people about. I suspect Microsoft is going to try to build up a whole "ecosystem" of software and media that only "trusts" Windows' configuration, as yet another attempt to marginalize Free Software, and I don't like it at all. Moreover, I'm convinced that this scenario is the driving force behind Microsoft's push for it.

      In other words, the fact that there do happen to be a few other uses of TPMs is irrelevant because this one is the reason Microsoft came up with the idea in the first place. Besides, everything that Treacherous Computing can do except DRM can be accomplished by normal, software-based public key cryptography!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  83. That isn't sufficient. by Irvu · · Score: 1

    If the BIOS hashes the boot loader and stores it, assuming the BIOS is operating properly then that does not necessarily provide security. If the TPM chip is as passive as you say then all it can do is answer the following question: "What is the last hash you were fed?" It can answer this using a signed key to show that it isn't lying. However that alone isn't security. Some measure must be made to compare the hashes to a "gold standard" in order to verify that they are correct.

    Given a BIOS B, B can be coded to hash the boot loader before using it. However, unless B "knows" what the correct hash is, it is only handing over control to "some program". If the chip operates as you say, and the chip has no knowledge of what the hash "should be" then control is surrendered at that point. B hands off to a boot loader and the boot loader does whatever it wants. If the only measure of correctness is "the last hash read" then B cannot be certain that what it is about to run is correct. This also holds true for boot loaders handing off to OS's etc.

    Either B would have to be hard-coded with knowledge of what the "correct" boot loader hash would be, or the chip would. In either case the hash would have to be non-writable and, itself hashed or the system breaks down. If I can access in any way the storage point for the "verified" hashes then they can be replaced with falsified ones. However if the hashes are hard-coded then I can never upgrade or alter the software (without obtaining a new chip) because the hashes would change.

    The only way that the system could work is if a) there exists a mutable storage system for "gold standard" hashes, b) the chip is capable of comparing a signed hash to a gold standard hash in a secure way, c) the algorithm used to do so is always secure and cannot be broken, and c) all of the software run on the system is "completely secure" and no bugs or deliberate attacks allow for the hash system to be fooled. If at any point any of these are violated then an attack is possible. False hashes can be planted for the future and the system is violated.

    Keep in mind that hashes are many to one functions. MD5 has been cracked. Others can be as well.

    1. Re:That isn't sufficient. by SiliconEntity · · Score: 1

      If the TPM chip is as passive as you say then all it can do is answer the following question: "What is the last hash you were fed?"

      That's not quite how it works. When I said that these hashes get fed to the TPM, I didn't say how it digests them.

      The TPM has several 20-byte registers called Platform Configuration Registers (PCRs). They are initialized to zero. When it receives a hash it gets folded into one of the PCRs. It does this by computing PCRn = SHA1 (PCRn || NewHash), where || means concatenation. In other words it takes its current hash value, concatenates the new hash value, SHA1 hashes this 40-byte buffer to get a new 20-byte hash, and stores that.

      This provides an update function that cannot be rolled back. If, during the boot sequence, any component deviates from a standard configuration, the PCR register will be changed irrevocably. It will be impossible for any later software action to feed anything to the TPM that would get the PCRs back to what they were supposed to be.

    2. Re:That isn't sufficient. by Irvu · · Score: 1

      Even if that progressive update is the case, it does not guarantee the security. Unless a method is available to verify the current state against "what it should be" then the chip itself provides no security. And if the hashes can be modified then any given system can backcheck to see that it was loaded "properly" provided it can accurately compare the hashed results, but it cannot do a forward look to ensure that it will be loading the correct software.

    3. Re:That isn't sufficient. by SiliconEntity · · Score: 1

      Unless a method is available to verify the current state against "what it should be" then the chip itself provides no security.

      That's not true. One of the capabilities of the TPM is to encrypt data and lock it to the current software configuration. Then if you boot a different OS, the software configuration will be different and it will be impossible to decrypt the data. You will only be able to decrypt the data if you are running the original configuration. This lets a high-security OS lock up its data and be assured that if a low-security OS is booted instead, it won't be able to access the data. That's good security without any concept of "what the state should be".

      Also, systems can report their state securely to remote computers on the net. The TPM signs the status report using a key embedded in the chip, that never leaves the chip and is known to be a valid TPM key. This lets remote computers decide whether they want to trust the local system, based on its software state as reported in this way.

      And if the hashes can be modified then any given system can backcheck to see that it was loaded "properly" provided it can accurately compare the hashed results, but it cannot do a forward look to ensure that it will be loading the correct software.

      Well, even without a TPM you could modify software (say, the Grub boot loader) with a list of known good hashes and only let them load the next step if it matched an expected hash. This kind of thing is always possible and is pretty much independent of what Trusted Computing aims to achieve.

      TC lets you boot and run whatever software you want. (Claims to the contrary are probably the biggest TC related lies.) But as I have described above, its goal is to reliably detect what the system configuration is, and to then be able to lock data to that configuration, or report it to remote peers. This lets remote systems know, for example, that not only will data they send you be treated according to certain rules (which they know because they know what software you are running), but that your system can lock up that data so if you booted into software that wouldn't follow those rules, it couldn't access the data.

      That's how it really works, despite the lies to the contrary. You can boot and run any software you like, yet data can be protected with high security. It's really an amazing architectural achievement.

    4. Re:That isn't sufficient. by bloo9298 · · Score: 1

      The access checks are made on other computers that communicate with the system that has a TPM.

  84. Re:Not such a bad idea? by Anonymous Coward · · Score: 1, Interesting

    "remember the USB drives showing up at bazaars?"

    Here's a clue, the Army/Air force/Marines/Navy may be dumb at times, but sometimes - just sometimes, they get it right.
    Disinformation is alive and well.
    Trusted hiring? Well thought out, opportunities for information theft?
    Priceless.

  85. "The Army" is far from monolithic by briancnorton · · Score: 2, Insightful

    To say that "the army" is requiring all pcs to do anything is questionable at best. What this appears to apply to is the enterprise systems. That's maybe a couple hundred servers that fall into the command of Netcom. I see no mention of netcom having responsibility for things like desktops, agency by agency servers, etc. Never can tell though.

    --

    People who think they know everything really piss off those of us that actually do.

    1. Re:"The Army" is far from monolithic by Gogo0 · · Score: 1

      Figures, someone who knows what theyre talking about and there are no mods in sight.
      But yeah, it is hard to tell with articles like this. I read one a few months back about the army's "SuprNet".

  86. Actually, that is EXACTLY wrong. by IBitOBear · · Score: 1

    You (or I in this usage) have no warrent about the remote machine _unless_ You are the keeper of the keys of that remote machine. So on average, _I_ cannot trust my computer, nor can any other normal user. The all powerful and all mysterious _they_, in turn _can_ trust my computer to run (ominous hum) _THEIR_ software on my computer.

    So in the current formulation, If my computer is talking to your computer, my trust of you is irrevelent. Our conversation is only as trustworthy as our collective trust in "them".

    For instance:

    Under "TCP" you and I are running MS Net Meeting. I can make no assertion about Net Meeting, you can make no assertion about Net Meeting, and Microsoft asserts that it will do whatever it is that Net Meeting does. Is this any warrent of safety? No. (much like all their products are unassailably safe, to be sarcastic,) If Net Meeting has an exploitable flaw I now have a garantee that I can exploit your computer. That is, I "trust" what I see as Net Meeting *is* net meeting, so I can operate against your flawed computer with the certianty of my "trust" in microsoft's flaw. I know FOR SURE that you are vulnerable.

    Contrapositively, in the absence of TCP, that thing that _says_ it's Net Meeting, might in fact be a custom application (say a comercial anti-intrustion package) wrapping or replacing Net Meeting.

    So in the world of trusted computing, I, exploit in hand, can operate with utter confidance that you cannot intercept or prevent my evil-doing; but without "Trusted Computing" I have to watch my step.

    Further, with "Trusted Computing" we cannot control what our computers are doing, only the keyholder can. So Microsoft can trust that they can, for instance, hold all your Word Doccuments hostage to a monthy rent on Word, and you can trust that you will have to pay that rent to access your Corporate Legacy, or that Novel you are Writing, or your Master's Thesis.

    Trusted computing does NOTHING for you, the user, but promise that you, the computer user, are powerless. Everybody else gets a free ride. Just like all Digital Restrictions Mandate technology, it isn't good for _YOU_, it is only good for some un-defined and un-accountable "THEM" somewhere.

    And, no, this isn't just paranoia. Try playing your iTunes "Purchase" (yea, right) on a Creative(tm) Nomad(tm) some time.

    --
    Innocent people shouldn't be forced to pay for inferior software development.
    --"Code Complete" Microsoft Press
  87. Re:secret agent man! they've given you a number... by Kuroji · · Score: 1

    If only I were so lucky; my dealings with the public are a lot more limited. I'm more of a logistics type of person, but then I deal with strictly domestic issues in the midwest, particularly in the medical field.

    Translation: I dispatch ambulances in Ohio and deal with nursing homes on the phone.

    Obfuscation is fun!