Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Microsoft's many eyeballs and the security development lifecycle

Microsoft's many eyeballs and the security development lifecycle

Scheduled Pinned Locked Moved The Lounge
comsecurity
6 Posts 5 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • _ Offline
    _ Offline
    _ghassen_
    wrote on last edited by
    #1

    http://blogs.msdn.com/shawnhernan/archive/2010/02/13/microsoft-s-many-eyeballs-and-the-security-development-lifecycle.aspx[^] Excellent!

    S L H 3 Replies Last reply
    0
    • _ _ghassen_

      http://blogs.msdn.com/shawnhernan/archive/2010/02/13/microsoft-s-many-eyeballs-and-the-security-development-lifecycle.aspx[^] Excellent!

      S Offline
      S Offline
      Shog9 0
      wrote on last edited by
      #2

      http://blogs.msdn.com/shawnhernan/archive/2010/02/13/microsoft-s-many-eyeballs-and-the-security-development-lifecycle.aspx:

      You might argue that the mere fact that Coverity can do this work is just another set of eyeballs. But I reject that argument entirely. This is a government subsidy to go do some hard and useful work, not a magic property of the fact that these are open source projects. The real beneficiaries of the subsidy are not Coverity (who is providing a fine service), but other companies whose business model is primarily about services and not software. I think those companies are big enough that they ought to be able to do some of this themselves.

      Or in other words, the fact that F/OSS software can be independently analyzed is irrelevant at best and an insidious subsidy for service companies at worst. :rolleyes:

      J 1 Reply Last reply
      0
      • S Shog9 0

        http://blogs.msdn.com/shawnhernan/archive/2010/02/13/microsoft-s-many-eyeballs-and-the-security-development-lifecycle.aspx:

        You might argue that the mere fact that Coverity can do this work is just another set of eyeballs. But I reject that argument entirely. This is a government subsidy to go do some hard and useful work, not a magic property of the fact that these are open source projects. The real beneficiaries of the subsidy are not Coverity (who is providing a fine service), but other companies whose business model is primarily about services and not software. I think those companies are big enough that they ought to be able to do some of this themselves.

        Or in other words, the fact that F/OSS software can be independently analyzed is irrelevant at best and an insidious subsidy for service companies at worst. :rolleyes:

        J Offline
        J Offline
        Joe Woodbury
        wrote on last edited by
        #3

        That's not his point at all. He's saying that what Coverity is doing is not a property of something being open source, but the result of a paid contract. (I'd argue that independent analysis is largely irrelevant anyway since source code analysis is primarily a tool to help identify potential problems--in the end, what matter is if the actual software exhibits a behavior and that can be tested on all published software, open source or not.)

        S 1 Reply Last reply
        0
        • _ _ghassen_

          http://blogs.msdn.com/shawnhernan/archive/2010/02/13/microsoft-s-many-eyeballs-and-the-security-development-lifecycle.aspx[^] Excellent!

          L Offline
          L Offline
          lepipele
          wrote on last edited by
          #4

          In article:

          "A million monkeys banging on a million keyboards will eventually produce Twelfth Night."

          "We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true." - Robert Wilensky

          1 Reply Last reply
          0
          • J Joe Woodbury

            That's not his point at all. He's saying that what Coverity is doing is not a property of something being open source, but the result of a paid contract. (I'd argue that independent analysis is largely irrelevant anyway since source code analysis is primarily a tool to help identify potential problems--in the end, what matter is if the actual software exhibits a behavior and that can be tested on all published software, open source or not.)

            S Offline
            S Offline
            Shog9 0
            wrote on last edited by
            #5

            Joe Woodbury wrote:

            That's not his point at all. He's saying that what Coverity is doing is not a property of something being open source, but the result of a paid contract.

            Source analysis - either automated static analysis or expert review - by definition requires access to the source code. That it also requires time and effort (== money) is irrelevant - you could have time, money, and the motivation to analyze a particular bit of software and without access to the source still be prevented from performing such analysis. Hence Microsoft's release of key source to Gov't agencies under limited circumstances. See also: various recent court cases requesting access to the source code for breathalyzers for the purpose of analyzing them for defects that would affect their accuracy/reliability.

            Joe Woodbury wrote:

            I'd argue that independent analysis is largely irrelevant anyway since source code analysis is primarily a tool to help identify potential problems--in the end, what matter is if the actual software exhibits a behavior and that can be tested on all published software, open source or not.

            Well... black-box testing can be useful, but comprehensive testing isn't always feasible (it may be difficult to control inputs, or impractical to test all input combinations). Still, one of the better points he made was the real-world utility of techniques like fuzz testing in identifying problems.

            1 Reply Last reply
            0
            • _ _ghassen_

              http://blogs.msdn.com/shawnhernan/archive/2010/02/13/microsoft-s-many-eyeballs-and-the-security-development-lifecycle.aspx[^] Excellent!

              H Offline
              H Offline
              Hans Dietrich
              wrote on last edited by
              #6

              I have to admit, "studliness ranking" sounds better than "man points".

              Best wishes, Hans


              [Hans Dietrich Software]

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups