Slashdot Mirror


MS: Windows Phone 8 Wi-Fi Vulnerable, Cannot Be Patched

Freshly Exhumed writes "Microsoft advises that a cryptographic problem in the PEAP-MS-CHAPv2 protocol used in Windows Phone 8 to provide WPA2 authentication allows a victim's encrypted domain credentials to be collected by an attacker posing as a typical WiFi access point. Redmond further states that this problem cannot be patched, although a set of manually entered configuration changes involving root certificates on all WP8 phones and on WiFi access points will apparently address the issue. WP7.8 phones are likewise vulnerable."

146 comments

  1. Why can't it be patched? by metrix007 · · Score: 5, Insightful

    If it can be fixed through manual configuration changes, why can't a patch make those same configuration changes?

    --
    If you ignore ACs because they are anonymous - you're an idiot.
    1. Re:Why can't it be patched? by i+kan+reed · · Score: 5, Funny

      Because the NSA won't let them?

    2. Re:Why can't it be patched? by Anonymous Coward · · Score: 5, Informative

      because the root certificate being installed is for the internal domain and Microsoft doesn't have that certificate.

      please note: this is only for PEAP using domain credentials. not standard WPA2-PSK that just about everyone uses.

    3. Re:Why can't it be patched? by Anonymous Coward · · Score: 4, Insightful

      watch as your actual-factual answer languishes at 0 while the "funny" comment about the NSA gets +5 Insightful.

    4. Re:Why can't it be patched? by aaron44126 · · Score: 4, Informative

      It says in the article that configuration changes must be made on the WiFi access points as well.

    5. Re: Why can't it be patched? by Anonymous Coward · · Score: 0

      Most people expect that any "manual configuration change" can be scripted, creating an automatic patch. It still doesn't make sense.

    6. Re: Why can't it be patched? by metrix007 · · Score: 1

      Really, why not? Configuration changes are stored somewhere. Have the patch diff the changes...

      In this case where you need a local certificate it makes sense. Most of the time...

      --
      If you ignore ACs because they are anonymous - you're an idiot.
    7. Re:Why can't it be patched? by fuzzyfuzzyfungus · · Score: 4, Informative

      If it can be fixed through manual configuration changes, why can't a patch make those same configuration changes?

      The configuration change is enabling server certificate validation. If the network is set up for this, all is well: just like SSL, the server demanding the credentials from the client connecting to the network has a certificate, which the client can verify before attempting to authenticate. Spoofing becomes effectively impossible without access to a suitably signed cert.

      However, if the authentication server is not set up to use a certificate, or is set up to use a certificate not signed by one of the CAs in the client's list of trusted authorities, enabling server certificate validation will cause the client to freak out and never attempt to authenticate (since validation will, correctly, fail.)

    8. Re:Why can't it be patched? by wmac1 · · Score: 1

      Perhaps it means to change the configuration on "genuine access points" in a way that clients are not required to set vulnerable settings on their phone.

    9. Re:Why can't it be patched? by Anonymous Coward · · Score: 3, Interesting

      because the root certificate being installed is for the internal domain and Microsoft doesn't have that certificate.

      please note: this is only for PEAP using domain credentials. not standard WPA2-PSK that just about everyone uses.

      The scary thing (if i read this correctly) is that someone could theoretically sit outside a business where a lot of WP8 users are, listen for a while to snoop the wireless details (SSID, AP's mac, whatever they want) and then set up a fake hotspot in the parking lot. As phones leave the building's wifi perimeter, they will try to re-auth to the fake hotspot and give away their user's credentials. The user can then turn their wifi gear toward the building, and log in as an insider with probably tons-o-access to the internal network and the crown jewels.

      Who cares if it's only a few businesses or that "most people" dont bother with it, the potential for targeted abuse is so huge that I don't see any sane enterprise keeping this turned on. They are better off just handing out "secret" WPA keys to their users than bothering with auth that basically ensures they are vulnerable.

    10. Re:Why can't it be patched? by robmv · · Score: 1

      Or treat wireless like an internet connection, require VPN access over it

    11. Re:Why can't it be patched? by Strider- · · Score: 1

      The configuration change is enabling server certificate validation. If the network is set up for this, all is well: just like SSL, the server demanding the credentials from the client connecting to the network has a certificate, which the client can verify before attempting to authenticate. Spoofing becomes effectively impossible without access to a suitably signed cert.

      The fundamental problem you run into however, is that at the point where you need to verify the certificate you don't yet have a network connection. In a PEAP environment, the certificate is presented to the client before layer 3 connectivity has been established. The client obtains the certificate, sees that it has been signed by a valid CA, but it can not actually verify that the certificate is being presented by the right server since, well, there's no network connection yet. It's really one of those chicken and egg problems, there's no good way to resolve it.

      The reality is that in most cases, it should pop a warning giving certificate details (along with the fact that it has been signed by a trusted CA), and asking the user if they would like to proceed (and then saving that approval if desired).

      --
      ...si hoc legere nimium eruditionis habes...
    12. Re:Why can't it be patched? by ISoldat53 · · Score: 1

      Maybe they can find some programers somewhere that can re-write it.

    13. Re:Why can't it be patched? by Anonymous Coward · · Score: 1

      Or treat wireless like an internet connection, require VPN access over it

      Too many people (mostly in the corporate world) believe that "defense in depth" means multiple layers of the highest encryption possible, and users who complain about having to authenticate 9 times just to check their email won out and required stored/cached single sign on so that you can breeze through all 9 layers as soon as you unlock your laptop with your domain password. It turns out that all that authentication shot them in the foot. Plus, if any ol person can belly up to your corporate WiFi, that makes you the same as Starbucks amiright? We can't have lazy, coffee swilling jerks laying around the office all day can we?

    14. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      >MS: Windows Phone 8 Wi-Fi Vulnerable, Cannot Be Patched

      A 10-lb sledgehammer will do the job nicely..

    15. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      The scary thing (if i read this correctly) is that someone could theoretically sit outside a business where a lot of WP8 users are

      You mean just outside Redmond's WP8 development office?

      Maybe this whole vulnerability report should have just been an internal memo.

    16. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      The client would have the DNS name so it could compare the CN though wouldn't it?

      Or is the problem an attacker uses your SSID and presents their own valid trusted CA signed certificate for their own auth server? So when setting up your client you didn't specify the actual auth server DNS name so it can't compare the CN in the cert?

      Perhaps the solution would be to have the SSID be the CN used in the certificate. So I would have to have a certificate with a CN of "corporate-wireless.example.com" and a SSID of the same name.

    17. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      alot of wp8 users? Did I read that correctly? naw, I've only seen one (1) WP in a year, thats it. all others are iphone or samsung phones...

    18. Re:Why can't it be patched? by DrXym · · Score: 3, Insightful

      Sounds like Microsoft has most to fear on their own campuses since I doubt that there are many other businesses with a high enough concentration of vulnerable phones who would be worth the risk.

    19. Re:Why can't it be patched? by r1348 · · Score: 2, Interesting

      Luckily, there's not such thing as a "business where a lot of WP8 users are", except maybe for Microsoft itself, but I wouldn't bet my life on it...

    20. Re:Why can't it be patched? by sjames · · Score: 1

      Because it only works by pre-sharing a generated certificate between the AP and the client. MS can't make that happen with a patch.

    21. Re:Why can't it be patched? by WaffleMonster · · Score: 1

      The fundamental problem you run into however, is that at the point where you need to verify the certificate you don't yet have a network connection. In a PEAP environment, the certificate is presented to the client before layer 3 connectivity has been established. The client obtains the certificate, sees that it has been signed by a valid CA, but it can not actually verify that the certificate is being presented by the right server since, well, there's no network connection yet. It's really one of those chicken and egg problems, there's no good way to resolve it.

      You resolve it the way all browsers and sane operating systems resolve it. You load/keep a list of trusted root certificates against which the device can validate the server certificate by itself out of band of the wifi communication channel.

      There are even extensions to TLS where OSCP can be performed over TLS such that revocation checking does not require network access.

    22. Re:Why can't it be patched? by sexconker · · Score: 1

      because the root certificate being installed is for the internal domain and Microsoft doesn't have that certificate.

      please note: this is only for PEAP using domain credentials. not standard WPA2-PSK that just about everyone uses.

      The scary thing (if i read this correctly) is that someone could theoretically sit outside a business where a lot of WP8 users are, listen for a while to snoop the wireless details (SSID, AP's mac, whatever they want) and then set up a fake hotspot in the parking lot. As phones leave the building's wifi perimeter, they will try to re-auth to the fake hotspot and give away their user's credentials. The user can then turn their wifi gear toward the building, and log in as an insider with probably tons-o-access to the internal network and the crown jewels.

      Who cares if it's only a few businesses or that "most people" dont bother with it, the potential for targeted abuse is so huge that I don't see any sane enterprise keeping this turned on. They are better off just handing out "secret" WPA keys to their users than bothering with auth that basically ensures they are vulnerable.

      The only thing you get is the encrypted credentials. Is PEAP-MS-CHAP v2 vulnerable to any practical attacks?

    23. Re:Why can't it be patched? by sexconker · · Score: 1

      Or treat wireless like an internet connection, require VPN access over it

      How would a VPN help? This vulnerability affects the authentication with the access point. If you authenticate, get an IP, and try to open a VPN connection, it's too late.

    24. Re:Why can't it be patched? by robmv · · Score: 1

      Because you can't access the company network without access to the VPN. Serious enterprise networks do not trust only the wireless encryption, simple as that

    25. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      Where are you going to find a place with a lot of WP8 users? Redmond?

    26. Re:Why can't it be patched? by WaffleMonster · · Score: 2

      The only thing you get is the encrypted credentials. Is PEAP-MS-CHAP v2 vulnerable to any practical attacks?

      If the TLS certificate is not validated all protections of TLS are null and void as it can be MITMd. In other words PEAP-MS-CHAPv2 becomes just MS-CHAPv2.

      Cracking MS-CHAPv2 is trivial...
      https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/

      Not just practical its EASY.

    27. Re: Why can't it be patched? by buchanmilne · · Score: 1

      EAP is performed when the EAP client is trying to establish layer 2 connectivity, before IP address aasignment can happed. Since there is no IP, there is no way to do a DNS lookup, and nothing to validate the subject cn against.

      If certificate validation against CA certificates is disabled by default ( which is the case on Android as well), certificate validation collapses to whether the cert has expired.

      I am only aware of 2 mobile platforms that do this better, iOS which prompts on a new EAP certificate, and Symbian, which didn't allow connecting to EAP networks with certs not signed by a trusted cert.

        The recent 'it just works' race to the least secure is not going to end well.

    28. Re:Why can't it be patched? by sexconker · · Score: 1

      Because you can't access the company network without access to the VPN. Serious enterprise networks do not trust only the wireless encryption, simple as that

      All of this happens before you even get an IP address.

      I'm going to repeat myself:

      How would a VPN help? This vulnerability affects the authentication with the access point. If you authenticate, get an IP, and try to open a VPN connection, it's too late.

    29. Re:Why can't it be patched? by d34thm0nk3y · · Score: 1

      Luckily, all of the WP eight users on the planet are under this large radio-proof dome currently so everything should be OK.

    30. Re: Why can't it be patched? by bleh-of-the-huns · · Score: 1

      And how many users just click accept to those types of prompts.

      Funny enough, at Defcon, a similar attack was performed that affected IOS and Android Devices, as well as OSX, MS products were not affected.

      Reading the articles leads me to believe this is the same attack. The attack occurs during PEAP Stage 2. yes a prompt was thrown for IOS, but not for Android, which just accepted the cert. This attack however had nothing to do with a cryptographic weakness, rather a weakness in IOS/OSX/Android that responded to a forged Challange message stating that the password was correct (when in reality no password was validated, and the client just took the radius servers answer as legit), allowing the clients to connect to the wireless network. At that point you force the user through a captive portal and ask the user to authenticate again, most users will just put their username and password in, which you are capturing at the portal.

       

      --
      I came, I conquered, I coredumped
    31. Re: Why can't it be patched? by Anonymous Coward · · Score: 0

      PEAP - which involves using an SSL channel to a RADIUS server for authentication and the negotiation of a WPA2 key with a limited lifespan, is almost the definition of a VPN.

      Microsoft have screwed the pooch with this. A perfectly good, secure protocol mis-implemented

    32. Re: Why can't it be patched? by gl4ss · · Score: 1

      Most people expect that any "manual configuration change" can be scripted, creating an automatic patch. It still doesn't make sense.

      yeah but that doesn't make as good headlines.

      fwiw wp8 is supposed to get vpn.. in 2014- for enterprise! probably most wp8's are used with psk networks anyways, since if you're serious about making a secure route you sure as fuck aren't deploying them to troops, so can't imagine that many IT offices bothering with anything fancier into them. you have to treat sw you install on them like they're going to be used from public wifis or operators without vpn anyways so why bother?

      --
      world was created 5 seconds before this post as it is.
    33. Re:Why can't it be patched? by marcosdumay · · Score: 1

      Maybe I shoud repeat the GP agan.

      No, a VPN by itself does not matter, what matters is that you put no resource besides internet accessible to whoever just authenticated into your wireless network. Anything that matters is inside a firewall, that people can traverse using a VPN.

      It does not make the attack fail, it just protects everything that is important.

      (And about having to authenticate at the access point, and the VPN, well, both are automatic, it shouldn't be a nuissance.)

    34. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      I was gonna say, people actually *buy* windows phones?

    35. Re:Why can't it be patched? by LBt1st · · Score: 1

      "a business where a lot of WP8 users are"

      Good luck finding one of those!

    36. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      or vagina

    37. Re:Why can't it be patched? by cbhacking · · Score: 1

      Note: "give away their credentials" is a little bit strong. Using custom hardware, CloudCracker can break MS-CHAPv2 in about a day at a reasonable cost, but it's still not feasible to do a massive attack of capturing everybody's creds unless you've got a fair bit of time and money to burn.

      On the other hand, if you capture the *right* person's credentials, then that's all you need anyhow.

      --
      There's no place I could be, since I've found Serenity...
    38. Re: Why can't it be patched? by WaffleMonster · · Score: 1

      EAP is performed when the EAP client is trying to establish layer 2 connectivity, before IP address aasignment can happed. Since there is no IP, there is no way to do a DNS lookup, and nothing to validate the subject cn against.

      The CN in PEAP is the whatever the PEAP server says it is. Hint it is not a DNS name or a SID or anything globally recognizable.

      The recent 'it just works' race to the least secure is not going to end well.

      Users and operators should not have to go thru all this trouble deploying PKI if they don't want to or jumping thru difficult hoops simply because protocol designers are stuck in the 80's.

      We can get a usable solution today using EAP-TLS method and simply negotiating TLS-SRP to verify mututal password knowledge and establish session encryption key rather than or in addition to mutual certificate authentication. More secure, PKI optional (identity protection). Best of all there is no new RFC/specification to invent and only glue code to write.

      We can get an extremely usable solution with only minor RFC work to communicate password format/salt or challenges such that stored non-reversable passwords could also be authenticated using the zero knowledge channel.

      I'm tired of all of the foolishness where it is not the user doing the wrong thing, it is not even the operator it is the vendors and the standards people who continue to tolerate unusable and or broken shit. PEAP as designed is simply too hard to deploy securely without an automated configuration push. It does not have to be this way.

    39. Re:Why can't it be patched? by Bert64 · · Score: 1

      And if both the vpn and the wifi (and devices beyond the vpn too) use the same authentication?
      Many organisations are set up this way, using windows domain logins for everything, so if you own one layer you have them all.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    40. Re:Why can't it be patched? by Anonymous Coward · · Score: 1

      looks like I was wrong.

    41. Re:Why can't it be patched? by sexconker · · Score: 2

      Maybe I shoud repeat the GP agan.

      No, a VPN by itself does not matter, what matters is that you put no resource besides internet accessible to whoever just authenticated into your wireless network. Anything that matters is inside a firewall, that people can traverse using a VPN.

      It does not make the attack fail, it just protects everything that is important.

      (And about having to authenticate at the access point, and the VPN, well, both are automatic, it shouldn't be a nuissance.)

      The credentials for the WiFi AP and the VPN are likely the same (domain credentials).

      Even if they're not, guess what the client does after hitting up that spoofed WiFi AP?
      Hint: It tries to establish a VPN connection.

      Even if it is smart enough to require some authentication before trusting the VPN (why would it when it's not smart enough to do that for the AP?), you can see everything the victim sends out (thinking it's on a legit AP), and you can join the legit AP and poke around to get the VPN's details.

      Even if the client and VPN negotiation is resilient to replay attacks, you're still in a position to MITM the whole game live once the victim connects to your AP. You're on the legit AP, the victim is on the spoofed one, you win.

      A VPN does not solve shit in this scenario.

    42. Re: Why can't it be patched? by Cramer · · Score: 1

      ... and nothing to validate the subject cn against.

      Sure there is... the SSID, the BSSID (AP MAC), the enterprise domain to which you're trying to join, etc. But, yes, it's all moot if the OS presents the user what a "whatever, just do it already" button.

    43. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      where a lot of WP8 users are,

      As if that would ever happen... ;)

    44. Re:Why can't it be patched? by Anonymous Coward · · Score: 0

      Not all of them, just most. We just tested this out at work and it worked brilliantly. Needless to say, Windows Phones are now officially banned from my workplace.

    45. Re: Why can't it be patched? by niftymitch · · Score: 1

      Scripting and patching need to operate at an "interesting" security level. What does this tell us about the system security?

      There is no way to validate the script thus there is no way to patch it.

      Perhaps like an Android update an entire new system image could do the job but that is not a patch.

      File this under the definition of "is" (thanks Bill).

      --
      Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
    46. Re: Why can't it be patched? by Anonymous Coward · · Score: 0

      Sounds like you only use Microsoft products. I'm a Large Enterprise Infrastructure Architect with the only surviving American IT firm with ~500k employees and I'm telling you that serious enterprises don't use the same credentials for VPN access. I often get RSA key fobs at new sites, and my employer uses AT&T. Your position is accurate for small and mid sized companies. Not large corporate entities.

  2. oops... by buzzsawddog · · Score: 1

    So that's why all of the wifi pineapples sold out at DEF CON...

    1. Re:oops... by binarylarry · · Score: 4, Funny

      Nah, whats the fun in hacking all 5 people who've bought Windows Phones?

      Apple Newton probably has bigger marketshare right now.

      --
      Mod me down, my New Earth Global Warmingist friends!
    2. Re:oops... by gstoddart · · Score: 1

      Nah, whats the fun in hacking all 5 people who've bought Windows Phones?

      Depends, if they're over-represented in corporate environments, they could be very attractive things with a known exploit.

      --
      Lost at C:>. Found at C.
  3. Oh please by Anonymous Coward · · Score: 5, Informative

    Every phone which implements CHAPv2 is vulnerable, because that's a broken algorithm. You can't patch it, because then it wouldn't be that algorithm anymore and stop working with other implementations of the algorithm. The right thing to do is to encapsulate it in a securely encrypted tunnel, but to have that, you have to check the certificates. If you don't secure the tunnel, an attacker can MITM you and crack the CHAPv2 inside. Not properly securing tunnels is a problem everywhere.

    1. Re:Oh please by Anonymous Coward · · Score: 0

      Dead on. Mod this up!

    2. Re:Oh please by tysonedwards · · Score: 4, Funny

      The fact that we have such lax tunnel security is a travesty.
      I propose that we immediately bring in the TSA to man the entrance to every tunnel, for our children!

      --
      Thirty four characters live here.
    3. Re:Oh please by Anonymous Coward · · Score: 1

      Quiet you, we're trying to bash Microsoft here.

      Knock Knock.

      Who's there?

      Windows Phone 8.

      Windows Phone 8 who?

      Exactly.

    4. Re:Oh please by Anonymous Coward · · Score: 0

      So every phone is vulnerable, except the ones that aren't. Got it.

    5. Re:Oh please by jrumney · · Score: 4, Informative

      Every phone which implements CHAPv2 is vulnerable

      Other phones don't automatically give out your corporate domain login details using it though.

    6. Re:Oh please by rodrigoandrade · · Score: 2

      But lambasting Microsoft and Windows phones is a lot more entertaining than some boring technical and cohesive explanation.

    7. Re:Oh please by Anonymous Coward · · Score: 0

      Mod parent up! This is the big deal!

    8. Re:Oh please by Notabadguy · · Score: 1

      I think Al Gore has a lock box full of tubes that has room to store this. Lock boxes are safer than tunnels.

    9. Re:Oh please by 93+Escort+Wagon · · Score: 4, Informative

      Well, to be fair to the blasters and lambasters:

      - This is a protocol developed by Microsoft, and it's fundamentally broken
      - Knowing it's fundamentally broken, Microsoft still included it on their phone and enabled its use by default

      --
      #DeleteChrome
    10. Re:Oh please by Anonymous Coward · · Score: 0

      It's not enabled by default. You need a receiving end / access point for it. =P

    11. Re:Oh please by Anonymous Coward · · Score: 0

      Quiet you, we're trying to bash Microsoft here. Knock Knock. Who's there? Windows Phone 8. Windows Phone 8 who? Exactly.

      Congratulations, you are on the jury!

    12. Re:Oh please by am+2k · · Score: 1

      Just like PPTP! I think I can see a pattern there.

    13. Re:Oh please by sexconker · · Score: 1

      On a scale of WEP to AES, how broken is PEAP-MS-CHAP v2?

    14. Re: Oh please by buchanmilne · · Score: 1

      And all platforms that support EAP support PEAP with MSCHAPv2.

      Any network that does PEAP with MSCHAPv2 using credentials thay are usee dor any other service is vulnerable, unless the clients will require certificates signed by a trusted CS cert.

      Android authenticating via FreeRADIUS to Samba password hashes to allow access to an AP running OpenWRY would be vulnerable by default.

    15. Re:Oh please by Anonymous Coward · · Score: 0

      Not at all if you do the first part of Protected Extensible Authentication Protocol right, which requires certificate verification. Not quite WEP-broken otherwise, as it takes more time and resources, but it is definitely broken.

    16. Re:Oh please by cbhacking · · Score: 2

      Assuming you don't use certificate validation for the SSL tunnel over which the MS-CHAPv2 communication occurs (which requires configuring each access point manually), then you can spoof the SSL connection (trivially), at which point it's just down to MS-CHAPv2. This algorithm boils down to three DES operations - not 3DES (which has an effective key strength of 112 bits, lower than the weakest AES key but still practically impossible to crack) but three independent and parallelizable DES operations. Each one has a key strength of 56 bits, so the total is (2^56)*3 possibilities, or about 57.585 bits of entropy. Look up CloudCracker; it can break MS-CHAPv2 via brute force in about a day by using massively parallel attacks on DES, and the keyspace just isn't big enough.

      --
      There's no place I could be, since I've found Serenity...
    17. Re:Oh please by Anonymous Coward · · Score: 0

      Last night I manned the entrance to your mom's tunnel.

      It remains to be seen if children will be involved.

    18. Re:Oh please by Anonymous Coward · · Score: 0

      Yep same NetBios name spoofing you can do to any Windows network. Takes less than 30 mins to own a domain.

    19. Re: Oh please by Anonymous Coward · · Score: 0

      Whoa, looks like you had a mini stroke in the middle of that post. Might want to get that checked out.

  4. Wait by jayhawk88 · · Score: 3, Insightful

    What's so special about Windows Phone 8/7.8 with regards to this issue? If you're not requiring a cert validating the identity of your radius server/access point/whatever, ANY device is going to be vulnerable to a spoofed SSID kind of attack, right?

    1. Re:Wait by wmac1 · · Score: 2

      Don't take the fun out of it please :) !

  5. FUD? by blcamp · · Score: 0

    This is quite the "Oops" on the part of MSFT which, even if this is nothing more than anti-MS FUD, can ill-afford this kind of bad press with a platform which has less than 4% of market share.

    --
    The problem with socialism is that they always run out of other people's money. - Margaret Thatcher
    1. Re:FUD? by ackthpt · · Score: 1

      This is quite the "Oops" on the part of MSFT which, even if this is nothing more than anti-MS FUD, can ill-afford this kind of bad press with a platform which has less than 4% of market share.

      Probably the result of an office memo, which came down from the top, worded something like this: More animations, more inexplicable navigation, don't worry about security or adhering to the APIs, we can fix that later .. or not.

      --

      A feeling of having made the same mistake before: Deja Foobar
    2. Re:FUD? by 1s44c · · Score: 1

      This is quite the "Oops" on the part of MSFT which, even if this is nothing more than anti-MS FUD, can ill-afford this kind of bad press with a platform which has less than 4% of market share.

      The Microsoft mantra has always been that they only get cracked because they have most of the market share. Here they have 4% of the market share and they are still getting cracked.

      Maybe the things MS make are just no good?

    3. Re:FUD? by Anonymous Coward · · Score: 0

      The handshaking here (CHAP) is not just present in WP7/8 devices, but practically all Windows versions.

      Biggest difference is that it's usually used over wire in a corporate environment.

  6. Rather than issue a security advisory.. by Trailer+Trash · · Score: 4, Funny

    They ought to just call the guy who bought one and explain it to him.

    1. Re:Rather than issue a security advisory.. by adycarter · · Score: 1

      They just did, and It doesn't bother me.

      Panic over everyone!

      --
      Witty Comment Here
  7. Never met anyone who had a windows 8 phone by jfdavis668 · · Score: 1, Flamebait

    Never met a Zune user, either.

    1. Re:Never met anyone who had a windows 8 phone by DogDude · · Score: 2

      Hello! Nice to meet you. My girlfriend has one, too.

      --
      I don't respond to AC's.
    2. Re:Never met anyone who had a windows 8 phone by Horshu · · Score: 1

      Another variant of the old "I don't know anyone who voted for Nixon" line.

    3. Re:Never met anyone who had a windows 8 phone by Anonymous Coward · · Score: 0

      God, why would anyone have a Zune, the damn bloatware to use it alone would scare me off... I do however, quite like my Lumia 928.

  8. The Good News, by Anonymous Coward · · Score: 0

    is that no one is using a Windows Phone.

  9. Re:Can't you protect it with HOST files? by Anonymous Coward · · Score: 5, Interesting
    Robert Scoble is a former technology evangelist at Microsoft who decided to leave the company in June 2006 to become the vice president of Podtech.net. At that time, it was believed that Scoble had resigned because he was looking for a higher salary elsewhere.

    Innovation is the key, he said, pointing out that Microsoft had completely failed to get itself noticed in the tablet and smartphone markets.

    "Since I've left [Microsoft], what have they done that's interesting? Microsoft [Xbox] Kinect is the only thing I can think of and for a company that has 90,000 employees, to have only one product that you can point to that's innovative, that's pretty disappointing I think,” he said according to The Age.

    "Compare that to Google, which is showing you self-driving cars, Google Glass and a phone that you can talk to, the Moto X, and on and on — automatic picture improvements on Google+ — It's a much more innovative company that is driving the future harder and faster."

    One of the reasons why Microsoft fails to innovate right now is the current leadership, Scoble explained, revealing that Steve Ballmer is actually trying to make more money by rolling out innovative technologies.

    “I just don't believe Steve Ballmer really likes the future. When I interviewed [him] he said innovation is something cool that makes a lot of money. And that's absolutely not true. [Google Glass] might never make a dollar but it's new, it's interesting [and] it causes conversations. If you're an innovator, you push the future ahead. You don't care whether it necessarily makes a dollar,” he continued.

    http://news.softpedia.com/news/Former-Employee-Says-That-Microsoft-Is-Not-Longer-Cool-Blames-Steve-Ballmer-373770.shtml

  10. Parent must be spam by jabberw0k · · Score: 2, Informative

    Real Slashdot users don't have girlfriends (or boyfriends for that matter).

    1. Re:Parent must be spam by Anonymous Coward · · Score: 0

      Some of us have wives, so we're still not getting laid. Six of one, half-dozen of the other...

    2. Re:Parent must be spam by 1s44c · · Score: 1

      Six wives and a half-dozen girlfriends? You must be tired!

    3. Re:Parent must be spam by MiniMike · · Score: 1

      Six wives and a half-dozen girlfriends?

      No, he just has polydactyly.

      You must be tired!

      He probably is, but TMI.

  11. How do you get on on the day it won't turn on? by dbIII · · Score: 1, Interesting

    So it's 1984, and I'm in a high school math class where I have to write a very simple calendar program on a Sperry computer, never knowing that years later the guy that did the same thing on the Zune would have got a zero and be held up as an epic failure to programmers today. How the fuck do you forget leap years? How the fuck do you mess things up so badly that your device will not even turn on on some days due to that calendar bug? How bad is the quality control to miss such a thing that was a high school level exercise decades ago?

    1. Re:How do you get on on the day it won't turn on? by wonkey_monkey · · Score: 1

      So it's 1984, and I'm in a high school math class where I have to write a very simple calendar program on a Sperry computer

      And you've inadvertently created the trans-temporal internet protocol? Kudos!

      --
      systemd is Roko's Basilisk.
    2. Re:How do you get on on the day it won't turn on? by gstoddart · · Score: 1

      How the fuck do you forget leap years?

      Gross incompetence, and a total lack of awareness of the Gergorian calendar.

      --
      Lost at C:>. Found at C.
    3. Re:How do you get on on the day it won't turn on? by Anonymous Coward · · Score: 0

      A 24-hr deadline?

    4. Re:How do you get on on the day it won't turn on? by oji-sama · · Score: 2

      How the fuck do you forget leap years?

      The same way you forget the month December from calendar I guess. It is strange, though.

      --
      It is what it is.
    5. Re:How do you get on on the day it won't turn on? by Teun · · Score: 1
      Because the guy was cheap?
      And/or he grew up with and is accustomed to a Moon cycle based calender?

      Still doesn't explain how it (in a market leading company) got past peer review...

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    6. Re:How do you get on on the day it won't turn on? by cbhacking · · Score: 2

      First point: it didn't "forget" leap years, there was just a logic error in the special-case code that handled them. Forgot to test, perhaps, but not actually forgot.
      Second point: Microsoft didn't write that code. It was part of the clock module that was built into the hardware that they used. Again, perhaps they should have tested it themselves, but the clock module's code quality itself wasn't Microsoft's fault.

      --
      There's no place I could be, since I've found Serenity...
    7. Re:How do you get on on the day it won't turn on? by dbIII · · Score: 1

      Thanks for demonstrating to the kids of today the "this is your brain on drugs" thing from way back then.

    8. Re:How do you get on on the day it won't turn on? by dbIII · · Score: 1

      Microsoft didn't write that code

      Their product, their responsibility no matter who they contracted it out to, thus it was Microsoft's fault.

  12. Use windows by 1s44c · · Score: 1

    Every year there is a story on slashdot where the perfect response is 'Use Windows, get screwed.' It seems things have not changed much in the last 15 years.

    1. Re:Use windows by QilessQi · · Score: 2

      Some folks argue that the stories (or, rather, the presentation and discussion of them) are unfairly slanted against Microsoft. For me, it comes down to this:

      When a company has a warchest in excess of 500 billion US dollars, as well as immense market penetration in a variety of domains -- desktop operating systems, web browser, word processing software, spreadsheet software, etc. -- it is expected to have its act together.

    2. Re:Use windows by rullywowr · · Score: 2

      Some folks argue that the stories (or, rather, the presentation and discussion of them) are unfairly slanted against Microsoft. For me, it comes down to this:

      When a company has a warchest in excess of 500 billion US dollars, as well as immense market penetration in a variety of domains -- desktop operating systems, web browser, word processing software, spreadsheet software, etc. -- it is expected to have its act together.

      (CompanyX AND 500 billion dollars) != "its act together"

      For example:

      Windows ME

      Windows Vista

      Zune

      Games for Windows Live/Steam DRM

      Surface RT

      Xbox One and their DRM strategy (until it was revoked)

    3. Re:Use windows by QilessQi · · Score: 2

      Oh, I agree ... Microsoft doesn't have its act together. My point was that given its war chest and the demands of its current user base, it should. There's simply no excuse.

      I think that's why some of us on /. come down harder on Microsoft then on smaller companies. Sure, all software shops produce buggy code from time to time. And many vendors ship products that they hope will be game changers but that, ultimately, people aren't interested in. But most of these companies don't have a zillion dollars to spend on usability studies, development, and testing.

    4. Re:Use windows by theskipper · · Score: 2

      Just a nitpick, you're a wee bit off there with $500B. Actual cash on balance sheet is $76B. Market cap is approximately $273B.

    5. Re:Use windows by QilessQi · · Score: 2

      My bad: the Forbes article I grabbed it from is a year old:

      http://www.forbes.com/sites/afontevecchia/2012/01/20/dont-underestimate-microsoft-but-watch-out-for-margin-compression/

      "Bing is another powerful tool Microsoft can juice. Despite “continuing to rack up operating losses,” Bing is “inching up the search ladder,” according to Caris, growing revenues 13% to $784 million. Microsoft is sitting on a massive $512.7 billion war chest with which it supports acquisitions and businesses like Bing, which are strategic in tapping into Google and Yahoo’s all-important search revenues. According to comScore, Bing’s market share is now up to 15.1% (as of December), compared to 14.5% for Yahoo and 66% for Google."

    6. Re:Use windows by Anonymous Coward · · Score: 0

      Every year? I've been here for at least a decade, and it's always been on more of a monthly or even weekly basis.

    7. Re:Use windows by theskipper · · Score: 2

      Yes, definitely a typo on their part. Decimal point should be shifted one place to the left.

  13. Good foundations are important by Anonymous Coward · · Score: 0

    Nice to see WP8 shares the same good foundations as any M$ product. (Captcha: wretches)

  14. Product death ... by gstoddart · · Score: 0

    Redmond further states that this problem cannot be patched

    One more nail in the coffin of a product which has been dying since it was released.

    Come on guys, just how bad of a job are you doing these days?

    --
    Lost at C:>. Found at C.
    1. Re:Product death ... by Anonymous Coward · · Score: 0

      .....You do realize Windows Phone market share is growing faster than any other currently? It's still small, but it's growing fairly rapidly. Jesus fanboys are terrible.

    2. Re:Product death ... by Windowser · · Score: 2

      .....You do realize Windows Phone market share is growing faster than any other currently?

      Statistics are like bikinis. What they reveal is suggestive, but what they hide is vital.
      Take this simple example :
      Company A as only 1 user of their phone. Then another person buy the phone. Now there is only two user, but they just doubled their users, 100% increase !
      Company B as 100 users of their phone. Then another person buy the phone. Now there is 101 usersm but only 1% increase

      If you only look at the stats, Company A is growing way faster than Company B.

      --
      Avoid the MS tax, always buy I.B.M. PC's (I Built-it Myself)
    3. Re:Product death ... by gstoddart · · Score: 1

      You do realize Windows Phone market share is growing faster than any other currently?

      Why, yes, they could double their market share by selling a relatively small amount of units, but that doesn't mean that there is really a significant amount of them in use.

      According to this:

      Over the past 12 months, Windows Phone went from 3.1% market share to 3.7%. This means that while shipments of Windows Phone devices are growing, they're barely growing any faster than the industry as a whole.

      Ooooh, Microsoft has gained 0.6% of the market over the last 12 months. I'm impressed, and I can only imagine the competitors are all running scared.

      And in case you'd like to claim that's not what it says, let's go straight to IDC here, it's the first table on the page. They may have shipped 8.9M units this year vs 4.7M units last year, but how many of them have actually sold?

      Jesus fanboys are terrible.

      Yes, especially when they cling to a lame statistic which doesn't say what they think it says. Next you'll try to tell me the Zune was a raging success.

      It's true that, as a percentage increase from what they had last year, Microsoft phones are 'growing faster' relative to itself (NOT faster relative to the overall market), but in terms of overall magnitude in the market, it's still a dud. Compared to what it did last year, it make huge gains ... compared to what everybody else did last year, Windows phone is a drop in the bucket.

      That doesn't equate to "Windows Phone market share is growing faster than any other" -- not by a bloody longshot.

      But, hey, you keep consoling yourself that it's the fanboys of competing technologies who are spreading lies and propaganda that Windows Phone is a joke and a failure. You console yourself that, if they'd only listen to the statistics which demonstrate it's a superior phone, we could all get along.

      And I'll keep assuming you're a drooling idiot who doesn't know how to read the statistics. All that stat says is how fast Microsoft's share increased over the last year compared to where Microsoft's share was last year.

      But growing from 3.1% of a market to 3.7% of a market isn't the success story you seem to think it is.

      --
      Lost at C:>. Found at C.
  15. Where does it say that it cannot be patched? by Fosterocalypse · · Score: 4, Informative

    You put it in quotes so I assumed you were quoting one of the two links you put in but neither state that. I know there's a lot of anti-MS people here but stick to the facts please. I understand that the current solution they offer is not a patch but something that the user needs to do manually, but seriously when you quote something use what they actually said. "Recommendation. Apply the suggested action to require a certificate verifying a wireless access point before starting an authentication process. Please see the Suggested Actions section of this advisory for more information." - from: http://technet.microsoft.com/en-us/security/advisory/2876146

    1. Re:Where does it say that it cannot be patched? by UnknowingFool · · Score: 3, Informative

      I think technically the flaw cannot be patched, but the vulnerability can be mitigated. Just reading it, it seems to be an inherent problem with the algorithm. Presumably it is analogous to the DNS cache poisoning flaw that Dan Kaminsky discovered in 2008. DNS was patched to make it less vulnerable but the flaw existed in the protocol itself. There was no truly way to fix it without re-writing the protocol. Replacing it with DNSSec was the recommended course of action.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    2. Re:Where does it say that it cannot be patched? by WaffleMonster · · Score: 3, Interesting

      I think technically the flaw cannot be patched, but the vulnerability can be mitigated. reading it, it seems to be an inherent problem with the algorithm.

      This is not the case here. It is a flaw in the MS implementation of a technology rather than the technology itself. A flaw by the way does not exist in other versions in Microsofts own products if they are configured properly.

      Presumably it is analogous to the DNS cache poisoning flaw that Dan Kaminsky discovered in 2008. DNS was patched to make it less vulnerable but the flaw existed in the protocol itself. There was no truly way to fix it without re-writing the protocol.

      There was no way to fix SYN attacks against TCP without replacing it either...oh wait yes there was cookies were added to mitigate the problem and today are widely deployed. The same solution for DNS continues to sit on a shelf and collect dust for no sane reason.

      http://tools.ietf.org/html/draft-eastlake-dnsext-cookies-03

      Replacing it with DNSSec was the recommended course of action.

      April 1st must come late this year cuz DNSSec is glued on top of DNS and has all the same insane transport issues that we continue to allow DNS to have. Only now now with significantly higher computational cost and DDOS amplification factors which just might give SNMP with public community strings a run for its money.

    3. Re:Where does it say that it cannot be patched? by UnknowingFool · · Score: 2

      There was no way to fix SYN attacks against TCP without replacing it either...oh wait yes there was cookies were added to mitigate the problem and today are widely deployed. The same solution for DNS continues to sit on a shelf and collect dust for no sane reason.

      The inherent problem is that DNS uses a 16-bit number for the query id as a means to authenticate the response. Changing DNS to use a larger number would require a major re-architecture of the protocol. The short-term patch was to pair the id with a 16-bit port number to increase the possible combinations. But that was only a short-term solution.

      April 1st must come late this year cuz DNSSec is glued on top of DNS and has all the same insane transport issues that we continue to allow DNS to have. Only now now with significantly higher computational cost and DDOS amplification factors which just might give SNMP with public community strings a run for its money.

      Um what? If I said WPA is vulnerable, replace it with WPA2, would your response be "Wait, WPA2 is glued on top of WPA!" Also I didn't recommend DNSSec. Dan Kaminsky and others did: "DNSSec has been proposed as the way to bring cryptographic assurance to results provided by DNS, and Kaminsky has spoken in favor of it."

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    4. Re:Where does it say that it cannot be patched? by WaffleMonster · · Score: 1

      The inherent problem is that DNS uses a 16-bit number for the query id as a means to authenticate the response.

      Correlating responses aint the only problem deploying cookies would solve. Amplification of bogus requests is a huge issue large scale deployment of DNSSEC will have made much worse.

      Changing DNS to use a larger number would require a major re-architecture of the protocol.

      I bet you didn't click on the ID link describing how to fix it did you? But yea major re-architecture..blah blah blah..

      Um what? If I said WPA is vulnerable, replace it with WPA2, would your response be "Wait, WPA2 is glued on top of WPA!"

      WPA analogue does not work. It is more like SSL v3 vs TLS v1.

      Also I didn't recommend DNSSec. Dan Kaminsky and others did: "DNSSec has been proposed as the way to bring cryptographic assurance to results provided by DNS, and Kaminsky has spoken in favor of it."

      Don't care about popularity contests or who said what.

      The reality is DNSSEC is glued atop DNS and it does inherit all of the same transport problems from DNS. While it is true you can layer something on top of something else and improve a security aspect what good is that if your denied use of the network because DNSSEC is being leveraged to DDOS you or your upstream into oblivion? The transport picture and the risk it represents to the larger network is unacceptable regardless of how "secure" DNSSEC is.

    5. Re:Where does it say that it cannot be patched? by UnknowingFool · · Score: 1

      I bet you didn't click on the ID link describing how to fix it did you?

      I did and, first of all, your link describes a proposed standard 5 years ago. I do not see that it has been accepted as a standard to IETF. Second in Eastlake's presentation he notes: "Provides weak authentication of queries and responses. Can be viewed as a weak version of TSIG. No protection against “on-path” attackers, that is, no protection against anyone who can see the plain text queries and responses"

      I read that as it probably would work if adopted but it is only slightly more secure than DNS but not my much. Port randomization probably does more.

      But yea major re-architecture..blah blah blah..

      Well if you need a more thorough explanation you can read this much more detailed and illustrative one.: "As has been alluded to several times, it's the small space — just 16 bits — of the Query ID that makes this attack possible. Though certainly one might wish to increase that ID to something larger (perhaps 32 bits), it's simply not possible do that in the short term because it would break DNS on the internet: the fields are what they are, and they can't be changed casually.

      Don't care about popularity contests or who said what.

      So you don't care how the hacker who found the problem proposes to fix it. By the way, Kaminsky has never liked DNSSec but he says it's the best solution for now. He actually would prefer DNSCurve but at the time was not ready. It might eventually replace DNSSec. Who do you care about? What about IANA: "DNSSEC is the current answer to this problem. This attack provides clear incentive to deploy a solution like DNSSEC, because without security the DNS will continue to be vulnerable to cache poisoning attacks."

      The transport picture and the risk it represents to the larger network is unacceptable regardless of how "secure" DNSSEC is.

      In response to this attack all the root servers implemented the solution Kaminksy suggested. People who know far more about Internet security than you and me did this. Either they implemented a popular but less secure solution. Or they don't know as much as you. Or they know what they are doing.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
  16. Hardware And Services by Anonymous Coward · · Score: 0

    Hows that working out for you, Microsoft?

    People already weren't buying your hardware or services before you switched, you think people are ever going to?
    People hate you as a company now, like genuinely hate you. They learned your bullshit tactics and now they are finding alternatives.

    Shoulda stuck with the OS and Office types. Those were your biggest income.
    But you shafted everyone from Vista onwards. You even fucked over Intel and straight up lied to them. Wintel died that year.
    Who has your back now?

  17. it does it automatically by dutchwhizzman · · Score: 1

    The problem is that you can't really turn off this behaviour and it does it automatically. Every client (laptop, tablet, phone, other wireless device) that does this fully automatic, may leak Active Directory account data that could be used to actually log on to file servers as well. It's not just MicroSoft that has this problem with PEAP, but that it's apparently not possible (at least not easily) to put some safety measures on the phone so you can mitigate this. I'm sure there will be other PEAP client implementations on other vendors devices that will suffer from this "automatically leaking AD logon data", but apparently, most vendors don't do it as bad as MS?

    --
    I was promised a flying car. Where is my flying car?
  18. Redmond? by Anonymous Coward · · Score: 0

    Who is 'Redmond' by the way?

    1. Re:Redmond? by Teun · · Score: 1

      You must have set Google to Safe Browsing...

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  19. Reeks of a data funnel by Stan92057 · · Score: 1

    Reeks of a data funnel for the NSA

    --
    Jack of all trades,master of none
    1. Re:Reeks of a data funnel by Anonymous Coward · · Score: 0

      Moron.

  20. This is a willfull and intentional act by WaffleMonster · · Score: 4, Interesting

    I personally contacted MS security people about this years ago before WP8 was released and they told me they would look into this and get back to me guess what I tried to follow up and they never did.

    To be very clear the problem is complete lack of necessary levers and knobs to validate the TLS certificate and common name of certificate in WP7-8. Without these options TLS is trivially MITMd this leaves only MS-CHAPv2 which has known to have been completely and publically broke for years.

    What is worse they don't even try there is not even a leap of faith latch as there is in other mobile platforms whereby if the cert changes it at least tells you it is different... The system never warns you or anything.

    To be even more clear this is not a problem that Microsoft just stumbled on... They knew full goddamn well what the implications of leaving those levers and knobs out of WP7 were... They knew about them circa 2002-2003 when their wireless supplicant was released for XP. They just didn't give a shit.

    1. Re:This is a willfull and intentional act by Anonymous Coward · · Score: 0

      No, you didn't.

    2. Re:This is a willfull and intentional act by Anonymous Coward · · Score: 0

      Oh yes he did.

    3. Re:This is a willfull and intentional act by Anonymous Coward · · Score: 0

      Times change. These days Microsoft is offering bounties for good attack instructions. I hope they expand the bounty program to all their products.

      http://www.microsoft.com/security/msrc/report/bountyprograms.aspx

  21. Microsoft is so dead. by Anonymous Coward · · Score: 0

    Microsoft is so dead.

    1. Re:Microsoft is so dead. by Anonymous Coward · · Score: 0

      Does Netcraft confirm that?

  22. So This Problem Affects... by Anonymous Coward · · Score: 0

    ...how many worldwide "lusers" that ought to be using something else....

    1. Re:So This Problem Affects... by cbhacking · · Score: 1

      About 3.7% of smartphone users.

      It's not unique to WP8 either; MS just happens to have issued an advisory about it. By default, I don't believe Android validates the SSL certs used for PEAP either.

      --
      There's no place I could be, since I've found Serenity...
    2. Re:So This Problem Affects... by Anonymous Coward · · Score: 0

      Not by default, but it really isn't very hard to add validation. That's what my company does for all of our Android devices, and we regularly test our network and devices for possible problems. Unfortunately there is no way to fix the problem with Windows Phones from an end user standpoint, so they are about to lose ALL marketshare from the private sector.

  23. Android is vulnerable too by Anonymous Coward · · Score: 0

    If the end-user doesn't require a server certificate check then Android is vulnerable too.

  24. How can.. by Anonymous Coward · · Score: 0

    Windows Phone 8 have vulnerabilities if nobody uses it.....

    1. Re:How can.. by Anonymous Coward · · Score: 0

      Windows Phone 8 have vulnerabilities if nobody uses it.....

      Ok... Hypothetically, if anyone actually used WP8 then they would be vulnerable.

      Fixed it for you...

  25. Re:Can't you protect it with HOST files? by cmurf · · Score: 1

    They lack innovation because they lack imagination. Ballmer isn't a futurist. Until he, and the entire VP layer, are gone, we will not see innovation from Microsoft. "There's no chance that the iPhone is going to get any significant market share. No chance." That, in a world with craptastic cell phone UX. The typical houseplant knew it was a dead paradigm on life support, and anyone who came in to do a half way decent job would get significant market share. Microsoft desktop OS lifespan is 12+ years to the point most of it's users not only don't expect innovation, they don't want it. And then for the past ~4 years did the polar opposite with their mobile strategy by having zero legacy compatibility, to the degree hardware was being abandoned (no software updates) days after being announced.

  26. Re:Can't you protect it with HOST files? by Yunzil · · Score: 0

    "Compare that to Google, which is showing you self-driving cars, Google Glass and a phone that you can talk to, the Moto X, and on and on â" automatic picture improvements on Google+

    Except none of that is really interesting either, because I don't want any of it. And get off my lawn.

  27. Nah! by dhaen · · Score: 1

    They all use iPhones...

  28. Re:Can't you protect it with HOST files? by Anonymous Coward · · Score: 0

    In its entire history the Kinect seems to be the only innovative technology, maybe DCOM, they've come up with.

    The company is on the other hand absolutely brilliant in marketing, bundling, and contract negotiations.

  29. Re:Can't you protect it with HOST files? by Anonymous Coward · · Score: 0

    Anyway, I want a self -FLYING car. That I can talk to.

  30. Game Over Man, Game Over. by Anonymous Coward · · Score: 0

    Ditto. For one cent to a dolllar............

  31. Although the real question is... by peacefool · · Score: 1

    will it blend?!