Slashdot Mirror

← Back to Stories (view on slashdot.org)

Fix the Bugs, Secure the System

Posted by michael on from the crunchy-on-the-outside dept.

LiquidPC writes: "OpenBSD's Louis Bertrand has put his MUSESS 2002 presentation online, entitled Fix the Bugs, Secure the System. Does an overview of OpenBSD, then explains Format String Ugliness, Buffer Overflows, The Wrong Way to Fix Overflows, along with numerous other things."

5 of 334 comments (clear)

  1. Re:Buggy by Jerf · · Score: 5, Funny

    Just searching for 'OpenBSD Bug' on Google Groups retrieves over 20,500 queries.

    Searching for "Brian bug" on Google shows 441,000 hits. Clearly you're 20 times buggier then OpenBSD, so I wouldn't be slinging implied accusations around.

  2. Look very closely at that picture by Anonymous Coward · · Score: 3, Funny

    The skeleton in front just left of the middle? The one with a beak and wings?

    That was a penguin. :-)

  3. Fix the bugs? by Jucius+Maximus · · Score: 3, Funny

    Why is it that when MSFT does something like stopping to fix bugs and secure systems, we make fun of them, but if it's BSD we look at it as something we can learn from?

  4. Re:The only remaining wish... by Arandir · · Score: 4, Funny

    ask yourself why strlcpy() still isn't part of glibc

    Because if it isn't invented at GNU they won't use it?

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  5. Re:Security: start in education by Kidder · · Score: 4, Funny

    A professor's code is not necessarily the best code in the world. I had a professor who used gets() in the example code he gave us and I had to explain the difference between fork() and vfork() to him (well, not much of a difference anymore...) I had another professor whose code had a MAJOR memory leak in it. I politely emailed the professor about it and he replied to the entire class with the memorable phrase: memory leaks are not important anymore.