Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: A New Round Of OpenSSL Vulnerabilities Discovered

  1. #11
    Join Date
    Jun 2011
    Posts
    921

    Default

    Quote Originally Posted by log0 View Post
    LOL. This report is actually an example of why open source is more secure. You have here multiple independent developers looking at the source and reporting bugs, and helping fix them. Would the same be possible with a ssl blob?
    There's that, and if it's open source, used widely enough, and you screw up as badly as openSSL has, Theo will come and fork your project to fix all of it's brain damage.

  2. #12
    Join Date
    Mar 2013
    Posts
    247

    Default

    Quote Originally Posted by gamerk2 View Post
    So, can we put to bad the argument of "OSS is by nature more secure" argument now?
    You need to learn three things about computer security:
    1) Just because someone slapped a "secure" label on something doesn't mean it's secure - whether it's open-source or proprietary.
    2) If security was a boolean it would always evaluate to false. "More secure" doesn't mean "100% secure". And nothing is 100% secure. The question is the price of a successful attack in terms of money (computing resources), time and effort. If it's too costly it'll almost never happen. And almost never is considered good enough.
    3) Heartbleed is overrated. It's just a bug, one out of many, that got blown way out of proportion by journalists. No security expert has ever seriously believed SSL to be impenetrable. But when the alternative is using plain text for credentials and unencrypted streams for data, it's a no-brainer that SSL is better than nothing.
    Last edited by prodigy_; 06-05-2014 at 02:24 PM.

  3. #13
    Join Date
    May 2013
    Posts
    533

    Default Looks like real time chat is biggest exploitable use of this against end users

    I looked at these, it looks like most of these are denial of service attacks, but one permits forcing the use of weak keys in https traffic and another permits arbitrary code execution against a machine engaged in real time chats (DTLS seems to be used mostly for this sort of thing according to what I could quickly dig up).

    If you don't do realtime chat and rely on GPG when you need strong encrption, this won't likely hurt you. I only trust https to keep my ISP and various wifi hotspots from logging copies of my work, I do NOT trust it against the NSA or even the FBI as it has too high a target profile.

    Never bank online with any computer, never shop online except with prepaid credit cards whose entire balance is expendable. Don't bet your savings on being a better hacker than every last person out there who puts food on their table by black hatting!

  4. #14
    Join Date
    Dec 2011
    Posts
    2,047

    Default Turtles all the way down

    I guess now after the Heartbleed vulnerability in OpenSSL, lots of security researchers are going to examine OpenSSL.

    I wonder if its turtles all the way down with new vulnerabilities exposed every week.

  5. #15
    Join Date
    May 2014
    Posts
    8

    Default Private disclosure

    Some days ago the bugs had been privately communicate to a list of linux distributions.

    This is the timeline:

    http://seclists.org/oss-sec/2014/q2/466

  6. #16
    Join Date
    Apr 2010
    Posts
    20

    Default

    Quote Originally Posted by erendorn View Post
    A closed source project with as many developer as OpenSSL (ie, very small project), would never have ended up in as much machines as OpenSSL did, even if it was free. Mostly because it would be neither auditable nor accountable, in other word, in a sense, too insecure.
    As such, it's quite difficult to reach a comparative conclusions when comparable non-OSS projects don't exist.

    Bullshit alaaaaaarm.

    You being paid by Microsoft or by Apple?

    Open source = auditible & accountable. You can always trace the path one has made an error, and nobody will deny it or play the blame game as happens most of the time in most multibillion corps.

    - Oh, is that a security hole? I'm so sorry, must have been something the intern introduced. Wasn't my fault mr. chief executive.
    - Is that so? Well, ok then. We'll sell it as a feature, not a bug.

    Once again, bullshite.

  7. #17
    Join Date
    Sep 2013
    Posts
    125

    Default

    Quote Originally Posted by arabek View Post
    Open source = auditible & accountable. You can always trace the path one has made an error, and nobody will deny it or play the blame game as happens most of the time in most multibillion corps.
    Try reading that quote again before getting your panties in a twist. That's pretty much what erendorn said about accountability.

  8. #18
    Join Date
    Apr 2010
    Posts
    20

    Default

    Quote Originally Posted by tuubi View Post
    Try reading that quote again before getting your panties in a twist. That's pretty much what erendorn said about accountability.
    Right, i must have been really tired or drunk to not notice that. Or both. Sorry!

  9. #19
    Join Date
    Sep 2012
    Posts
    678

    Default

    Quote Originally Posted by tuubi View Post
    Try reading that quote again before getting your panties in a twist. That's pretty much what erendorn said about accountability.
    Quote Originally Posted by arabek View Post
    Right, i must have been really tired or drunk to not notice that. Or both. Sorry!
    flamers gotta flame!

    np

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •