Slashdot Mirror


Microsoft Brands WebGL a 'Harmful' Technology

An anonymous reader writes "Microsoft has announced that it has no plans to support WebGL — a cross-platform low-level 3D graphics API designed for web use — in its future browsers, citing numerous security concerns over the technology and branding the basic principles as 'harmful.'"

66 of 503 comments (clear)

  1. Microsoft should know... by Bill_the_Engineer · · Score: 5, Informative

    a dangerous web idea when they see one. They created ActiveX.

    --
    These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    1. Re:Microsoft should know... by Anonymous Coward · · Score: 4, Insightful

      To this day it is still easy to make Word Documents that phone home to a server with user info every time they are opened. But WebGL is harmful.

    2. Re:Microsoft should know... by Anonymous Coward · · Score: 5, Interesting

      Maybe Processing has them scared as shit. Not only does it do OpenGL acceleration in a browser, but it's also open source and nearly a drop-in replacement for Flash or Silverlight.

    3. Re:Microsoft should know... by cygnwolf · · Score: 5, Insightful

      I think you hit the nail on the head there with the Silverlight comment. M$ could probably care less about Flash but they're not fond of any new players in that market.

      --
      Free Pie! The Pie is Also Evil!
    4. Re:Microsoft should know... by jasmusic · · Score: 2

      ...and are adding P/Invoke to Silverlight last I heard.

    5. Re:Microsoft should know... by beelsebob · · Score: 5, Insightful

      I'm really surprised that everyone is jumping on the "lawl microsoft security" bandwagon here, rather than the "well of course it's dangerous tech – it's OpenGL based, not D3D based... it's dangerous for MS's market share" bandwagon.

    6. Re:Microsoft should know... by Anonymous Coward · · Score: 2, Insightful

      Even a stopped clock can be right once or twice a day. Concerns for the security of this popped up on slashdot not long ago, and seemed to be accepted, but now that MS has concerns, it's a great tech?

      They should treat it like they treat all of their other insecure tech (scripting in word, html in emails with outlook, activex, silverlight that wants to do risky things) - prompt the users "Hey, do you want to do this, it's probably not a bright idea unless you really trust the source"

    7. Re:Microsoft should know... by Ephemeriis · · Score: 4, Insightful

      Yup.

      If it were WebDirectX they'd be all over it. Since it's WebGL, however, there are security concerns.

      Which isn't to say that the security concerns aren't valid... If you're giving a web page low-level access to your hardware there's certainly a possibility for abuse. But I suspect that Microsoft's concern here is more about market share than security.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    8. Re:Microsoft should know... by icebraining · · Score: 3

      Processing is Java, what does have to do with WebGL? Do you mean Processing.js?

    9. Re:Microsoft should know... by Locutus · · Score: 5, Insightful

      they created ActiveX in response to Java applets and the threat that someone else's API's could become dominant. This is normal business for Microsoft and just like how they created Direct3D to counter the spreading OpenGL API's in the 90s, WebGL is probably too much of a platform threat to support so they'll do the typical FUD thing and say it sucks, it's bad and it's dangerous while they're working on their own replacement which will solve world hunger according to their press releases and up until it actually ships with about 50% of what WebGL had when they started.

      They must do everything they know how to keep profits rolling and 3D is finally catching on so it's back to their form of business. FUD before crud.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    10. Re:Microsoft should know... by bhtooefr · · Score: 3, Insightful

      Except video drivers are about as secure and stable as IE4.

    11. Re:Microsoft should know... by Entrope · · Score: 2

      Consequently, the Canvas element is obviously harmful too.

      Video drivers do a lot more than just OpenGL. It's not clear to me that WebGL exposes any more potential security issues than anything else in a web browser.

    12. Re:Microsoft should know... by Locutus · · Score: 4, Insightful

      probably because they have a history of not doing well with security. Microsoft always goes out of their way 'calling the kettle black' when they don't want people using something they don't control so its no wonder people here mock them and point the finger back to them. Have you asked yourself why Microsoft would make such a public statement about WebGL? what is their position on OpenGL and cross platform 3D and why is that? Is Microsoft even part of the WebGL Working Group? Maybe Microsoft should be the ones STFU.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    13. Re:Microsoft should know... by CokoBWare · · Score: 4, Interesting

      Something tells me they wouldn't create ActiveX today... they've had well over a decade to learn how bad the technology actually is, and try to mitigate their mistakes with it. It doesn't surprise me they'd make comments on WebGL like this today in 2011. A lot can happen in 15 years.

    14. Re:Microsoft should know... by tepples · · Score: 2

      If you're giving a web page low-level access to your hardware

      Then your operating system is broken. A browser implementing WebGL makes calls to the operating system's implementation of OpenGL or Direct3D, which is supposed to protect each application using OpenGL or Direct3D from others. A broken 3D video driver is no different from a broken 2D video driver: both are security holes.

    15. Re:Microsoft should know... by WindBourne · · Score: 3, Interesting

      Yes, they did. However, with WebGL, they actually have a good and factual point. There ARE security flaws in it that MUST be addressed.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    16. Re:Microsoft should know... by Ephemeriis · · Score: 2

      If you're giving a web page low-level access to your hardware

      Then your operating system is broken. A browser implementing WebGL makes calls to the operating system's implementation of OpenGL or Direct3D, which is supposed to protect each application using OpenGL or Direct3D from others. A broken 3D video driver is no different from a broken 2D video driver: both are security holes.

      I guess that's true these days. I've had various games crash my 3D drivers and I just get a pop-up message stating that the driver had to be re-started.

      I'm still thinking of the good ol' days where a video driver crash meant a BSOD.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    17. Re:Microsoft should know... by TheRaven64 · · Score: 3, Insightful

      A good faith reaction would be to work with others to fix the security issues.

      The problem is, a lot of the security problems with WebGL need fixing in silicon. With most GPUs currently out there, a small bug anywhere in the OpenGL stack - a huge chunk of code that was designed to run trusted code and so optimised heavily for speed, and not really designed with security in mind - can let shader code completely compromise the system, or at least let malicious code perform a DoS attack. This isn't much of a problem at the moment, because most users don't run OpenGL code that they don't trust. You rarely see GLSL code on servers, it's either running on compute nodes (where compromising the node isn't seen as a problem because you want the user to be able to get as much out of the hardware as possible) or on machines that are basically single-user, so it's already trusted by the only user with any important data on the system.

      --
      I am TheRaven on Soylent News
    18. Re:Microsoft should know... by TheRaven64 · · Score: 2

      More likely, you have broken hardware. Microsoft's complaint is based on reality, not theory. In theory, the driver would contain no bugs and the hardware would provide enough isolation that multiple applications' command streams and memory accesses would be isolated and would be no more able to interact without operating system mediation than multiple unprivileged processes on the CPU. In practice, the hardware generally makes a half-arsed attempt at providing isolation, with numerous ways of bypassing it, and the drivers are the buggiest code in ring 0 and probably anywhere on your computer.

      These are not likely to change any time soon. Why do people choose GPUs? When was the last time you saw a GPU advertised with 'security audited drivers' or 'hardware memory protection' as features? People buy GPUs because they're fast, and writing fast secure code (and designing fast secure hardware) is significantly harder than writing code that is either fast or secure. The one that doesn't sell cards is the one that slips, every time.

      This is why most operating systems only permit one user to access the GPU at a time. From a security standpoint, there's little lost because programs can only control the GPU if they are already running on the CPU, and that means that they're code that the user trusts. If they compromise the system, it's no different from the user running a trojan - you can't protect against the user intentionally running malicious code.

      WebGL changes this. Now the web browser will run untrusted GLSL code and there's nothing that the web browser can do to make that secure. In a few years, when GPUs have proper support for MMUs and preemptive multitasking as basic features, WebGL might be possible to implement securely. At the moment, I'd be surprised if it's possible to implement it securely on more than about 10% of the systems that it's possible to implement it on.

      --
      I am TheRaven on Soylent News
    19. Re:Microsoft should know... by Shotgun · · Score: 2

      They had 20 years of UNIX to learn from before they created ActiveX. Hell, even a fool with a comp-sci degree could have told them that unfettered access to the local machine from any remote machine was brain-dead stupid. The biggest pain with Java applets was the sandbox put around it, and Micosoft was well aware of the reason for it.

      The "they didn't know it would be that bad" argument is just lame. If they didn't know, they were completely incompetent. If they knew, and chose to ignore common sense, they were criminally liable. You choose.

      --
      Aah, change is good. -- Rafiki
      Yeah, but it ain't easy. -- Simba
    20. Re:Microsoft should know... by dna_(c)(tm)(r) · · Score: 2

      The fundamental flaws in WebGL are an order of magnitude worse than almost any problem in Flash.

      [citation needed]

    21. Re:Microsoft should know... by man_of_mr_e · · Score: 2

      ActiveX is rarely used as a malware vector. Almost all malware is delivered these days from Flash, Java, PDF, and through user allowed trojans.

      The fact is, ActiveX holds no more additional threat than do Trojans, as both require end users to agree to install them. In the distant past that was not the case, but now it is and virus makers don't even bother with it anymore as it's too limiting and with IE Protected mode, it's very hard to exploit anymore.

    22. Re:Microsoft should know... by shutdown+-p+now · · Score: 2

      A browser implementing WebGL makes calls to the operating system's implementation of OpenGL or Direct3D, which is supposed to protect each application using OpenGL or Direct3D from others.

      The operating system "implements" OpenGL or D3D largely by deferring to the driver, since only that knows whether the call can be handed over to graphics hardware pretty much as is, or need to be broken down into smaller components. What's under question here is the security of the driver.

      It's not normally an issue when we're talking about basic stuff such as "draw this here polygon", but WebGL also has shaders - i.e. code! - that runs on the GPU. And it's much harder to guarantee that the existing implementation of that is completely safe - it is actually a VM of sorts, so now you're talking about sandboxing that properly, and the people who wrote it likely never considered that shaders would be coming from random unsafe sources.

      So, yes, it's fundamentally a security problem that doesn't go away just by ignoring WebGL and needs to be fixed; but you can't ask the OS to fix it (or at least not without ditching hardware acceleration altogether). The burden lies on graphics hardware manufacturers.

  2. At least silverlight is save! by cccc828 · · Score: 4, Interesting

    I am relieved that sliverlight will never support such harmful technology!

    1. Re:At least silverlight is save! by fuzzyfuzzyfungus · · Score: 2, Interesting

      Under "Extended Features":

      "Access devices and other system capabilities by calling into application COM components."

      "Call existing unmanaged code directly from within Silverlight with PInvoke."

      "Read and write files to the user’s My Documents folder, making it easier to find media files or create local copies of reports. Launch Microsoft Office and other desktop programs. Users can open Microsoft Outlook and create an e-mail message, or send a report to Word utilizing the power of Office."

      They just couldn't stay away from the convenience that ActiveX plugins' "me casa es tu casa" security model provided...

  3. They can't even spell by DavidR1991 · · Score: 3, Insightful

    "Although mitigatinos such as ARB_robustness [...]"

    Nice Microsoft, nice.

    Whilst I believe that WebGL _could_ become a vector for attack, I think this is actually "We want to push DX not GL, let's stick to NIH by saying it's dangerous instead"

  4. Re:Games on Linux means the end of the MS Empire by schnikies79 · · Score: 2, Informative

    The business world keeps Microsoft in power, not gamers.

    --
    Gone!
  5. Hate to Say This... by mrpacmanjel · · Score: 5, Informative

    The security issue is a valid question.

    In one of the links in the summary it shows that the video memory can be read and get a snapshot of the user's desktop (in the example a confidential document is viewable) - exceptionally bad. Use an exploit like this with something else means their is potential for a severe security breach.

    Then again it's early stages and I'm sure the security issues will be resolved in time.

    It's an exciting techology especially with regard to streaming games over the internet.

    Who remembers VRML???

    1. Re:Hate to Say This... by royallthefourth · · Score: 2

      It will be better since it should mean that video memory will exist in protected mode instead of real mode (since it will be part of the same protected address space as system memory), thus proscribing programs from reading data not belonging to them.

    2. Re:Hate to Say This... by sgt+scrub · · Score: 2

      I completely agree. It needs to be fixed not dumped. This reminds me of WebSockets Experiment comparing Upgrade and CONNECT handshakes. Microsoft didn't say they wanted websockets abandoned. If there isn't OpenGL support in other browsers HTML5 canvas will be better in IE than any other browser. In other words, convincing everyone OpenGL support is evil and scary when IE gets HTML5 canvas support it would put them in the front of graphically rich web interfaces.

      --
      Having to work for a living is the root of all evil.
  6. No news by The+MAZZTer · · Score: 2

    If WebGL takes off, they'll have no choice but to support it. If it doesn't, then no-one will care that they don't support it.

    1. Re:No news by Bengie · · Score: 2

      WebGL is as bad or worse than ActiveX ever was. Should be interesting.

      I've already read security blogs from reputable security professionals about how WebGL is flawed from the ground up and can allow for kernel level security issues. ActiveX at least ran as the current user, not kernel.

      I really think MS could get away with no implementing it.

  7. Microsoft should get out of browsers ASAP by GameboyRMH · · Score: 3, Insightful

    Microsoft has no business building browsers. The open architecture of the web will always conflict with IE being closed source and the EEE tactics Microsoft is constantly trying on various web technologies. In the past, Microsoft's hegemony over computer technology gave them enough influence that they might actually have a chance at "de-commoditizing" (as they say) some popular open web technologies, but that's over, they aren't the 800lb gorilla in the room anymore, they're just another dog in a fight with at least 2 other dogs (the Open dog and the Apple dog - and no they're not the same. Look at Safari's special HTML5 rendering. Familiar? Don't forget that an open web also poses a threat to Apple's mobile apps).

    By continuing to work on browsers, Microsoft is fighting a war they can't win, but like all wars this one is still harmful to the other combatants and various innocent bystanders.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
    1. Re:Microsoft should get out of browsers ASAP by pinpuke · · Score: 2

      RE: "Microsoft has no business building browsers." Well, maybe that should read... "Microsoft has only to build browsers for big business." Firefox is a pain to manage in large corporate settings. Luckily someone out there made the CCK for Firefox but it can still be a pain to manage once deployed. If you take away IE then when you make calls to businesses that serve you don't complain about the extra long call queues and slow account services. Corporate infrastructures that utilize web apps will come to a crawl while internal devs, and third party devs, scramble for fixes.

    2. Re:Microsoft should get out of browsers ASAP by GameboyRMH · · Score: 2

      Because you're destroying the client-independence of the web. If you believe in an Apple-like One True Platform future I can see how you could consider moving to clients to be a forward move, but I'd just have to disagree.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    3. Re:Microsoft should get out of browsers ASAP by chemicaldave · · Score: 2

      I'll admit that developing web apps does indeed suck. It sucks hard, but not because the actual app development sucks. That part is easy. Where I work we still do the meat and potatoes of the work with the same languages we would use for a desktop app. The only thing we use the web for is presentation and a little scripting for input -- which gets mirrored on the server anyway -- and that's the part that sucks. Mostly because browsers don't work the same way.

      But customers are always right, and if they don't get what they want they'll get it somewhere else. And customers want to access an app from -- almost -- any browser, on any computer -- or mobile device -- from any location, and that's just not practical with desktop apps.

    4. Re:Microsoft should get out of browsers ASAP by nschubach · · Score: 3, Informative

      Windows doesn't come pre-loaded with wget yet (as far as I'm aware) so it's a little more difficult:

      (Start / Run:)
      cmd
      ftp releases.mozilla.org
      (User: anonymous)
      (Pass: joe.blow@somewhere.com)
      cd /pub/mozilla.org/firefox/releases/latest/win32/en-US/
      binary
      mget *.exe
      (answer yes)
      quit
      dir Firefox*
      (Run listed program)

      Pretty sure I didn't miss anything...

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    5. Re:Microsoft should get out of browsers ASAP by paimin · · Score: 2

      How does Webkit not qualify as open?

      --
      Facebook is the new AOL
    6. Re:Microsoft should get out of browsers ASAP by GameboyRMH · · Score: 2

      Webkit is open source but Safari isn't, and Apple has shown they have no intention of following HTML5 standards, at least with Safari (although adding a ton of redundant vendor-specific HTML5 features to WebKit in the first place doesn't scream "openness"). If IE swapped its rendering engine to a WebKit fork tomorrow, it wouldn't make IE an open browser.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  8. They're right by Anonymous Coward · · Score: 5, Insightful

    You really want websites to be able to freeze and possibly crash your graphics subsystem, possibly overheat reboot your machine?

    Besides that, it's just sloppy, just like WebSQL is sloppy. It's just "hey lets compile opengl ES into our browser" or "lets compile SQLite into our browser" and neither are even half-hearted attempts at a proper standard. I originally said this as a joke, but it makes more sense to just link in the quake engine and support a "quake" tag, that takes a link to a PAK file as its .src attribute. That'd at least solve the (very real) security problems. Executing arbitrary shader code from random websites isn't a good idea.

    Aside: apparently noone else supports WebGL either. The implementations in both FF and Chrome are broken. I've had problems with multiple textures, framebuffers, the list goes on. It's simply not working yet.

    Of course, webGL would be trivial to reimplement in IE with a partial trust Silverlight plugin, which could just execute the GL natively, though that would be a much bigger security hole.

    1. Re:They're right by kyz · · Score: 2

      it makes more sense to just link in the quake engine and support a "quake" tag

      Yesterday's news, my good man - haven't you heard of Quake Live? Serve up the .pak with MIME type "application/x-id-quakelive" and Bob's your uncle!

      --
      Does my bum look big in this?
    2. Re:They're right by gmueckl · · Score: 2

      What hardware and OS did you try WebGL on? If it was Linux with poor (read: open source) drivers then there's your explanation. I've yet to see any open source driver for 3D hardware acceleration that actually works (and being able to run desktop compositing does not count - it's not even remotely an indication of how modern 3D rendering is done). I really hate to bash the open source drivers in that fashion, even though it's true.

      --
      http://www.moonlight3d.eu/
  9. It is a problem; but... by fuzzyfuzzyfungus · · Score: 5, Insightful

    It is hard to argue with the thesis that allowing a webpage to run OpenGL code on the system GPU is less secure(and places security in more hands) than not doing so. However, that seems to throw us back on the more basic problem:

    Allowing the internet to do things to your machine is dangerous. It is also among the top reasons why most people bother to own a computer. Letting pages run Javascript opens you up to vulnerabilities in your JS engine. Support for images in webpages means that a bug in any of your image format renderers(and there have been a few of these) will allow the attacker to own you. Even HTML rendering isn't safe. People from the internet are running code on your CPU, through assorted layers of indirection, virtually continually... We put up with this blatantly dangerous situation because we want the functionality.

    Other than the (im)maturity of OpenGL as something that is subject to maliciously crafted input, rather than just error by well-meaning application designers, I'm not seeing a fundamental difference. Everything that happens in your browser happens because filthy, possibly dangerous, 3rd party instructions are executed, through some number of intermediate interpreters and libraries and codecs, right on your hardware.

    Now, I can definitely see the case to be made for "You really shouldn't enable WebGL, except for websites that you would also trust enough to download and execute with admin permissions executables from, until the OpenGL ecosystem has had time to finish wetting itself from pure fear and start improving things", it is quite likely the case that the large, complex, more-focused-on-speed-than-security, mass that is GPU firmware, GPU drivers, etc is a mass of potentially serious issues, having historically been sheltered from the more hostile side of things. However, that doesn't seem fundamentally different from the state of the stack sitting on top of the CPU that was inherited from a more innocent time before widespread network malice. Ultimately, we just had to fix that; because the alternative involved not being able to do what we wanted to do.

  10. Re:Games on Linux means the end of the MS Empire by _merlin · · Score: 2

    WebGL won't deliver that. It's just going to deliver the next generation of what are currently Flash games, that run on Linux anyway (just not RMS' GNU/Linux because the player isn't free as in beards).

  11. Amazing! by Anonymous Coward · · Score: 2, Funny

    Microsoft claims competitor's technology harmful and everyone should use their safe & secure version :)

    Tune in at 11 for more news from the No Shit, Sherlock dept

  12. I tend to agree by Cigaes · · Score: 4, Insightful

    Considering that most accelerated 3D drivers for video controllers are utter crap full security flaws, or “optimizations“, as some call them, and that a video controller has full access to the system bus, and therefore to the RAM, drives, etc., I tend to agree that letting anyone on the web transparently send possibly crafted data to the 3D driver is, from a security point of view, a rather dubious idea.

  13. Re:Games on Linux means the end of the MS Empire by Elbereth · · Score: 2

    Don't underestimate gamers or the gaming industry.

    If every gamer switched to Linux, you'd see Windows become as irrelevant as OS/2, which also had a sizeable installed base in the corporate world, or Mac OS, which had a huge installed base in education. Corporate users hardly ever upgrade, and many of their biggest apps have already been ported to at least one other OS, if not more. In the corporate world, they cater to the customer's needs and desires. In the home market, they dictate to the market.

  14. It is true. It is harmful. by 140Mandak262Jamuna · · Score: 2, Informative

    The question is what is harmed. In this it looks like it is harmful to Microsoft's market share and profits.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  15. Can't trust MS's opinions by bzipitidoo · · Score: 5, Interesting

    What they mean by "security" is not what everyone else means. Security is just the biggest argument in the FUD arsenal. They mean control, to secure their bottom line.

    For 25 plus years, that's been MS's real goal. They tried to kill off Ogg Vorbis over "insecurity"-- the supposed insecurity of no built in DRM. Security was probably one of the arguments they used to push OOXML over ODF when they were trying to maintain their file format lockdown. Talk about an outdated tactic, but then, MS has been slipping for some time now. They would have tried the old line suggesting no one would maintain the software without a large company backing it, another FUD favorite, but even they must see no one would buy that any more. And yet, they can't see the uselessness of the entire Windows Genuine Advantage program.

    What specifically could they be trying to promote in place of webGL? Silverlight?

    --
    Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
  16. WebGL bugs already demonstrated by lseltzer · · Score: 4, Informative

    Context Information Security has already tested WebGL implementations and demonstrated the sorts of bugs Microsoft warns about. In fact, it looks like maybe they got a tip about it from Redmond, but they do demonstrate it, and Mozilla has acknowledged the bugs for Firefox 4.

  17. For once don't bash M$, read the article instead by amn108 · · Score: 5, Insightful

    An essential factor in security is trust. You cannot trust a website you have never seen before to load code of its choosing to be executed on a driver supplied to you by third-party which may or may not have a stellar security record themselves. Especially when "modern" operating systems like Linux run drivers as part of their monolithic kernel and so probably WILL crash when the website code messes up the driver runtime. Windows is heading in all the right directions moving their graphics driver supporing infrastracture out of the kernel into userspace. At least that way, your entire OS won't crash bringing everything down with it. At worst, smart people will figure out doing their favourite things - injecting their code through good old buffer overflows and what not.

    This is what you get when you pair three poorly isolating systems to eachother. Microsoft may have done a lot of their own mess during the years with their products' security, but for once, they are right. Not the least, becaue they probably have gotten so much flak for it they finally decided enough is enough and started going by security checklist documets and automated programs that eliminate all the obvious bugs. I sincerely hope they're getting it, for I for one am tired of hearing everyone bash them. Look into your own backyard when you get 20 million lines of code running wildly on a several hundred million computers around the globe, thanks. Or reduce your SLOC, but that, again, is another discussion.

  18. Re:Their concerns do make sense by obarthelemy · · Score: 2

    maybe one solution would be to create an intermediary WebGL driver in userland with lots of security checks. Would that still be worth it, performance-wise

    --
    The Cloud - because you don't care if your apps and data are up in the air.
  19. Don't you just hate it by lorax · · Score: 4, Interesting

    Don't you just hate it when Microsoft takes the high road on security and raises some valid points. We've been through this scenario a bunch of times where some class of programs that used to only be used by local programs became accessible on the web and suddenly there is a rash of exploits (jpeg and pdf come to mind), I'd rather not go through it again.

    That said, I think Microsoft laid out the problems with enough specificity that they could be addressed.

  20. Re:Games on Linux means the end of the MS Empire by Quarters · · Score: 2

    End of story.

    Linux gaming is a niche idea for a niche OS (-Linux on desktops for the masses. I know Linux in the enterprise is big). Microsoft isn't losing any sleep over the idea of Linux gaming going mainstream.

  21. Re:Good advise! by balbord · · Score: 2

    Good recommending!!!

    --
    "If I have been able to see so far, It is because I went out and bought a damn binoculars" - Ze da Esquina
  22. Re:Games on Linux means the end of the MS Empire by Merk42 · · Score: 2

    Hypothetical:

    Developer: I'm going to make a great game for Linux, it's closed source.
    Linux Community: closed source? BAH! No thank you, Linux is about Freedom man,
    Result: Game does not become the widely adopted killer game converting people to Linux

    Developer: I'm going to make a great game for Linux, it's open source.
    Windows Community: Open source? Cool! *ports game to Windows*
    Result: Game does not become the widely adopted killer game converting people to Linux

  23. Re:For once don't bash M$, read the article instea by NatasRevol · · Score: 5, Insightful

    Can you explain to me, from your security point of view, how this is any different than using flash or silverlight on the web? Using those technologies, you're loading code form a website to be executed on a driver supplied to you by a third party which does NOT have a stellar security record.

    --
    There are two types of people in the world: Those who crave closure
  24. Re:Good advise! by iserlohn · · Score: 2

    You're right. Microsoft has done lots for the information security industry by selling a desktop and desktop derived server OS that has an security model that is insecure by default.

    Just because we're Microsoft bashing, doesn't mean we don't have a point.

  25. We missed an opportunity. by SanityInAnarchy · · Score: 2

    You are flat wrong on a few points:

    It's not the access to high performance video drivers, as they don't exist.

    Bullshit. The nVidia drivers benchmark comparably on Linux and Windows. ATI might still be worse.

    And this is where I think the Linux community missed an opportunity. Back when Quake 3 was the hot new shit, and was how benchmarks were done, someone benchmarked Windows vs Wine vs native Linux. They found the performance went roughly in that order -- Quake 3 was faster under Wine on Linux than it was on Windows, and the native Linux port was faster still.

    So you're right that gamers need something better -- but we had that. We had a significant performance advantage for awhile, and that was out of the box. This was also back when desktop GUI environments were still fairly resource-intensive things, so you could get even more performance out of killing off your entire GUI and running just that game in its own X server (with no other X apps) -- and PC gamers were always looking for little tweaks like that to give them an edge.

    None of these things are true anymore. Linux is no longer a performance edge by itself, and whatever performance there is to be gained isn't really going to make your framerate go up. That's where it's even comparable, because since then, Direct3D got better and much more popular. There was a point where OpenGL was just faster and better, when games would ship with multiple renderers (OpenGL, D3D, and software) in case one happened to be faster or better supported on your machine, but as I remember, after a certain point, Half-Life always ran faster under OpenGL. But again, things just aren't comparable anymore -- too many games are D3D only.

    That, and there are so many new features (all of them high-performance) that you're not likely to get the best experience out of open source drivers, so if you're stuck with ATI, Linux is going to be significantly worse than Windows, even for an identical OpenGL game.

    I feel like if we'd kept that edge just a bit longer, we might've seen a lot more start to change. I played an MMO with a friend, and aside from his Norton Anti-Virus always interrupting his game, I could run it windowed (via Wine hacks) while he couldn't -- and eventually, when the game's auto-patching system not only worked on Wine but not his Windows, but we "patched" his copy by pulling files out of my Wine copy, he was convinced -- a few months later, I set him up with Linux. That kind of thing happens much less often these days.

    Anyway...

    It's not the access to ubiquitous and non-finicky audio systems, as they don't exist.

    I don't know, ALSA pretty much met that goal, and I haven't had issues with Pulse since I switched to it, though I did wait awhile before making that switch. For a gamer, though, I don't see needing anything more than ALSA. For that matter, I also don't see a game developer needing to use anything more than OpenAL.

    You are, however, almost right about this:

    The gamers need something better than what they have if they are going to move away from their current situation and negate their library of games... The majority of game companies won't make games on Linux until there is a market, which doesn't exist.

    Linux support is still a very good idea for a new indie game. And if anything, I'd expect it to be easier to build a portable game than other kinds of applications -- the game's entire interface with the OS can be reduced to OpenAL, OpenGL, the filesystem, and the network. OpenAL and OpenGL are already ported, and the filesystem is almost automatically portable if you don't assume stupid things (don't add a bunch of backslashes; forward slashes work on Windows, too).

    But then, indie developers can't really afford to exclusively support Linux, which means the game itself isn't an inc

    --
    Don't thank God, thank a doctor!
  26. Re:For once don't bash M$, read the article instea by amn108 · · Score: 2

    Sure, gladly. You have half a point - indeed systems that communicate invariably affect and potentially may compromise each other. That's a fact, which can also be seen in any other field of engineering. Like they say, the only secure system is the one that is not connected [to the Internet]. But since we do connect systems, the factor here is the interface cross-section. Flash Player and Silverlight, ok I won't speak for Silverlight because I never said it is much better than WebGL, so yeah - Flash Player uses fewer and more benign interfaces than WebGL - it certainly does not execute that much GPU code, in fact most of the SWF code interpreted by it is run on your average CPU eventually, and the parts that are abstracted by Windows, again, run in USER MODE - font rendering, printer, mouse, sound etc - hence my choosing of the word "more benign". If Flash Player crashes, your OS doesn't (hopefully this includes Linux based OSes.)

    Granted, Flash Player DOES now expose the GPU indirectly through its that-3d-rendering-api-codename-i-dont-remember-the-name-of, and indeed it's much of the same dilemma as with WebGL - untrusted code programming your graphic driver has the same chance of crashing your box as those fancy desktop 3d games that give you BSOD or Linux kernel panic.

    To sum it all up: it's the interface cross-section that matters and the domain of the code the interfaces abstract.

  27. WEBGL makes the drivers more visible. by leuk_he · · Score: 5, Insightful

    Anything that gets drawn in a browser is controlled by the browser. After 10 years of failure that part mosty is sandboxed into safety. The Code of web gl has almost complete access to the video driver. The video driver was never written for security. Speed and picture quality were the number one priorities. Since the application that ran them was alrady a local application that had a lot of access security was not really an issue. The application that access the drivers did not have to be checked extra, because they had already full access to the machine.

    Display drivers are complex software, that might show the same level of vulnerabilities that plagues the browser.

    However a subset of WEBGL that is more easy check could be implemented safely i think.

    1. Re:WEBGL makes the drivers more visible. by TheRaven64 · · Score: 4, Informative

      You seem to have no idea of how a modern graphics stack works. Canvas drawing is mediated by the browser. You do something like lineTo() from JavaScript. The JavaScript code then translates this into a call to a host OS API call. The call comes from the browser and its arguments are checked by the browser for sanity, then they're checked by the graphics stack, then they're checked by the driver. In contrast, WebGL takes a blob of GLSL code and a blob of data and passes it straight to the driver. The browser can try checking this, but it doesn't really know what to look for. The drivers then compile this C-like code, using a compiler that wasn't designed for security. Then they chuck it over the bus and the card (which may have DMA access to all of system memory) runs it. Comparing the two is like comparing a telephone with someone dictating messages and a fax machine: you're only likely to be goatse'd by one...

      --
      I am TheRaven on Soylent News
  28. Re:Games on Linux means the end of the MS Empire by zeroshade · · Score: 2

    Actually, lack of games on Linux is one of the driving forces for keeping a large swath of people from switching.

  29. Re:Crap. by DaveV1.0 · · Score: 2

    Solution: Stop using the browser for things that are not browsing. Stop using the browser as an OS inside an OS. If your website needs OpenGL, you are doing it wrong.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  30. Why is WebGL even needed? by DaveV1.0 · · Score: 2

    Seriously, why is it needed? Why don't developers just write their own UI instead of trying to push everything into the browser?

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  31. Re:Games on Linux means the end of the MS Empire by pandrijeczko · · Score: 2

    I don't know you from Adam and therefore don't care that you're having a bad day and feeling a bit grumpy with the rest of the world either.

    But just for the record, my computer knowledge started with programming on Commodore Amigas and doing system support work during mid- to late-80s on DEC PDP-11s running RSX-11 and IBM x86 servers running SCO UNIX - so I actually worked on UNIX before I ever even touched a Windows PC. And by the immaturity of your comments, that was probably around the time you were in nappies...

    I've also run Linux for nigh-on 18 years, I was a Red Hat Certified Engineer in 2000 and my full-time job is doing security analysis and hardening of Linux-based telecoms servers - believe it or don't believe it, I don't care.

    But I'm not a zealot. A computer is a tool and you use the best tool for the job. Period.

    --
    Gentoo Linux - another day, another USE flag.