Announcement

Collapse
No announcement yet.

Nouveau Advances For OpenGL 3.2 Support

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by benjamin545 View Post
    maybe thats a big reason nobody has realy made (opensource) windows support to the current gallium codebase, because is signifigantly more likely it would be used in a propriatary driver? there wouldnt be a lot of motivation to just make that i guess.
    You can easily make such a Windows driver be GPL by making your changes be GPL. I guess the issue of driver signing is worse, IIRC MS doesn't allow unsigned drivers from Vista onwards without boot code trickery. MS wouldn't sign a driver for free, users wouldn't install something that opens their system to (more) rootkits.

    Comment


    • #12
      Originally posted by curaga View Post
      You can easily make such a Windows driver be GPL by making your changes be GPL. I guess the issue of driver signing is worse, IIRC MS doesn't allow unsigned drivers from Vista onwards without boot code trickery. MS wouldn't sign a driver for free, users wouldn't install something that opens their system to (more) rootkits.
      Theoretically, if you had the driver built and working, you could get ReactOS to sign it.

      Comment


      • #13
        That's interesting, how did they get a key? What purpose would ReactOS making drivers for genuine Windows have?

        Comment


        • #14
          Originally posted by curaga View Post
          That's interesting, how did they get a key? What purpose would ReactOS making drivers for genuine Windows have?
          They stole it: http://support.microsoft.com/kb/293818

          No, seriously, I guess they just paid for it. Verisign/Symantec are selling them.

          Comment


          • #15
            Well what the fuck. I thought they had an actually secure setup where MS vetted every kernel mode signing cert. If you can just buy one for 200$, that's just asking for rootkits.

            Comment


            • #16
              Originally posted by curaga View Post
              Well what the fuck. I thought they had an actually secure setup where MS vetted every kernel mode signing cert. If you can just buy one for 200$, that's just asking for rootkits.
              I'm sure they do vet it- which is why it's kind of pointless to try getting a cert if you plan to do malicious things. You still have to provide information, and if you're going to try to convince the certificate authority that you're real when you're not, might as well just borrow someone else's or do something that doesn't require a signed cert.

              MS can blacklist your cert, and it'll probably be a big news story if an issued code signing cert turns out to be malicious and not stolen, which will further limit the damage that can be done.

              Comment


              • #17
                1. Buy 1000 Russian identities in bulk, make sure they are spread evenly and unrelated.
                2. Buy 1000 signing certs.
                3. Even if they close one, no prob.
                4. ???
                5. PROFIT

                Comment

                Working...
                X