Slashdot Mirror


Microsoft Working With Security Vendors

mikesd81 writes "The BBC is reporting on Microsoft's U-Turn. They've now given security vendors some of the information they want to make their products work with Microsoft's new operating system, Vista." From the article: "Earlier this month, security firm McAfee took out a full-page advert in the Financial Times to alert readers to its worries about the way Microsoft was handling the release of its new operating system. 'Microsoft seems to envision a world in which one giant company not only controls the systems that drive most computers around the world but also the security that protects those computers from viruses and other online threats,' the advert said. "

98 comments

  1. Is anyone suprised by Anonymous Coward · · Score: 0, Troll

    And this is suprising how? Play with the devil...

  2. World Domination by New+Breeze · · Score: 0, Troll

    So MS was considering leveraging Vista for world domination... Who here is surprised?

    1. Re:World Domination by MollyB · · Score: 3, Insightful

      Don't they just do what they want unless they "lose" a legal case, then continue whilst appealing until the suit is moot? Or until a settlement is reached (money changes hands and minds)?

      MS is such a juggernaut that it flows around or over obstacles, like an avalanche, tsunami, mud (fud?) slide, etc. If McAfee and company survive, they'll be the exception that makes the rule, imho.

    2. Re:World Domination by Rob+T+Firefly · · Score: 2, Insightful

      I like MS-bashing as much as the next basher, but this is just a cheap shot. When you get down to it, isn't virtually every company in every trade envisioning a world in which they eventually snuff out all the competition and grow to become the only source for whatever it is they do? Even if you know it won't logically happen, it's still the general goal that's paraphrased into the "mission statement" posters in every corporate breakroom.

    3. Re:World Domination by From+A+Far+Away+Land · · Score: 1

      I'd get a kick out of Vista using its DRM badness to block McAfee and Symantec from running. Something along the lines of:
      "This software is unathenticated, and could be malware.
      Would you like to:
      Block / Permit once / Report this problem to Microsoft and Continue"

    4. Re:World Domination by Trelane · · Score: 1
      When you get down to it, isn't virtually every company in every trade envisioning a world in which they eventually snuff out all the competition and grow to become the only source for whatever it is they do?

      Sure, but there's a critical difference: very, very few can.

      --

      --
      Given enough personal experience, all stereotypes are shallow.
    5. Re:World Domination by Rob+T+Firefly · · Score: 1

      Yes, but McAfee could do a lot better to make their point. (I was referring to them mainly, I probably should have made a new post rather than replying to a thread. Sorry!) The full-page ad and everything comes off as petulant, pinting at MS and saying "they want to own everything and that's bad!" Joe Public isn't going to come off any wiser as to why the way they're going about it is bad. Most people, however dense, tend to take comments about any company or person made by their competition with a grain of salt.

  3. Never Happy by corroncho · · Score: 1, Insightful

    These security vendors been taking advantage of the flaws in the windows OS's for years and making tons of money doing it. Great someone needed to do it since MS couldn't or wouldn't. However MS is now trying to hardent heir OS and remove the security holes that should have been removed years ago and what happens? People complain. And by people I mean Symantec, McAfee, etc (not the end user mind you).

    I for one am pleased to see MS trying to lock down their systems and these other vendors just need to quite whining. I am sure there will still be plenty left to fix. There always is.
    ___________________________
    Free iPods? Its legit and simple. 5 of my friends got theirs. Get yours here!

    1. Re:Never Happy by Silver+Sloth · · Score: 2, Insightful
      Well... er... yes.... but....

      The otherside of the arguement is that the proposed Vista lockout would leave M$ as the only suppliers of anti malware (Ok, so Symantic don't seem to agree, but I'm stating McAfee's aguement, not mine) and we are all aware of the dangers of a monoculture, especially one run by Seatle's finest.

      What I want, if at all posible, is the choice to run which anti malware systems I choose.

      --
      init 11 - for when you need that edge.
    2. Re:Never Happy by lbmouse · · Score: 2

      Do you honestly believe that if MS locks down Vista it will solve any security issue? If anything it makes the OS more vulnerable because now the only people that are aware of the security holes are either working in Redmond and/or working to find ways to take advantage of the holes (aka, bad guys). IMHO it's a good thing to have as many (good guy) eyes as possible reviewing an OS's framework.

    3. Re:Never Happy by Amouth · · Score: 1

      What gets me is MS took a page for Apple's book and it set them on fire..

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    4. Re:Never Happy by Silver+Sloth · · Score: 1
      Ooops

      in parent post s/Symantec/Sophos/

      --
      init 11 - for when you need that edge.
    5. Re:Never Happy by mikesd81 · · Score: 1

      What I want, if at all posible, is the choice to run which anti malware systems I choose.

      Not only to chose which one you want, but it should be easy to install the one you want easily as well.

      --
      That which does not kill me only postpones the inevitable.
    6. Re:Never Happy by baadger · · Score: 1

      Vista may be trying to harden their OS with Vista, but there screwing up alot of the decisions again.

      People are still essentially setup as pseudo-admins out of the box (i'm sure UAC won't solve the problem) and DEP is disabled on all programs by default (most of the recent critical XP flaws are prevented by DEP being enabled for all programs and services).

      I'm glad they have improved useability as a limited user though. Switching to a limited user account, disabling UAC, and enabling DEP will be the first things I do. Vista still prompts for admin priveleges but asks for a password instead of a simple click.

    7. Re:Never Happy by Anonymous Coward · · Score: 0

      Fuck off, you spamming asshole.

    8. Re:Never Happy by Anonymous Coward · · Score: 0

      (IMHO it's a good thing to have as many (good guy) eyes as possible reviewing an OS's framework) I am so glad they have their eyes on it, maybe some day they will do something about what they see. I have seen many machines with Symangoof and Mcaffafolp with all their so called updates and patches up to date but still infected with malware, spyware, viruses. I am not the greatest fan of Microsoft, but I am starting to wonder if the problem with MS security might lie in all the doors they have to leave unlocked for vendors such as the above mentioned ones. Everyone always focuses at MS windows when there is a problem, "Windows let malware or a virus get in my computer". No one every seems to look at these third party softwares and how poorly they are written. Virus a lot of times are coded to infect the anti-virus scanners first then they have its API's to the kernel. Third party uninstallers are a joke, they never remove all that they put in, WHY??? Why are the not held to the same expected standards as those imposed on Windows. I think it sould be up the us (the end user, the consumer.) I think Microsoft should offer the option, like during setup/install of windows to choose the locked kernel or the unlocked (so to speak)kernel. They could put a disclaimer explaining the difference, but let us choose, not the other software companies or the European Union. I live in the USA not Europe, and I sure did not elect Symantec or Mcaffee to represent me.

  4. Oblig by mattwarden · · Score: 0

    "The wolf shall dwell with the lamb, and the the leopard shall lie down with the kid; and the calf and the young lion and the fatling together; and a little child shall lead them." Isaiah 11:6-7

    1. Re:Oblig by gstoddart · · Score: 0, Offtopic
      "The wolf shall dwell with the lamb, and the the leopard shall lie down with the kid; and the calf and the young lion and the fatling together; and a little child shall lead them." Isaiah 11:6-7

      Hmmm .... I don't know what Slashdot you've been reading, but on the one I read, the obligatory is more of the form: in Soviet Russia, security firms give information to you.

      Biblical quotes ... not so much. :-P

      Cheers
      --
      Lost at C:>. Found at C.
    2. Re:Oblig by Anonymous Coward · · Score: 1, Funny

      In Soviet Russia, bibles quote you!

      "And the Lord sayeth unto the followers of Portman,
      'Lest ye poureth steaming gryts into thyne trousers,
      Ye shall be stripped and turned to stone...'"

    3. Re:Oblig by Jugalator · · Score: 1

      I first thought it was something related to the Book of Mozilla. Shows how interested I am in those stories. :-p

      --
      Beware: In C++, your friends can see your privates!
    4. Re:Oblig by Anonymous Coward · · Score: 0

      and the the leopard shall lie down with the kid

      So, is that pedophilia or zoophilia they are about?

  5. Oh No! by balsy2001 · · Score: 4, Funny

    MS is destroying my revenue stream by making a more secure OS!

    --
    GENERATION 27: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    1. Re:Oh No! by Anonymous Coward · · Score: 0

      Yea, all the AV vendor QQing paid off I guess.

    2. Re:Oh No! by UnknowingFool · · Score: 1
      MS is destroying my revenue stream by making a more secure OS!

      There's two sides to this issue. From the security vendor's standpoint, MS is just making it harder for them to work with Vista. While there are locking down the OS somewhat, MS will be releasing competing security products. This has shades of the antitrust behavior which got them into trouble. On the other hand, Trend Micro has been able to work through the changes in Vista.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    3. Re:Oh No! by Gunfighter · · Score: 2, Insightful

      There's actually a lot of truth to this statement. Success for Microsoft can mean an overall decrease in long term recurring revenue for a variety of service providers (even Microsoft Certified Solution Providers). If Vista is more secure, it means less need for "more secure" alternatives. For those of us who base our living off of maintaining and supporting said alternatives, this is a bad thing.

      Personally, I support homogenous networks; so I will see a spike in revenue from any XP->Vista upgrades. In the long run, there will be a decline in revenue if Vista is more secure. A more secure OS means fewer customer calls for security related issues and a decrease in the sales, installation, maintenance, and support of security related products. Initially, the antivirus/antispyware/firewall/IDS/etc. sales and support would stay the course. People have it engraved in the back of their heads that they need all of these things when they're running a Windows environment. Over time, the perception and realization would be that such preventative measures are no longer required.

      Luckily, I don't think Microsoft is releasing a more secure OS. Just like every Microsoft Operating System to date, I have a feeling they will roll it out with trumpets blaring and decree how secure it is.... only to have some black hat cracker show up at a hacker conference with an arsenal of exploits and blow holes in their hard work. We all know that there is no such thing as a completely secure networked computer; but I would caveat that with "especially a Microsoft-powered system." I don't see that caveat changing any time in the near future.

      --
      -- Stu

      /. ID under 2,000. I feel old now.
    4. Re:Oh No! by drsmithy · · Score: 1

      There's two sides to this issue. From the security vendor's standpoint, MS is just making it harder for them to work with Vista.

      Indeed. Now, instead of just trundling around wantonly in kernel space with their buggy software, they'd have to actually stick to known and documented APIs. The horror !

      While there are locking down the OS somewhat, MS will be releasing competing security products.

      Which use the same APIs available to _all_ "security software" vendors.

      Despite Slashdot folklore, the whole "secret APIs make Microsoft software work better with Windows" has never been more than an urban legend.

      On the other hand, Trend Micro has been able to work through the changes in Vista.

      Exactly. Which tells you everything you need to know about the validity of McAfee and Symantec's claims.

    5. Re:Oh No! by tokul · · Score: 1
      MS is destroying my revenue stream by making a more secure OS!
      Nope. MS is destroying revenue stream by changing API and locking all security products except own one.
    6. Re:Oh No! by kabz · · Score: 1

      Norton, Macafee, Symantec and the like need to build a better rootkit.

      Maybe they should give Sony a call. ;-)

      --
      -- "It's not stalking if you're married!" My Wife.
    7. Re:Oh No! by molarmass192 · · Score: 1

      Despite Slashdot folklore, the whole "secret APIs make Microsoft software work better with Windows" has never been more than an urban legend.

      As a former Windows programmer, I can assure you that there were many undocumented, aka. secret, aka. internal, API calls which provided functionality not available in any of the documented Windows APIs. I'm speaking from a W2K perspective, which I assume also carried forward to XP. This may have changed in Vista, but I'd be very surprised if there were no undocumented APIs, especially since in the McAf/Sym case there are now documenting a previously undocumented API. Now, as for making MS software work *better* than 3rd party software ... that's an urban legend ... it may have more *functionality*, but certainly not work *better*.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    8. Re:Oh No! by gutnor · · Score: 1

      "Luckily, I don't think Microsoft is releasing a more secure OS."

      Security is a *problem*, not a feature that's nice to keep around. What you are asking is a bit like "I sure hope they will never cure cancer because today it makes confortable living for a lot of doctor, scientist, psychologist, charity, widow association, ..."

      I hope Vista is more secure and that all the money and work that goes into security software goes into something else a bit more productive. By "more productive" I mean something that is directly related to the reason why you have a computer in the first place. Nobody buys a computer to run security software.

      Making computers more accessible and easier to use means that other markets will be available. Internet connections are much faster and requires a lot less support than in the past. That's why more people can connect and why Google is making billions.

    9. Re:Oh No! by AmberBlackCat · · Score: 1

      It looks to me more like "Microsoft is making Windows no longer compatible with my security software at the same time they're making their own software to compete against me".

    10. Re:Oh No! by drsmithy · · Score: 1

      As a former Windows programmer, I can assure you that there were many undocumented, aka. secret, aka. internal, API calls which provided functionality not available in any of the documented Windows APIs.

      I am not disagreeing there are undocumented APIs. All platforms have "undocumented APIs" in one form or another, and always will. I am arguing that they were never used in a "nefarious" fashion by anyone at Microsoft.

    11. Re:Oh No! by will_die · · Score: 1

      I guess it depends on what your definition of "nefarious" is. If nefarious does not means that certian APIs exsist for use by other microsoft products(non-OS), or very close outside companies, or allow thier products to operate faster then using the documented APIs then you are right. Most devs would not call it nefarious if it was something microsoft was not using internally, the documentation was wrong comparied to implementation or was clearing marked as for testing and somehow made it through to the final version(but was not actually used anywhere).
      Look at cases of the AARD code(more of an interface), the loadhi API, the XMS 3.0 spec, EMM Import spec. Also various lead devs at microsoft have admitted that they had undocumented API done in the OS and used in office for communication. Also look at various lawsuits as New York vs Microsoft or Caledra vs microsoft also grab copies of the older books of undocumented APIs
      Microsoft has gotten alot better in this in the last few releases and has gotten to the point where it is not really an issue any more

    12. Re:Oh No! by Gunfighter · · Score: 1

      Very well, just take the "Luckily" out of that statement and re-read it.

      I imagine for most slashdotters, it's not so much a "lucky for us people who support FLOSS/Windows security and can still make money off of it" as it is a "lucky for us people who believe the security of Microsoft products is flawed by design and them releasing yet another buggy, unsecure OS proves correct what many people have been saying for quite some time: if you want hardened systems, stay away from Microsoft products and go with something a little more bulletproof."

      I'm all for Microsoft doing a ground-up rewrite of their Operating System with security as the top priority. I hope they do it some day. After I posted that post, I went and looked at my accounting records for the past year because I was curious how much time I had actually spent helping customers with Windows security measures. From the numbers I crunched, it probably wouldn't affect my little slice of IT consulting revenue one bit if Microsoft were to roll out the Windows 2009 Holy Grail of Security Edition. As a good friend of mine once said when he first opened his IT consulting firm a few years ago, "There will always be someone out there willing to pay me to show them how to set up macros in Microsoft Word."

      P.S. Security isn't a problem or a feature. It's a process ;)

      --
      -- Stu

      /. ID under 2,000. I feel old now.
  6. Lack of clarity by LaughingCoder · · Score: 1
    The article is not very clear as to exactly what the "u-turn" is. First there is this:

    The news that the software giant will now allow companies such as McAfee and Symantec access to the kernel of the 64-bit version of Vista has been met with cautious approval.
    Is it only the 64 bit version of Vista that was the problem? Further down in the article we have this:

    Not all security firms have had issues with Microsoft. Security experts Sophos will release its Vista-compatible product next month.

    This makes me wonder what all the complaining is really about. You don't think McAfee and Symantec are just paving the way for future lawsuits when Vista's inherent security renders their products obsolete, do you?
    --
    The more you regulate a company, the worse its products become.
    1. Re:Lack of clarity by drsmithy · · Score: 1

      This makes me wonder what all the complaining is really about.

      The complaining is about Symantec and McAfee having to rewrite their software _properly_ and use public APIs rather than just rehashing the same POS every year that hooks into undocumented parts of the Windows kernel at will.

  7. A trickle... by Gription · · Score: 0, Troll

    They give them SOME of the info they need...
    3 months before the OS releases in stores.

    I'm sure that they can write a completely new release-ready product in 3 months. Plenty of time for coding, testing and maybe even a beta release...

    Yeah, right.
    Microsoft makes sure they have an advantage.

    1. Re:A trickle... by Rob86TA · · Score: 5, Insightful

      That's funny... Trend Micro had a fully working Anti-virus product during the Beta. They didn't need any special "Kernel Interface Documenation" to make it work. All the information needed was already available, this is about Norton and McAfee whining because THEY couldn't work with MS and wanted special kernel access, not the other way around.

    2. Re:A trickle... by Penguinisto · · Score: 1
      I think the big stink was w/ folks working the whole rootkit-detection angle (which would require something a bit tighter to the kernel), and not the ordinary everyday virus/worm propagation (which could more easily be caught with something looking for memory footprint signatures or what-have-you).

      But then again, F-Secure is big on rootkit detection, and you didn't hear any crying out of them ab't the whole Vista thing. *shrug*

      /P

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    3. Re:A trickle... by gEvil+(beta) · · Score: 1

      Does Trend Micro's product work on the 64-bit version of Vista? Apparently it's the 64-bit version that only allows signed drivers and has many of the extra security methods in place. That's what Norton and McAfee are complaining about. Their products will work fine on the 32-bit version.

      --
      This guy's the limit!
    4. Re:A trickle... by Rob86TA · · Score: 1

      Yup... both 32 bit and 64 bit versions were released by Trend, see: https://www.trendbeta.com/index.php?get=80

    5. Re:A trickle... by Flopy · · Score: 1

      Not only that, but the available information is just enough for any application to run without problems. Giving the Kernel Interface Documentation away will probably make more vulnerabilities available in the future.

  8. Finally, they did something right? by Penguinisto · · Score: 1, Interesting
    Of course, Symantec and McAfee are likely singing MSFT's praises to high heaven once again... (and their business model is saved)

    OTOH, given the closeness of the supposed release date, it tells me that the requisite holes were likely already there to begin with (and that they can likely be exploited, even if MSFT sat tight and never gave the A/V folks the info anyway). That, or they're burning midnight oil to open up said holes (which would mean that oh damn, here it comes...!)

    Man - either way, this doesn't exactly insipre confidence that MSFt, Vista, or it's devs were actually serious about security (save through obscurity) in the first place...

    /P

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
    1. Re:Finally, they did something right? by kestasjk · · Score: 1

      Microsoft developed software called PatchGuard to keep 3rd party stuff out of the kernel, this is what McAffee and Symantec are complaining about.

      It doesn't seem like the sort of software that would break things when taken away, it seems like the sort of software which you could toggle (though that would defeat the object of course).

      --
      // MD_Update(&m,buf,j);
  9. This is all so dumb by Moby+Cock · · Score: 2, Insightful

    While I revile MS for their draconian business practices, Mcafee is not much better. The problemm with security is that everyone have (roughly) the same system. There is no variation in the computers on the 'net. A windows box with Mcafee (or Norton, to me they are all the same) is as vulnerable as anyother equivalently equpipped box. So a virus will spread quickly. Imagine every person ob earth had an equivalent immune system. Every mutated bug would render the entire population out for the count.
    For Mcafee to raise the alarm that MS was playing fast and loose with security by freezing out security software is just crap. Its FUD just like the crap MS spouts. Although it seems to have worked in this case.

    1. Re:This is all so dumb by Gospodin · · Score: 1

      Hey, I've got a solution to this: just have the McAfee, etc. client turn off random virus definitions from time to time. Then everyone would have a different "immune system"!

      Sheesh.

      --
      ...following the principles of Heisenburger's Uncertain Cat...
    2. Re:This is all so dumb by Anonymous Coward · · Score: 0

      Yup. Just ask Symantec how a user program can scan a file, just as Microsoft Word does, and you get a "we can't tell you for security reasons." Cosy little relationship they have going there.

  10. Financial Times? by caylem · · Score: 1

    It's nice to know that there's an effort being made to make the general pubic more aware of the Microsoft and its quest for world domination, but seriously, the Financial Times? While I'm sure many /.'s read it, consider the amount of people who use McAfee, use Windows, and don't read that particular paper.. or watch/read the BBC. Perhaps a full-page ad in the tabloid magazines/newspapers would reach a larger audience.

    1. Re:Financial Times? by The+Real+Andrew · · Score: 1

      But the people who read the FT are the ones who will be shelling out the big bucks for Vista Super Corporate Bells and Whistles edition, not the tabloid readers who are going to get it off bit torrent.

    2. Re:Financial Times? by caylem · · Score: 1

      assuming they know how to use bt. out of my non-pc savvy famly and friends, a total of 2 know what bt is, but dont know how to use it. and yes, they have all bought legit copies of all their windows versions. and theyll prolly buy vista too.

  11. "Some"? by k33l0r · · Score: 0, Troll

    "Some of the information"? So not all? Will this information be useful or will it be an empty gesture to try and make Microsoft look like a well behaved and caring company?

  12. Related by caluml · · Score: 1, Offtopic

    An old Russian saying: The wolf will hire himself out very cheaply as a shepherd.
     
    My point? None.

  13. Why MS never can do it right? by atchijov · · Score: 1, Troll

    So MS try to do "right-thing" by hardening Vista. Due to they arrogance they ignored all 3-rd party security companies while doing it. Now they figure out that they can not ignore them after all. So instead of having properly designed 3-rd party integration APIs they will try to put together something quick -- and most likely undo at least some of the "right-things" in the process.

  14. And the problem with Microsoft Securing by Frumious+Wombat · · Score: 2, Insightful

    their OS is....?

    From the Original post: 'Microsoft seems to envision ... but also the security that protects those computers from viruses and other online threats,'

    Not to be picky, but on my Solaris boxes, I don't call up McAffee every time a security vulnerability is released, nor do I call them to protect my AIX systems from Crackers either. I expect that Sun and IBM, respectively, will secure their OS, issue patches, and provide the appropriate tools to manage security. We've been letting Microsoft get away with fobbing that duty off on third-parties for far too long. Pity if that impacts Symantec's business model, but Microsoft should have years ago either (a) fixed their OS or (b) taken the tcp/ip stack out and stuck a big, neon-orange, sticker on every box and install disk which reads, "This Products Is Terminally Insecure and If You Let It Connect to a Network, 12-Year Old Script Kiddies Will OWN Your Valuable Corporate DATA! Within 20 Minutes Or Less!"

    It's hard in a case like this to know which one of them (Microsoft or Symantec) to have less sympathy for.

    --
    the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    1. Re:And the problem with Microsoft Securing by Darkon · · Score: 1
      Not to be picky, but on my Solaris boxes, I don't call up McAffee every time a security vulnerability is released, nor do I call them to protect my AIX systems from Crackers either. I expect that Sun and IBM, respectively, will secure their OS, issue patches, and provide the appropriate tools to manage security.

      As usual it's that old bugbear antitrust rearing its ugly head again. McAffee et al claim that MS is going to produce its own anti-malware tools and lock them out of the market, kind of like if Sun hardened Solaris in such a way that you had to run their supplied Sendmail and it segfaulted when you tried to install Postfix.

      That said I think increased security trumps competition in this case. I don't want any APIs for 3rd parties to mess with the Windows kernel because malware writers will just use them too.
    2. Re:And the problem with Microsoft Securing by badfish99 · · Score: 1

      The sendmail analogy is surely wrong. Nobody buys add-ons from McAffee or anyone else in order to make Solaris secure. It is secure out of the box, as supplied by Sun.

      In the ideal world, if Windows were secure, there would be loads of competition for email software on Windows, but anti-virus software would just not exist at all.

    3. Re:And the problem with Microsoft Securing by drsmithy · · Score: 1

      In the ideal world, if Windows were secure, there would be loads of competition for email software on Windows, but anti-virus software would just not exist at all.

      Rubbish. AV software and OS security are only vaguely related.

      Only the inane ramblings of technically incompetent hacks has caused the clueless to think that "no viruses" and "secure" are synonyms. Anyone remotely knowledgable understands that AV software and OS security are solutions to almost completely different problems that go hand in hand, not one against the other.

  15. Antivirus and Security by TheRecklessWanderer · · Score: 3, Interesting

    It seems to me that lately the large players in the AV world (Norton, McAfee) have been trying so hard to differentiate their product from standard Microsoft offerings (i.e. add value to their products) that the cost/benefit of having one of the major player products is not good. We had a 20 or so copies of NAV 2005 (or maybe it was 2004) and we ordered them through Ingram Micro and we got the licences. So we installed the licences, and then a couple of weeks later they would need to be activated (again) but wouldn't accept the #. So after a month or so of this we scrapped the norton product, went to AVG and have had no problems since. So the moral of the story is that the large players are trying so hard to show that you HAVE TO have their product, and to make sure that you pay for it, that it is not a usable product, IMHO.

    --
    Mean what you say...say what you mean.
  16. Mark my words... by justinbach · · Score: 4, Funny

    Microsoft's security is gonna do a total 360!

    --
    I left my wallet in El Sigundo!
  17. this is dumb by Anonymous Coward · · Score: 1, Funny

    So Microsoft comes out with a system that isn't riddled with (the standard) security holes, and the third-party companies whose bottom line depends on MS incompetence freak out, because they're no longer needed.

    Microsoft can't win for losing.

  18. I look forward to that... by briancnorton · · Score: 0, Troll

    I really do look forward to a day when a software vendor takes responsibility for the proper functioning of their software. IMHO, Mcaffee, symantec, etc shouldn't exist. They are able to get by because of Microsoft's sloppiness. I don't blame MS one bit for trying to correct years of negligence. (I do blame them for those years of negligence) Making Microsoft Windows work shouldn't have to be a competitive industry, Microsoft SHOULD monopolize that.

    --

    People who think they know everything really piss off those of us that actually do.

    1. Re:I look forward to that... by mgblst · · Score: 2, Informative

      McAffee came about in the days of Msdos, when viruses would replace the boot sector, or attach themselves to the end of EXE and COM files. I am not sure that you can blame Microsoft for that one - there were before the days of encrypion and kernel protection, when any program had full access to memory, so there is not way you could stop it, without building a more secure os. And you can't start of building a more secure OS. (You need money, and ideas!)

    2. Re:I look forward to that... by Bobby+Mahoney · · Score: 1

      I agree... And on a slight tangent, At what point does an individual component of a given system become generally accepted as a standard offering of said system? I.E., an automatic transmission in a vehicle may of at one time have been considered an option but is now fairly standard on most vehicles. I'm sure there's a better automotive analogy, but you get the idea. At some point, antivirus (as viri are a fact of life) is going to become as standard as the gui. Note that at one point in the not-to-distant past, the GUI was (still is for some users) considered a separate entity from the os.

      --
      !#&*
  19. Good news, but not great news... by jmagar.com · · Score: 2, Funny
    I'm glad that Microsoft is being more open, and co-operating more. But I believe the real security improvements are from Microsoft, and the McAffees and Nortons of the world are becoming less relevant. I installed the latest McAfee "security center" on my mother in-law's PC and the system performance was cut damn near in half. The experience has cemented in my mind that an up to date version of Windows with the latest security patches is the right way to go, and that these third party tools are bloatware, and resource hogs. And that the protection they provide is an illusion anyway, since Microsoft patches holes much faster these days anyway. By the time the security vendors have a new identity update, Microsoft has patched the hole... So why waste the time, and money on these things anyway?

    The short answer is that it makes her "feel" more secure. (I'm not sure that she really is though)

    1. Re:Good news, but not great news... by Anonymous Coward · · Score: 0

      ha ha ha, there's more sh*t in this post than in my local water waste processing plant.
      Good to see people still give 'authorative' views on stuff they are clueless about ha ha ha again..

  20. MS should take security totally in house .. by rs232 · · Score: 1

    I would have no objection to to MS totally taking security in house. Locking down the kernel and only allowing API access would eliminate most of the defects in Vistos. The only difference is the end use pays MS a yearly subscription instead of McAfee $274.5, Symantec $4.14 billion) and the rest. Of course charging after the fact for defects in the product is a very odd way of doing business. Myself don't plan to pay either of them a cent for 'security'.

    --
    davecb5620@gmail.com
  21. AV further weakens TCO argument by businessnerd · · Score: 1

    I can understand why Microsoft wants to lock out the third party vendors. These vendors have convinced everyone that Windows is so insecure by default that whenever you buy a copy of windows, or a computer with windows on it, you must automatically buy their product as well as sign up for their subscription services. AV and firewalls are expensive (for a home user, tack on an extra $70 upon purchase on your new computer and another $30 or so every year after) and when Microsoft tries to make its Total Cost of Ownership (TCO) claims (which is total FUD anyway) it looks really bad when you must factor in security services into that cost, while Mac and the *NIXes have not such costs. If Microsoft can convince people that they don't need these third party vendors, they are much better off. I for one would really like to see a Windows release that really does not require third party security and once and for all mitigates the virus threat by design, not duct tape. Sure Windows will be specifically targeted as long as they hold the most market share, but this virus crap is rediculous.

    Follow-up question for all of the linux and mac gurus out there. I've always heard that Mac and Linux are inherently protected from viruses, meaning that if one were to actually catch a Linux or Mac virus, the damage done would be very minimal. How true is this, keeping in mind that a lot of viruses today are not necessarily there to vandalize, but to carry out ID theft?

    --
    "It's not whether you win or lose, it's how drunk you get." -- H. J. Simpson
  22. There seems to be a massive misconception here by Myria · · Score: 2, Insightful

    Reading the comments here, I think that most people aren't aware of what PatchGuard is.

    PatchGuard, quite simply, is "security through obscurity". Basically, while the kernel is running, a hidden background thread continuously hashes the code sections of the kernel and validates that nothing has changed. If something changes, the system bugchecks (blue screens). PatchGuard's security comes from it being obfuscated.

    PatchGuard doesn't offer true security. It has nothing to do with escalation of privilege - if you're able to modify the kernel, it's already too late. PatchGuard was intended to stop commercial products from patching the kernel because frequently they do so improperly, and end up causing instability and local privilege elevation exploits. If a company got around PatchGuard, their product would only work until the next second Tuesday. However, rootkit authors may not care about that "time limit".

    Certainly PatchGuard helps slightly with DRM. However its more important use is preventing companies from doing improper kernel hacks. With Microsoft bowing to these companies, PatchGuard's only use is now DRM.

    By the way, the only reason Microsoft is doing this is because of Europe's antitrust complaints. No full page ad will convince Microsoft of anything.

    Melissa

    --
    "Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
    1. Re:There seems to be a massive misconception here by Anonymous Coward · · Score: 0

      You are indeed correct about PatchGuard being purposely obfuscated (http://uninformed.org/index.cgi?v=3&a=3&p=1), but it certainly does raise the bar to rootkit writers, and ensures that earlier ones will not work with Vista.

    2. Re:There seems to be a massive misconception here by Shados · · Score: 1

      Yeah, its a shame Microsoft bowed down with this. Less intrusive anti-viruses worked fine, its only junks like Norton and McC that didn't, and forcing them to rewrite their product so that it doesn't bug down your computer more than running Oblivion in the background would have been a definate plus. Microsoft's monopoly has to be controled, but, in my opinion, not at "all costs". The customer lost on this one, in my opinion. Of course, it is easy to avoid these products for us...but for the rest, not really.

    3. Re:There seems to be a massive misconception here by drsmithy · · Score: 3, Interesting

      PatchGuard, quite simply, is "security through obscurity".

      No, it's not. Saying PatchGuard is "security through obscurity" is like saying passwords, etc are "security through obscurity".

      Basically, while the kernel is running, a hidden background thread continuously hashes the code sections of the kernel and validates that nothing has changed. If something changes, the system bugchecks (blue screens). PatchGuard's security comes from it being obfuscated.

      No, PatchGuard's security comes from not allowing unknown code to execute in kernel space. Ie: it stops things like rootkits from functioning by crashing the OS when it detects unauthorised activity.

      PatchGuard doesn't offer true security.

      No one measure offers "true security". PatchGuard is just another part of a layered security model.

      It has nothing to do with escalation of privilege - if you're able to modify the kernel, it's already too late.

      No, only if you *actually can* modify the kernel, is it already too late [for the kinds of attacks PatchGuard is protecting against]. Which is why the system crash-dumps - because there's not much else you can do in the face of an attacker who has already reached that level of privilege.

      PatchGuard was intended to stop commercial products from patching the kernel because frequently they do so improperly, and end up causing instability and local privilege elevation exploits. If a company got around PatchGuard, their product would only work until the next second Tuesday. However, rootkit authors may not care about that "time limit".

      PatchGuard is there to stop malicious and unknown interceptions of low-level system calls. In other words, the kind of stuff rootkits (in addition to badly written, but legitimate applications) do.

    4. Re:There seems to be a massive misconception here by mdozturk · · Score: 1

      ... by crashing the OS when it detects unauthorised activity

      This seems like a great way someone to cause my computer to crash. When will the patch come out for this denial of service attack?

    5. Re:There seems to be a massive misconception here by drsmithy · · Score: 1

      This seems like a great way someone to cause my computer to crash.

      Considering the alternative, it's a reasonable tradeoff.

      It's no different than any other OS that crashes instead of letting rogue code go tromping all over the kernel.

      When will the patch come out for this denial of service attack?

      Probably as soon as someone can come up with a better way of defending against the more important kernel attack.

    6. Re:There seems to be a massive misconception here by Beryllium+Sphere(tm) · · Score: 1

      OK, threat model is an attack that modifies the kernel. Attacker has root privileges.

      What keeps Patchguard running in the presence of intentionally bad code with full run of the system? What stops code that can and does modify the kernel from turning off or NOPing Patchguard?

      If the answer is something other than "by obfuscation" it would be educational to hear it.

    7. Re:There seems to be a massive misconception here by drsmithy · · Score: 1

      What keeps Patchguard running in the presence of intentionally bad code with full run of the system? What stops code that can and does modify the kernel from turning off or NOPing Patchguard?

      It halts the entire machine when something tries to modify it, thus stopping them from doing that.

      If the answer is something other than "by obfuscation" it would be educational to hear it.

      If you have better alternatives, I'm sure Microsoft's software engineers would be interested to hear about them.

    8. Re:There seems to be a massive misconception here by Anonymous Coward · · Score: 0

      you have lots of misconceptions about PatchGuard.

      1. digitally signed drivers have nothing to do with PG. after all, Windows has had driver signing well before Vista. Vista/amd64 does require signed drivers only (modulo whatever concessions MS made now), but that's a policy decision that could be implemented in older Windows versions as well, it just happens to be not practical for reasons that PG intends to address. also consider that a signed driver can just as well do all the bad things that an unsigned one, in fact, you'd think that Symantec et al. can afford the certificate to produce signed drivers, their issue was with what happens once executing in kernel mode, that's where PG kicks in.

      2. PG *is* obscurity, so are passwords or any method that relies on the secrecy of some piece of information. obscurity is not bad per se (we use it all the time in everyday life), maybe you were misguided by some security mantra that teaches otherwise.

      3. you've got some conceptual misunderstandings: digitally signed drivers ("not allowing unknown code to execute in kernel space") are different from runtime patch detection ("it stops things like rootkits from functioning by crashing the OS when it detects unauthorised activity"). the former prevents unsigned drivers from loading and hence executing altogether, there's no way such drivers could perform any unauthorized activity then (so contrary to your statement, they are not the same). the latter is what PG actually does but it needs some clarification, see below.

      4. you're wrong when you state that "if you *actually can* modify the kernel, is it already too late" because that's *exactly* the situation PG was written for (you're still running on your misunderstanding between signed drivers and PG). any driver once loaded and executed can do anything it wants (there's only one 'kernel mode' to use under Windows, although that'll probably change with virtualization eventually), including patching Windows kernel code, that of other drivers, kernel data, talk to hw devices, etc. what PG detects is a subset of possible driver activity, something that MS deemed 'inappropriate' for whatever reason, and as has been pointed out before, none of which will stop malicious software developers - only signed drivers may pose an issue inasmuch they'll now have to invest in a fake ID based certificate, PG can/has been/will be circumvented easily (because it's obscurity based).

      5. contrary to you claim that "PatchGuard is there to stop malicious and unknown interceptions of low-level system calls", PG doesn't actually *stop* any such activity at all, rather, it detects them after they happened (by using an obfuscated, timer based checksum routine). after all, if PG could detect the 'bad activity' as it's about to happen (say, a page fault due to a write attempt on a read-only page, such as the kernel's code), it may as well just unload the bad driver, vs. stopping the whole machine. second, what's badly written about becoming deeper ingrained into the kernel? nothing per se, there's no law that says only one company can be in control of your machine (allowing device drivers to become part of the kernel via various APIs should be proof enough that it's indeed a good thing to allow others to participate in that part of the OS). what is at stake here is the lack of proper APIs that allow the deep hooks needed for certain kinds of products. whether other products can get by without such an API is irrelevant, after all you don't actually know if those products provide the same level of security as those that are supposedly 'badly written' (hint: there is a good reason for hooking deeper and deeper in the control flow of the kernel).

  23. Mods on crack by jb.hl.com · · Score: 1

    -1 Troll?! This is 100% the truth.

    --
    By summer it was all gone...now shesmovedon. --
  24. consequences to productivity by Phantom+of+the+Opera · · Score: 1

    I have used computers bogged down with anti-virus software. My work involved a huge amount of disc access. Symantec not only slowed work down, it caused such disc grinding that scrambled discs were not uncommon where I worked. I solved that problem by disabling and banishing the anti-virus software. Yes, everything was behind a firewall and yes, if an computer was infected on the intranet, my box would have been in danger. The marginal protection of the anti-virus was not worth the cost.

    Microsoft's security is probably not so easily disabled. It sounds like Vista is already bloated and this is an additional drag on the system. Want to bet there is no off switch? What are the chances this will be on the 'safe side' and slow things down enough to where only the highest power hardware allows for productivity.

    1. Re:consequences to productivity by rs232 · · Score: 1

      "The marginal protection of the anti-virus was not worth the cost .. What are the chances this will be on the 'safe side' and slow things down enough to where only the highest power hardware allows for productivity."

      On a clients machine installing AV software slowed the machine down tremendously. I removed it, set up a standard user, set wordviewer as the default. Installed Firefox and OpenOffice. Advised the client that using IExplorer, Outlook and msWord in combination was not a good idea.

      It sounds like Vista is already bloated and this is an additional drag on the system.

      Install clean Vista with all the bug fixes .. er service packs. Install all the apps. Put all user data on drive D:. Make a backup image to a hidden partition on the harddrive. Modify the bios so this image is reloaded at every boot. Modify the bios so this can't be bypasssed and write access to the image is disabled. The Vista users can have full reign knowing that every thing is back to normal at next boot.

      If you're on a big network setup an Image server and have two cat5 sockets per desktop. One for the regular network and one for the image server. Which is exactly how the big companies do it. Then reinstall Exchange Profile... reinstall Exchange Profile... Oh I forgot what was it we did before spending all day reinstalling Windows.

      --
      davecb5620@gmail.com
  25. Mysterious advert in the FT. by RemovableBait · · Score: 1

    Has anybody here actually seen this advert for themselves? I've tried googling around for a picture of it or a link to it, but without any luck. Anyone have a link?

    I'm still amazed in some respects that McAfee got away with it. IANAL, but it sounded almost libellous to me.

    1. Re:Mysterious advert in the FT. by alienfluid · · Score: 1
  26. Remember The MS MO by mpapet · · Score: 1

    Even if MS intentionally locked up API, naysayers who trumpet a lesser known antivirus/spyware vendor need to understand that they are of little interest to MS.

    They go after the #1 money/volume producer in the category. This is the usual "big fish" strategy. Along the way, a bunch of smaller companies in the same category get eaten alive by the onslaught of lock-in and big-ticket marketing budgets. HP and Apple do the same thing.

    Symantec has the most to lose in "security". Just as AdobeMedia has the most to lose in a different category.

    DISCLAIMERS:
    1. I didn't say symantec's products were good. They've got some real stinkers.
    2. It's quite likely MS is intentionally locking the vendors out.

    RANT:
    A secure OS addresses security issues by design, from the kernel up. (ex. Linux, BSD) MS "security" is an afterthought cobbled together to appear as if it's useful.

    Regretfully, I think it will be years before many consumers get tired of the pop up's asking if their sure, or if they want to add this url to their list of okay url's. (IE on 2003 server does this for -every- URL and subdomain unless you turn it off. Now -that's- secure!?)

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Remember The MS MO by Anonymous Coward · · Score: 0

      "They've now given security vendors some of the information they want to make their products work with Microsoft's new operating system, Vista."

      should be:
      They've now given security vendors some of the information they want to make their viruses work with Microsoft's new operating system, Vista.

  27. use OneCare or my mother in-law will get upset by rs232 · · Score: 1

    I'm glad that Microsoft is being more open, and co-operating more. But I believe the real security improvements are from Microsoft, and the McAffees and Nortons of the world are becoming less relevant"

    They are becoming less relevent but not for the reasons you suggest. With Vista arriving with OneCare already installed they all will go the same way as Netscape and Wordperfect. Some of the new innovative security features in Vista are Patchlock that works by preventing third party software modifying the kernel and Code Integrity that runs check-sums on code.

    . "I installed the latest McAfee "security center" on my mother in-law's PC and the system performance was cut damn near in half. The experience has cemented in my mind that an up to date version of Windows with the latest security patches is the right way to go"

    Call me a cynic, but when someone injects a little personal anecdote to bolster an argument I suspect the whole story. It's as in the effort to convince yourself, you over compensate

    "and that these third party tools are bloatware, and resource hogs .. So why waste the time, and money on these things anyway?"

    Ah, I once saw as through a glass darkly, but now I see the light, amen. By the way, those little dot dot dots are a bit of a give away...

    was Re:Good news, but not great news...

    --
    davecb5620@gmail.com
    1. Re:use OneCare or my mother in-law will get upset by ejdmoo · · Score: 1

      Vista doesn't come with OneCare (anti-virus)

      It does come with Windows Defender (anti-spyware)

      From what I gather, they wanted to include both, but they could only include anti-spyware because there wasn't an anti-trust problem there.

  28. I'm not sure I understand the commotion here... by Toreo+asesino · · Score: 1

    Correct me if I'm wrong, but isn't patching the kernel an administrator-only function anyway?

    If this is so, isn't the principal more or less achievable with Linux by installing a modified kernel under root access?

    Either way, I wouldn't want anything tinkering with my kernel operation, so I see these API's as a negative thing - I just hope to God Windows will display some absolutely mammoth dialogue boxes should (heaven forbid) anything try and modify my kernel!

    --
    throw new NoSignatureException();
  29. Why does everyone but McAfee/Symantec manage fine? by L0neW0lf · · Score: 1

    "The otherside of the arguement is that the proposed Vista lockout would leave M$ as the only suppliers of anti malware (Ok, so Symantic don't seem to agree, but I'm stating McAfee's aguement, not mine) and we are all aware of the dangers of a monoculture, especially one run by Seatle's finest.

    What I want, if at all posible, is the choice to run which anti malware systems I choose."


    If this is such a huge problem, as Symantec and McAfee suggest, then why do Avast!, eTrust, and TrendMicro, among others, already have products that work just fine in Vista (I'm running RC2 and have tested them) without needing access to PatchGuard or the kernel?

    I'm inclined to believe that McAfee and Symantec are lazy, and want to cobble a new version of their existing products, rather than innovate and create something new. I also believe that MS opening up PatchGuard in this way makes it more vulnerable to any disgruntled programmer on Symantec or McAfee's teams, or anyone who would be prepared to divulge their knowledge of PatchGuard for a price.

    --

    Never look down your nose at others. Someday, someone is bound to see your boogers.
  30. U-Turn? by Ant+P. · · Score: 1

    Makes it sound like MS suddenly pulled its head out of its ass, which is wrong. The only U-turn they did here was because they went into a dead end street.

  31. Re:World Domination - the popup by fahrbot-bot · · Score: 1
    So MS was considering leveraging Vista for world domination...

    Oh ya! Every time an overlord wants to do something there'll be this popup requesting their admin credentials.

    --
    It must have been something you assimilated. . . .
  32. MS's genius PR move. by Quasar1999 · · Score: 1

    nah... that's not the real story...

    The real story is that Microsoft claimed to have made their Kernel completely secure... nobody can touch anything inside... so that means anything that goes wrong with it will be totally their fault. After mulling over it for a while, they then realised that they'd have nobody to blame when some malicious code got up in there and did some hefty damage. So in a genius PR move, they decided to expose an API for security vendors to be able to hook into the kernel. Now when something goes wrong in their kernel they can claim that someone leaked their API or it was exploited by hackers, and that's the reason Vista is just as insecure as previous windows... and had they not been forced to expose the API (due to anti-trust crap in from the EU) this never would have happened.

    I'm totally convinced this is the card MS is playing... Anyone who's ever worked in the security field knows that there will always be something that sneaks through... MS is just covering their ass, and setting up the ability for them to pass blame for any issues that come up when their kernel is owned yet again.

    --

    ---
    Programming is like sex... Make one mistake and support it the rest of your life.
  33. Oh Grow Up! by Anonymous Coward · · Score: 0

    Since when was creating a self-mending secure OS that has security tools a big taboo? Grow up McAfee / Symantec. Its like if Micrsofot doesn't do anything about security people blame it, and if it DOES do something, McAfee and Symantec bitch and cry. Oh grow up!

  34. n/a by me.at.work · · Score: 1

    As this does not really concern me, I'll just conclude that I am yet to run any sort of av-software on my linux installs. Thanks, I'll be gone now.

  35. Re:Why does everyone but McAfee/Symantec manage fi by 3fiddy · · Score: 1

    If this is such a huge problem, as Symantec and McAfee suggest, then why do Avast!, eTrust, and TrendMicro, among others, already have products that work just fine in Vista (I'm running RC2 and have tested them) without needing access to PatchGuard or the kernel? Maybe because Trend (I can't speak for the others) doesn't even catch viruses in XP/2000? So if by 'work' you mean they 'coexist with the OS', then yes. They 'work'. Not that I'm touting McAfee or Symantec, but they are definitely a step up from Trend.

  36. Isn't this... by griffon666 · · Score: 1

    ...McAfee screaming: "I want some piece of the cake, too?"

    Microsoft has made supplemental software (defrag, disk compression, zips, etc.) obsolete in the past by including it into the system. They will do it again.

  37. A cliche by Anonymous Coward · · Score: 0

    "working with" has become a cliche for "we tried to screw them, but they screamed out, so now we'll give you the impression we're cooperating with them when in fact we are drawing them close enough to our teat to strangle them."

    Companies: all the rights of the individual without the moral repsonsibility.

    Gengkis Kahn was "looking after his shareholders" too.