Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

No Backdoor in Vista

Posted by Zonk on Sat Mar 04, 2006 07:41 AM
from the inappropriate-comments-aplenty dept.
mytrip wrote to mention a C|Net article stating that Vista will not have a security backdoor after all. From the article: "'The suggestion is that we are working with governments to create a back door so that they can always access BitLocker-encrypted data,' Niels Ferguson, a developer and cryptographer at Microsoft, wrote Thursday on a corporate blog. 'Over my dead body,' he wrote in his post titled Back-door nonsense."
+ -
story

Related Stories

[+] Technology: UK Government Wants a Backdoor Into Windows 598 comments
REBloomfield writes "The BBC is reporting that the British Government is working with Microsoft in order to gain backdoor access to hard drives encrypted by the forthcoming Windows Vista file system. Professor Anderson, professor of security engineering at Cambridge University, urged the Government to contact Microsoft over fears that evidence could be lost by suspects claiming to have forgotten their encryption key."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Pavel Stratil (950257) on Saturday March 04 2006, @07:43AM (#14849399) Homepage Journal
    going to die soon? (nothing personal)
    • by bj8rn (583532) on Saturday March 04 2006, @08:14AM (#14849479)
      Let's see. Your comment was modded redundant. This could mean that there's no point in asking this question, as Ferguson is going to die soon. At the same time, however, it could also mean "He's not going to die! Stop asking these stupid questions!" So I really don't know whether he is going to die soon or not. The information you (and the mods) have provided me with is insufficient to determine the this. Sorry.
      • People didn't get it ... he said it would happen ...

        "Over my dead body"

        We're talking Bush administration here. Talk about painting a target on your back! They'd WANT to get rid of anyone who can point a finger. Disposing of the body is no big deal.

        Heck, they don't even have to "terminate with extreme sanction" any more. Just drop a hint to Balmer that he's going to work for google, and let a random chair take him out.

        Speaking of which, if google wanted to throw up a few roadblocks, they could "hint/spread rumours/FUD" that a few critical microsoft developers have accepted/will accept/are in secret talks to accept to jump switch, and watch the body count in Redmond rise like the kill score in Alien 2, from the "pre-emptive kills".

    • by gnarlin (696263) on Saturday March 04 2006, @01:44PM (#14850574) Homepage Journal
      Steve Balmer, in the converence room, with the chair!
  • by aragod (149532) on Saturday March 04 2006, @07:46AM (#14849407) Homepage
    I believe that can be arranged...
  • Right. (Score:5, Insightful)

    by Fantastic Lad (198284) on Saturday March 04 2006, @07:48AM (#14849413)
    Over my dead body,' he wrote in his post titled Back-door nonsense."

    I suspect the NSA, (who I seem to recall left a few stray tags lying around in a previous version of Windows' code), would look at you dead-pan and agree.


    -FL

    • Re:Right. (Score:5, Insightful)

      by hey! (33014) on Saturday March 04 2006, @08:32AM (#14849532) Homepage Journal
      I'd be disappointed if NSA ever resorted to anything so crude. NSA is an agency of savants not a mob of freebooting bucaneers. Assasination is so CIA.

      NSA surely is well aware of the way that trust can, unintentionally, propagate. Everybody trusts something; if somebody doesn't want to cooperate, you obtain his unwitting cooperating by coopting something he trusts. Does he personally supervise the building of every release and patch? Certainly not. He trusts the release process to carry out his intentions. Even if the individuals involved are not cooptable, they trust their compilers to generate object code that is perfectly isomorphic to their source code. Those who do not trust compilers trust their debuggers, disassemblers and operating system utilities.

      Those who do not trust their operating system utilities, and live-boot from randomly chosen operating systems or remove their hard disks and examine them using a hand coded manchine language program on a custom built computer lacking a bios or operating system to be subverted, still trust the network to transfer their object code to the mastering facility, or their optical disk burning software to burn the image accurately. Or they trust the facility to read that data correctly, and to press it as they intended to the distribution media.

      Those who trusted none of this and checked the hard disks by hand coded machine code on a hand wired computer without BIOS or operating system probably deserve assasination, but even so this is hardly necessary, since everyone gets patches over the Internet. A simple black bag job to retrieve the signing keys, and nobody can trust anything anymore.
        • Re:Right. (Score:3, Insightful)

          You just need a separate computer

          What you left out is you need a separate computer that you trust. But how do you know you can trust it?

          Until we evolve to be able to read magnetic domains directly off the platter, everything boils down to believing what your software tells you to be so.
    • Re:Right. (Score:5, Interesting)

      by Haeleth (414428) on Saturday March 04 2006, @08:48AM (#14849574) Journal
      I suspect the NSA, (who I seem to recall left a few stray tags lying around in a previous version of Windows' code)

      Yes and no.

      True, there was a tag in one version of Windows NT 4 that had the name "_NSAKEY". However, it has never been linked to the NSA in any way whatsoever, except by conspiracy theorists.

      You might as well claim that USER32.DLL is proof of a conspiracy to turn American back into a British colony (U.S. obviously stands for United States, and E.R. = Elizabeth Regina = the queen of England! OMG BILL GATES HATES AMERICA!)

      Here [schneier.com] is Bruce Schneier's take on the matter.
      • Details (Score:5, Informative)

        by truthsearch (249536) on Saturday March 04 2006, @09:46AM (#14849759) Homepage Journal
        Here are more details on the NSA keys in Windows [msversus.org]:

        For at least Windows 95 OSR2, 98, NT, and 2000 Microsoft has included a secret cryptographic key owned by the U.S. National Security Agency (NSA). It's most likely that the NSA's key exists within Windows so U.S. government users of Windows can run classified cryptosystems on their computers. But it has been kept secret and it does provide the potential for abuse. "According to Fernandez of Cryptonym, the result of having the secret key inside your Windows operating system 'is that it is tremendously easier for the NSA to load unauthorized security services on all copies of Microsoft Windows, and once these security services are loaded, they can effectively compromise your entire operating system.'" Users of Windows outside the U.S. should be especially concerned that the U.S. government can possibly gain security control over their computers. Users within the U.S. should also be concerned that Microsoft has provided the government with a secret back door that they can exploit. (Campbell, Duncan. "How NSA access was built into Windows [heise.de]." Heise Online 4 Sept 1999)
      • Re:Right. (Score:5, Insightful)

        by Zeinfeld (263942) on Saturday March 04 2006, @08:51AM (#14849586) Homepage
        I think it's much easier for MS to sack him and then change the code.

        I know Niels, he certainly would not have any difficulty getting another job. He was pretty well known before he went to Microsoft. He was the cryptographer who worked on Two-Fish with Bruce Schneier. Microsoft has been hiring pretty much all the top security talent they can over the past five years.

        Cryptography and data security is pretty much a guild craft. If Niels made such a categoric statement and it turned out to be untrue his personal reputation would be severely damaged. Microsoft can't force him to lie for them and since he works in the Netherlands trying to would be most inadvisable.

        • Re:Right. (Score:4, Insightful)

          by stinky wizzleteats (552063) on Saturday March 04 2006, @11:07AM (#14850017) Homepage Journal
          Microsoft can't force him to lie for them and since he works in the Netherlands trying to would be most inadvisable.

          Microsoft is large enough and the codebase complicated enough that such a back door could be added without Niels being aware of it.

          Why do you think the Netherlands are going to affect Microsoft's behavior? They're convicted criminals in the most powerful nation on Earth. I very much doubt that the Netherlands are going to make them clean up their act. Most of the news I see about European software patents seems to support the idea that MS is operating "business as usual" in Europe.
  • by mangus_angus (873781) on Saturday March 04 2006, @07:49AM (#14849416)
    "The suggestion is that we are working with governments to create a back door so that they can always access BitLocker-encrypted data,' Niels Ferguson, a developer and cryptographer at Microsoft, wrote Thursday on a corporate blog. 'Over my dead body,' he wrote in his post titled Back-door nonsense."


    I think we would be reading about his dead body if he came out and admitted that there were backdoors being put into Vista.
      • Why am I replying to an AC? I have no idea, but...

        Do you even know what BitLocker is? It's full drive encryption - basically they encrypt all the data on the hard disk using a key in the TPM.

        It's not about DRM, and can't be used for DRM.

        DRM's about ensuring that you can't INTENTIONALLY give your data to someone else. BitLocker is about ensuring that you can't ACCIDENTALLY give your data to someone else.

        On a BitLocker encrypted system, if you can boot the system, you can access your hard disk without any
  • by replicant108 (690832) on Saturday March 04 2006, @07:54AM (#14849428) Journal
    'Over my dead body,' he wrote

    The problem with closed software is that we have to take his word for it.

    • Also, how are we (not that I'd use this stuff) to know he would know if it were (going to be) the case?
    • there are heaps of people with access to the source code (ok, maybe not full), such as academic institutions, and infamous examples such as MainSoft, who could prove 'em wrong.

      But then we'd have to take the word of some un1337 student haxer at some institution, who just locked down access to their precious copied jewels because some un1337 student haxer at some instituion proved some M$ guy wrong.

      Anyway, aren't there multiple reports of backdoors in PGP from various stages of its life? Of course, since its
      • Re:However (Score:4, Insightful)

        by cortana (588495) <sam AT robots DOT org DOT uk> on Saturday March 04 2006, @09:48AM (#14849766) Homepage
        there are heaps of people with access to the source code (ok, maybe not full), such as academic institutions, and infamous examples such as MainSoft, who could prove 'em wrong.
        How do they know that the code they are provided with matches the code that we all run?
        But then we'd have to take the word of some un1337 student haxer at some institution, who just locked down access to their precious copied jewels because some un1337 student haxer at some instituion proved some M$ guy wrong.
        I can't parse this. But if someone did discover a back door in the code that MS provided them with then surely others would be able to reproduce the flaw?
        Anyway, aren't there multiple reports of backdoors in PGP from various stages of its life?
        Cite please.
    • "Besides, they wouldn't find anybody on this team willing to implement and test the back door."

      (emphasis mine)

      • Re:You're right! (Score:4, Insightful)

        by replicant108 (690832) on Saturday March 04 2006, @09:14AM (#14849651) Journal
        At least with OSS... oh wait... I still have to take a developer's word for it.

        Are you trolling?

        Obviously, if you had the necessary skills you could audit the code yourself.

        Alternatively you could pay someone to audit it for you; or just wait for someone else to blow the whistle.

        The point is that it is much harder to hide malicious code when the source is available.

          • Re:You're right! (Score:5, Insightful)

            by timeOday (582209) on Saturday March 04 2006, @02:01PM (#14850638)
            So, it comes down to a question of who do you trust: college kids who have nothing at stake, or companies that have everything at stake?
            1) the point isn't for every user to check the code, just for a few people or companies to do it and distribute the checksums. It's not that the open source world trusts anybody in particular, but it's impossible to keep a secret once several people with different interests know it.

            2) You're wrong to state that open source is just about college students and not companies. There are many many companies with an interest in Linux being secure.

            3) Why do you assume a company would be trustworthy? Having something to lose makes them vulnerable to government pressure. Look how fast all the search engines caved in to China.

      • Well, you can take this one guy's word for it in the case of Windows.

        Or in the case of OSS you can take the word of the hundreds of developers who want to audit the code themselves (and for something this important, there'll be hundreds of them), where it only takes one person to throw a red flag on bugtraq, and suddenly there's thousands if not tens of thousands of them looking over this code.

        Also you could, if you had an especially vested interest, hire some developers to look over it. Say, perhaps, seve
  • by Anonymous Coward on Saturday March 04 2006, @07:57AM (#14849433)
    - Get me Ferguson... tell him we're going hunting. Yes, hunting. With Cheney.
  • Dead Body? (Score:5, Funny)

    by OverflowingBitBucket (464177) on Saturday March 04 2006, @08:00AM (#14849442) Homepage Journal
    'Over my dead body,' he wrote

    "Your terms are acceptable" reply the NSA.
  • AHA! (Score:5, Insightful)

    by der_joachim (590045) on Saturday March 04 2006, @08:01AM (#14849445)
    So it's a secret backdoor. :-)
  • ... you won't be in the loop if/when it gets compromised.

    A quick look at the "Crypto AG" fiasco makes it plain how very much governments want backdoors. "For decades, the US has routinely intercepted and deciphered top secret encrypted messages of 120 countries." Imagine the power some entity would have if it could peek into any Windows system at will - the temptation must be making their toes curl.

    Whether or not there is a top-level agreement with top-level spooks it is still unlikely that local lawmen will be allowed to know about it. So what exactly IS Microsoft planning to do when they inevitably get a request to "help" with an encrypted drive?
  • by Linegod (9952) <pasnak@warpedsystems. s k .ca> on Saturday March 04 2006, @08:31AM (#14849528) Homepage Journal
    Let the government wait a week for someone to find a backdoor, just like the rest of us....
  • by vandelais (164490) on Saturday March 04 2006, @08:32AM (#14849529)
    strangely silent on the topic of Internet Hearts.

  • by nxsty (942984) on Saturday March 04 2006, @08:41AM (#14849559)
    If there actually where a backdoor in vista, would MS admit it? Probably not.
  • by dprovine (140134) on Saturday March 04 2006, @08:49AM (#14849581)

    Aside from the obvious "what about buffer overruns?" questions, aimed at the usually poor competence Microsoft shows in writing code, there's also "what about cryptographic strength?" question -- maybe the NSA already has a simple and fast way to break whatever encryption BitLocker will end up using.

    And, of course, there may well be several people working at Microsoft who actually work for the NSA or MI-6 or the FSB. (I'd be astonished if there weren't at least a few such people on the Microsoft payroll.) Those people may well do things as described in Reflections on Trusting Trust [acm.org], without letting their superiors know.

      • by dprovine (140134) on Saturday March 04 2006, @09:27AM (#14849694)

        There's no reason you couldn't be for Microsoft and also be for some other entity too. The deception would pretending to be for Microsoft alone. But if you work for the NSA, and you get a job at Microsoft, you may well write good code, and fix security holes, and otherwise help them succeed even while ensuring NSA access to things secured using Microsoft products. Very few things in life are completely either/or.

        If Microsoft caught you and you got sued, the last thing that would happen is the NSA saying a word. I suspect the following, in decreasing order of probability:

        • You make it look like a huge mistake.
        • You tell them you wrote your password down and put it in your wallet, and your wallet was lost and later returned, and you didn't think to update the password.
        • Some heretofore unknown rich uncle dies and leaves you enough money to cover the lawsuit.
        • You die in an auto accident.

        In any case, before placing an asset in such a position, the NSA would probably train such a person with the right lies to tell if something goes wrong. If I were going to do something like that, I'd make up a fake history for the person before Microsoft hired him, and if he got caught then the FBI could investigate and tell Microsoft he was actually a spy for the Mossad. It wasn't even his real name or anything! But for sure the NSA would keep their name out of it. There's a reason they're known as the "No Such Agency".

  • MacOS X, with filefault*, creates a backdoor by means of a certificate. If you then safe the RSA key pair from your Keychain on a separate machine - you yourself or corperate IT can then be easily ensured access in case of some-one beeing hit by a bus; or in case of a total OS crash.
    Dw.

    Ad *) Or manually

    # on a safe machine
    openssl req -new -x509 -out backup.cer -outform DER -nodes
    cp privkey.pem backup.cer /safeplace
    srm privkey.pem
    # copy public cert to laptop or wherever..
    hdiutil create -encryption -type SPARSE -fs HFS+ -volname secure -size 5G -certificate backup.cer sec
  • by Anonymous Coward on Saturday March 04 2006, @09:26AM (#14849687)
    microsoft operating systems begining with windows 95 have never really needed a backdoor, especially since the front door is left wide open.
  • The suggestion is that we are working with governments to create a back door so that they can always access BitLocker-encrypted data,' Niels Ferguson, a developer and cryptographer at Microsoft, wrote Thursday on a corporate blog. 'Over my dead body,' he wrote in his post titled Back-door nonsense.

    But they left out the rest of his quote.

    Niels then put his feet up on the desk and went on to say, "Off the record, you should note my careful use of the word 'always' in the above sentence", he said, with a slight grin on his face. "Context is everything. If I allow them occasional or intermittent access, I'm still being honest, right?" Niels then laughed and pointed to his "Honorary member of the DoD" plaque on his office wall.
  • by smartin (942) on Saturday March 04 2006, @10:14AM (#14849862)
    After all they don't call it windows for nothing.
  • by Fantastic Lad (198284) on Saturday March 04 2006, @10:29AM (#14849899)
    This article makes for interesting reading. . .

    NSA and secret keys added to windows. [heise.de]

    Thanks for the link, truthsearch.


    -FL

  • by ScrewMaster (602015) on Saturday March 04 2006, @10:51AM (#14849961)
    "Your proposal is acceptable."
  • Correction (Score:3, Funny)

    by Opportunist (166417) on Saturday March 04 2006, @11:10AM (#14850022)
    There won't be a backdoor in Vista that they KNOW about. I bet they'll manage to build some in unintentionally.

    I mean, why should it be different in Vista than it was 'til now?
  • by Animats (122034) on Saturday March 04 2006, @03:27PM (#14850858) Homepage
    Intel, HP, Dell, and Toshiba are including the Intelligent Platform Management Interface (IPMI) [intel.com] in many of their machines. IPMI is a "remote administration" tool embedded in the LAN hardware. It looks at UDP packets (on ports 663 and 664) and performs various commands on the target machine, completely independently of the operating system. Here's the IPMI 2.0 rev 1 specification [intel.com], a rather long PDF.

    IPMI is very powerful. An IPMI session starts with a Presence ping Any machine with IPMI hardware should answer a "presence ping" on UDP port 663. This identifies an IPMI-capable machine, and returns some vendor info. Anyone can send this. This should work even if the machine is "turned off", as long as it has standby power and is on a LAN.

    Then, there's a challenge-response authentication sequence. More on this later.

    Once you're in, here are some of the things you can do:

    • Power up the system. Power it down. Force a hard reset. Force a power cycle. Force a phony overtemperature condition (in hopes of getting a clean OS shutdown.).
    • Disable front panel controls (power off, reset, and standby buttons.) Yes, that's really in the protocol. See section 28.6 of the specification. Remote control can also lock out the keyboard and blank the screen.
    • Set system boot options Or, what OS do we want to run today? These include useful tools like "bypass user password".

    There's more. Much more. Basically, you can remotely take over the machine, turn it on, inventory the hardware, load an operating system, boot it up, and talk to it.

    IPMI's back channel can do more than this. With some help from the operating system (and yes, it's supported in Windows) you can do more remote administration functions. This is great for administering your data center remotely. But it has darker implications.

    Supposedly, most machines are shipped with IPMI mostly turned off, unavailable until a program is run on the machine to load in the keys that enable it. Supposedly.

    Thus, all it takes for IPMI to be a "backdoor" is for a set of secret challenge/response keys to be preloaded into the IPMI chip. There's no way to read those keys. Short of taking the chip apart, gate by gate, there's no way to tell if there's a backdoor in there. Or a set of keys might be loaded by the system integrator before shipping the system. You can't tell. So that's where to put a backdoor, where no one can find it.

    There's an open source, OpenIPMI [sourceforge.net], for sending IPMI commands on Sourceforge. Send "Presence pings" to the machines you have and see if they answer.

    • ability to view the supposed source and ability to put said source to use are required. If you can't verify that the source you're looking at is the source used in the binaries you're using, there's zero point. Chances of MS releasing enough source to be able to rebuild aspects of windows- most likely a few steps shy of zero, at least for now.
    • Re:Prove it. (Score:4, Insightful)

      by ROOK*CA (703602) on Saturday March 04 2006, @07:59AM (#14849441)
      We have no reason to believe this claim -- doubly so given that Microsoft has lied repeatedly in the past.

      I'd be willing to bet that even Microsoft would not be willing to go so far as to create intentional "backdoors" in their encryption to facilitate government (Law Enforcement) access. First off I don't think the government (at least those in the UK and the US) have the power to legally force them into doing it, and secondly if they did it voluntarily one would think the public outcry would be deafening and severly damaging to Microsoft (and it seems that "keeping it quiet" would be nearly impossible).

      I generally don't trust the government as far as I can throw them, and I don't trust Microsoft much farther than that, but I think the suggestion that they are colluding in something as nefarious as this is a bit in the Tin Foil Hat realm.

      Besides how would they "prove" they aren't doing it? release the source? as if ..... :)
      • Re:Prove it. (Score:4, Insightful)

        by sqlrob (173498) on Saturday March 04 2006, @10:07AM (#14849838)
        First off I don't think the government (at least those in the UK and the US) have the power to legally force them into doing it

        Nice government contract you have there. Shame if anything were to happen to it.
      • The problem is transparency.
        Would you stake your business or for that matter, you life (as is the case in some regions of the world) on this assumption? Since there is no transparency in Microsoft products, you simply have to take their word for it.

        I thought the golden rule of security was that any viable security mechanism should tolerate public scrutiny. Knowing how the software works should not work against the devised scheme itself.

    • He's crazy if thinks big corporations would even think twice of doing something over the dead body of one of their workers.

      Corporations might think twice, but governments wouldn't.

    • Gnupg is open source, so you can verify there are no backdoors

      Yes, absolutely. If you're going to use encryption semi-seriously or even professionally, you have no choice but to use open source crypto libraries and apps!

      But source code alone is no panacea here: you (or anyone skilled enough -- a.k.a. the community) could discover obvious backdoors, but what about backdoors in some crypto algorithms themselves? Having the source code for this won't help you much. Nothing could really prevent the NSA [nsa.gov] fr