Slashdot Mirror


How Does Heartbleed Alter the 'Open Source Is Safer' Discussion?

jammag writes: "Heartbleed has dealt a blow to the image of free and open source software. In the self-mythology of FOSS, bugs like Heartbleed aren't supposed to happen when the source code is freely available and being worked with daily. As Eric Raymond famously said, 'given enough eyeballs, all bugs are shallow.' Many users of proprietary software, tired of FOSS's continual claims of superior security, welcome the idea that Heartbleed has punctured FOSS's pretensions. But is that what has happened?"

582 comments

  1. Leaked by codenomicon by symbolset · · Score: 4, Interesting

    Which is run by a former Microsoft executive who was in charge of security. I guess he can gloat about being personally responsible.

    --
    Help stamp out iliturcy.
    1. Re:Leaked by codenomicon by Thiarna · · Score: 5, Interesting

      I had to dig for direct connections between Codenomicon and Microsoft, but the chairman of the board seems a fairly strong link. The way Codenomicon have behaved in this has seemed reckless, I've never seen a bug so heavily marketed. The stats floating around initially seem to be way off the mark - to begin with quotes were of 66% of web servers being affected, later revised to 17% running affected versions. Both these numbers look too round to be anything other than made up.

    2. Re:Leaked by codenomicon by msauve · · Score: 4, Insightful

      Gloat? About what? This only provides proof of the benefits of open source - a significant flaw was discovered, which is exactly the claimed advantage - the more eyes, the better.

      Anyone who would claim that proprietary software is somehow more secure is making a huge leap - there are only a few eyes, if any, looking for unreported issues - so there may be even more serious issues which have existed for much longer, which only a few bad guys know about. If MS or anyone else thinks that their proprietary SSL implementation has no security breaches, let them put a guarantee with full financial liability behind that thought.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    3. Re:Leaked by codenomicon by Anonymous Coward · · Score: 0

      Yeah, people seem to not understand that catching a bug is this in action.

    4. Re:Leaked by codenomicon by Anonymous Coward · · Score: 0

      More concerned with the millions of Android phones running 4.1.1 (including my own) that are known vulnerable with no patch yet.

    5. Re:Leaked by codenomicon by Gunboat_Diplomat · · Score: 2

      Gloat? About what? This only provides proof of the benefits of open source - a significant flaw was discovered, which is exactly the claimed advantage - the more eyes, the better.

      But it wasn't found by eyes, in the source. It was found by automated testing tool that would have just as easily found it in closed source.

    6. Re:Leaked by codenomicon by Anonymous Coward · · Score: 0

      Gloat? About what? This only provides proof of the benefits of open source - a significant flaw was discovered, which is exactly the claimed advantage - the more eyes, the better.

      But it wasn't found by eyes, in the source. It was found by automated testing tool that would have just as easily found it in closed source.

      For all the eyes it went undiscovered for 2 years...

  2. Wat? by Anonymous Coward · · Score: 5, Insightful

    In the self-mythology of FOSS, bugs like Heartbleed aren't supposed to happen when the source code is freely available and being worked with daily.

    False. Bugs can and do happen. However, what can also happen with open source software is that entities other than the group working on the project can find bugs. In this case, Google found the bug. If the source were not open, maybe it would have never been officially recognized and fixed.

    1. Re:Wat? by Anonymous Coward · · Score: 0

      On the other hand, Google is a prime example of a customer that could well be doing its own audits and examination of the software regardless, they aren't operating out of a garage, and probably have the source to any number of proprietary systems.

    2. Re:Wat? by tysonedwards · · Score: 5, Interesting

      It is a double edged sword. Because one can see the code, there is visibility into the process. Because OpenSSL is such a common tool and is arguably vital to the function of the Internet as we know it, this sort of a bug really is one of those "worst case scenarios" PR wise, as opposed to being cleanly swept under the rug as is possible in the case of many Closed Source 0-day vulnerabilities.

      The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility. And the argument "Open Source is inherently safer" has been very heavily damaged by Heartbleed and now ranks up there with "Macs don't get viruses" and "Women are worse drivers".

      If this happened in Microsoft, Adobe or Oracle Land this would be "yet another 0-day" and largely ignored by the public. Because it is in an area with such a vocal group of people spouting "Impenetrable" for decades, it all of the sudden becomes quite newsworthy in a way that "yet-another-remote-code-execution-with-privilege-escalation-in-Acrobat-Reader" vulnerability doesn't.

      And if you doubt any of this for a moment, have you ever heard the name of the developer who was at fault for introducing a bug into Flash on the local news? Now did you hear the name "Robin Seggelmann" in connection to Heartbleed?

      --
      Thirty four characters live here.
    3. Re:Wat? by Anonymous Coward · · Score: 1

      And yet, closed source bugs are found and exploited just as effectively, but rarely fixed as a result.

    4. Re:Wat? by clarkkent09 · · Score: 2, Insightful

      True, but it is also easier for malicious people to find vulnerabilities when they have the source code. There are other disadvantages, a broad developer base allows vulnerabilities to be deliberately introduced more easily and it's harder to enforce standards etc.

      I searched and couldn't find a good study or any reliable evidence either way. There is good and bad open source software and there is also good and bad commercial software. Posting with absolute certainty that open source is more secure will get you modded up around here but I would like to see some evidence.

      --
      Negative moral value of force outweighs the positive value of good intentions.
    5. Re:Wat? by F.Ultra · · Score: 4, Insightful

      You seriously think that black hats bother with reading millions of lines of code in the hope of finding an exploit when all they have to do is play with the data sent to services/applications and see if it misbehaves. Which is why exploits are equally found among closed and open softwares.

    6. Re:Wat? by Anonymous Coward · · Score: 1

      Google wasn't the only one to find the bug, there was another independent discovery within 24 hours. What this means is it's functioning EXACTLY as intended. Large open source projects of high importance are getting many independent set of eyes on the problem and real, serious, nightmare inducing exploits are getting found and FIXED rather than exploited for extended periods of time.

    7. Re:Wat? by clarkkent09 · · Score: 2

      Well, you wouldn't start by reading millions of lines of code but it certainly helps to have access to it. Especially for people with serious resources, governments etc.

      --
      Negative moral value of force outweighs the positive value of good intentions.
    8. Re:Wat? by aliquis · · Score: 1

      Also of course regardless of whatever the product is open source or propitary and paid for you can't from that draw any conclusions about the skills of the individual who have written the code but if it's a high prestige brand/project I guess chances are higher they have been more picky than if it's some small rather unknown one individual thing.

      The idea was to make it a point that you for instance may not want to trust the individuals who roll their own packages for your Linux distribution of choice and download from random page or trust THISISTHEBEST___INTHEWORLDBUTITSNOTAWELLKNOWNPRODUCT from someone rather unknown for instance.

      But I guess it all fails with this being OpenSSL which I feel is a high prestige / well-known product and where safety should be important and still it simply failed.

      Somewhat related I noticed that Fedora run OpenSSH by default and with the defaults (PermitRootLogin yes) and listening to the whole world which imho is completely retarded and I don't see why one would want to have that the default. I guess it could be argued that "Hey, someone may need that to access the computer after installation!" but I guess in that case let them set that up in the installer or make a special installation with such settings and really, do they use the regular installer but have no keyboard and screen hooked up so they can turn it on if they want to afterwards?

      It did seemed like none of the BSDs ran sshd by default. Which imho is much more reasonable. Whatever to allow root or not as default I guess one could argue on. Since the OpenSSH default is PermitRootLogin yes I guess it make some sense to keep that the default rather than changing it but I guess there has been some argument about that one too. A way of rescuing a poorly setup installation? Possibly better (imho) to just force people to redo it correctly if they mess up and really need some way to get in.

      And regarding trusted source code, prestige projects and whatever anyone is actually watching the code and finding the bugs. What happened with the claim about some backdoor in was it OpenBSD or OpenSSH? Was it just bullshit or something real? I guess the first question would be whatever anything/it was actually found, because without that the answer would of course be "we don't know" =P

      Guess I'm off-topic enough to not take it even further so I'll stop there :)

    9. Re:Wat? by alex4u2nv · · Score: 3, Insightful

      Correct -- I could imagine that there are lots of "heartbleeds" in closed source software that can and will be exploited. Whether it becomes public and puts pressure on the development staff to fix, is another story.

    10. Re:Wat? by aliquis · · Score: 0

      Is this happened a closed source product I guess the question whatever it would had been on purpose or not and whatever any closed source product could be trusted would had been way steamier here on /.

    11. Re:Wat? by Anonymous Coward · · Score: 1

      Are you implying that closed source software is not exploited often, or that open source software is often exploited?

      Either way, I hope you're joking. You can't possibly be serious.

    12. Re:Wat? by Anonymous Coward · · Score: 1

      If you bring governments in, then closed source isn't really any different. The governments have eyeballs on those too, but the community at large does not. Yeah, maybe the Chinese government can't read Microsoft's code and the US government can't read Huawei's, but I'm sure they have people trained in assembly and pattern matching of assembly code to what compilers output for certain sequences of code to "mitigate" that. I think I'd enjoy one of those jobs...

    13. Re:Wat? by Arker · · Score: 4, Insightful

      "The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility."

      No, just no. No one with any sort of a clue ever argued these issues cannot happen with Free Software. It's good practice, it helps, but it's no silver bullet. That's just as true as it ever was and this news in no way contradicts that.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    14. Re:Wat? by RabidReindeer · · Score: 2

      All source is open if it's worth it to someone.

      That's what disassemblers are for.

      I reverse-engineered the old Microsoft assembler for CP/M to give it an advanced feature it lacked and did it strictly on my own time and for my own private benefit (pre-DMCA).

      You can be certain that open or closed, SOMEONE whose business is penetrating security has people dedicated to ensuring that there's source code to pore over for exploits.

    15. Re:Wat? by Anonymous Coward · · Score: 1

      eh? Something can be exploited even if it is closed source. The worst part of that is, it won't be officially recognized and fix, heck people potentially won't even know about it to recognize and fix it.

      A lot of companies hire contractors and consultants working on their closed source, proprietary code. Any of those plus any existing employee can stumble on it and decide to keep the information for themselves either to exploit or sell it. Given the closed source nature, it could be a long time before another person with enough integrity stumble on it and report it. Even then, it may not be officially recognized and can easily be hand-waved away by execs hiding behind profit and "close source".

      Open source doesn't prevent the problem, it provides visibility and that forces people's hand to fix it quickly. Shit happens whether it is closed or open source. The only difference is the shit is visible and gets cleaned rapidly in the latter.

    16. Re:Wat? by Anonymous Coward · · Score: 0

      real, serious, nightmare inducing exploits are getting found and FIXED rather than exploited for extended periods of time.

      So how would you explain serious bugs like heartbleed existing for TWO YEARS (and being exploited for who knows how long by blackhats) before being detected? Given the widespread use of the software, this whole "many eyes" argument pretty much falls on its face. It is patently clear that in the open source world, large user-bases means nothing in terms of eyes looking at code. This is not open source functioning "EXACTLY" as intended.

    17. Re:Wat? by lister+king+of+smeg · · Score: 2

      yes but they would not necessarily be able to patch the closed code

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    18. Re:Wat? by Anonymous Coward · · Score: 0

      The biggest impediment to any patches is getting people aware of the need and them being comfortable doing so with their systems, rather than getting a patch.

    19. Re:Wat? by Fallen+Kell · · Score: 1

      No one has ever been spouting "impenetrable", ever... What they spout is that anyone can find it, and anyone can fix it.

      The only people who have come close to spouting impenetrable have been OpenBSD when using their customized versions of C/C++ libraries, which OpenSSL did not use...

      --
      We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
    20. Re:Wat? by Livius · · Score: 2

      "Open Source is inherently safer"

      Yes.

      Open source absolutely safe?
      No.

    21. Re:Wat? by Anonymous Coward · · Score: 0

      The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility.

      Well, maybe a few people have, but most have been using the "many eyes" argument. This is on its face an open admission that Open Source code has bugs. If not, there would be no use for those many eyes.

      The fundamental argument for Open Source is that, yes, it will contain bugs, but they will be discovered and fixed faster, because anyone interested can dig into the code, analyze it, test their conclusions, and publish the results (whether they be merely exploits or also include patches).

      The occasional claims that Open Source doesn't have bugs should generally be dismissed for the cluelessness that they show. Either that, or they're intentional disinformation by people wanting to push the PR tactics that we're already reading here.

      To push in the other direction, we might point out that closed-source proprietary "security" code could well contain exploits like this intentionally, with the full intent of selling the collected information to other interested parties without your knowledge. If you're at all interested in security, you should take this possibility seriously. There's probably no need to mention the recent news stories that illustrate this, right?

    22. Re:Wat? by DerekLyons · · Score: 1, Insightful

      "The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility."

      No, just no. No one with any sort of a clue ever argued these issues cannot happen with Free Software.

      No, they haven't made that claim in so many words. But they've sure as hell implied it for years now. That's the whole line of thought that Raymond's statement (quoted in TFS) is based on.

      The amount of backpedaling and smoke blowing in this discussion awesome.

    23. Re:Wat? by Anonymous Coward · · Score: 1

      Just shows foss-being-secure-because-source-code-is-open was never a valid argument to begin with. Obscurity does not afford security, but advertising your unfixed vulnerabilities openly is worse. Way worse.

      In truth, the world does not share FOSS altruism. We open source things hoping people will abide by , contribute fixes and share alike. You get some of that, but you also get people looking for vulnerabilities to exploit or profit from. And finding them in source code is easier than wading through obfuscated binaries.

      And this example begs another question - if this was present in the venerable OpenSSL, what of thousands of smaller projects?

    24. Re:Wat? by Savage-Rabbit · · Score: 1

      You seriously think that black hats bother with reading millions of lines of code in the hope of finding an exploit when all they have to do is play with the data sent to services/applications and see if it misbehaves. Which is why exploits are equally found among closed and open softwares.

      Generally I still think that open source projects have an advantage over closed source because there are more eyes on the code in a FOSS project. That being said shit does and will happen and unfortunately even in open source projects sometimes a whole lot of shit manages to pile up before it finally hits the fan which of course then results in a particularly big and very stinky mess like Heartbleed. What the OpenSSL team seems to have failed to do is to perform a really serious amount of destructive testing on their library which, as you pointed out is essentially what black hats do to find these kinds of vulnerabilities anyway. This is not surprising since quality assurance and testing seems to be a bit of a poor relations many FOSS projects just like it is in the closed source community. Another thing I'd try if I was a black hat is to run some kind of static code analyser on the codebase that can identify this kind of problem so that might be another thing the OpenSSL team can try if they aren't doing it already. Finally, when something is as widely used and fundamental to the workings of the internet and online commerce as OpenSSL is one would expect that perhaps some of the big beneficiaries of the OpenSSL project like Google, Apple, Amazon, Facebook etc. could foot the bill to do some suitably paranoid amount of quality assurance on it and other such FOSS projects. After all it's not like any of them is short of cash now is it and maybe these corporations could invest some of that cash they avoid paying in taxes to make everybody's digital lives a little safer by offering bounties for OpenSSL bugs? (...and yes, I know that expecting corporations to show communal responsibility is a long shot but hope springs eternal)

      --
      Only to idiots, are orders laws.
      -- Henning von Tresckow
    25. Re:Wat? by Anonymous Coward · · Score: 1

      Google wasn't the only one to find the bug, there was another independent discovery within 24 hours.

      That was a joke, right? Bug was in the wild for 18 months, and suddenly discovered independently by two orgs?

      What this means is it's functioning EXACTLY as intended.

      If what you are saying is true (you didn't name who discovered independently), this means EXACTLY the opposite of what you are suggesting - that OpenSSL being open source had nothing to do with discovering the bug.

    26. Re:Wat? by TsuruchiBrian · · Score: 4, Insightful

      The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility.

      The visibility doesn't make it so bugs don't exist. It makes them more likely to be found. This one existed and was found.

      And the argument "Open Source is inherently safer" has been very heavily damaged by Heartbleed and now ranks up there with "Macs don't get viruses" and "Women are worse drivers".

      The argument "seatbelts make riding in a car safer" is not "heavily damaged" by someone dying in a car accident while wearing a seatbelt.

      Imagine this code was closed source. Whats the desired outcome? That hackers never stumble upon the bug and the it goes unnoticed forever, and therefore never needs to be fixed?

    27. Re:Wat? by budgenator · · Score: 1

      I reverse-engineered the old Microsoft assembler for CP/M to give it an advanced feature it lacked and did it strictly on my own time and for my own private benefit (pre-DMCA).

      Disassembling something like SSL is several orders of magnitude more involved than an assembler for CP/M, but I'll give you extra points if you remember what run #400 did.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    28. Re:Wat? by grumpyman · · Score: 1

      I don't know but it's plausible. Randomly sending stuff seeing it misbehave is kind of ad-hoc, but one can possibly target the code change at each release then there's no need to read millions lines of code.

    29. Re:Wat? by jc42 · · Score: 2

      Because OpenSSL is such a common tool and is arguably vital to the function of the Internet as we know it, this sort of a bug really is one of those "worst case scenarios"

      True, but the main lesson to learn from it can be summarized by the old cliche saying "Don't put all your eggs in one basket". The warning about a "monoculture" also applies here. If one specific piece of software is universally used, even a minor bug in it can be a widespread disaster. If people had any sense, the very fact that something is so popular and widespread would be a strong argument for duplicating its functionality with independently-developed code.

      Of course, in reality we humans tend to act like herds of sheep ("sheeple", to coin a term ;-), and we tend to think that if everyone is buying X, then X must be a good thing to buy. With software, this is a major failure of logic that should stand out in the current story. If everyone is using X, then all it takes is one exploit to take down everyone's favorite toys.

      But history teaches us that, no matter how many times we warn people about a single basket, people in general don't learn.

      (Actually, I've long thought that this was a major explanation of why computer geeks tend to have such a wide variety of systems, with different release levels from their neighbors and friends. They're usually not much impressed by popularity. But the geeks are a tiny minority of humanity.)

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    30. Re:Wat? by Anonymous Coward · · Score: 1

      But the statement that "anyone can find and fix it" is a false claim for several reasons.

      1) It takes expertise in the code base at hand to be able to find and fix bugs. One cannot simply walk over to any old million-line code base and start fixing it. There is a barrier to entry which is the time that it takes to grok a sufficient amount of not just the code, but the intended design ideas behind the code in order to actually find and fix a bug. There is also the basic issue of the level of competence of the developer. The number of developers would can work on complex code bases successfully is actually rather small.

      2) The open-source projects are highly inbreed with respect to who can actually submit patches to a project. My company has experienced this issue repeatedly. We find a bug, or implement an improvement, and the open source project simply won't even talk to us or consider our patches because we are not an "insider" on the project. Many open-source communities seem to develop a very myopic perspective on whose patches they will even consider, and what sort of patches they will consider ("we will not accept this feature patch because it contradicts our personal vision of what is important" is something that we've heard more than once). As much as they talk about open communities, my experience has been that each project develops its own very, very closed community and if one is not on the inside of said community you can forget having your patches or feedback even considered.

      The reality is that the claim that there are "lots of people looking at the code" is not so much like the truth and hence bugs, even serious bugs, can persist in those projects for years, as we are seeing here. The claim that FOSS is somehow "more reliable" is really just more of the specious tehcno-hype that has become so endemic in our technical communities (in my opinion, much to the detriment of the technologies involved).

    31. Re:Wat? by exomondo · · Score: 1

      Because it is in an area with such a vocal group of people spouting "Impenetrable" for decades, it all of the sudden becomes quite newsworthy in a way that "yet-another-remote-code-execution-with-privilege-escalation-in-Acrobat-Reader" vulnerability doesn't.

      Or maybe because - unlike OpenSSL - nobody is running products like acrobat reader on their server which contains millions of usernames, passwords and the encryption keys that go with them that is vulnerable to this bug.

    32. Re:Wat? by jc42 · · Score: 5, Insightful

      No, just no. No one with any sort of a clue ever argued these issues cannot happen with Free Software.

      No, they haven't made that claim in so many words. But they've sure as hell implied it for years now. That's the whole line of thought that Raymond's statement (quoted in TFS) is based on.

      Huh? The quote is "given enough eyeballs, all bugs are shallow." That's a clear admission that open software, like all other software, contains bugs; that's why you want the many eyeballs. Any claim otherwise is a symptom of not understanding plain English. Eric's whole point was that the bugs in open software will be found and fixed faster than the bugs in other software, due to the population of interested people who will study it, looking for the bugs. Nothing in that quote implies (to anyone with reasonable understanding of English and basic logic) that open software doesn't have bugs. I expect Eric would just chuckle at the very idea of software without bugs.

      (Actually, someone near him should ask him. Tell us whether he chuckles, or snickers, or just gets a sad look on his face. Or maybe he'll say "Well, there is a conjecture that bug-free software exists, but in has never been observed in the field by reliable observers." ;-)

      A much more useful conclusion from this story (if you're serious about computer security) is that this bug has been found and fixed in OpenSSL, but with its proprietary competitors, we have no way of knowing what horrible exploits they may be hiding. And you'd be a dummy to think they don't have exploits; every chunk of security-related software has exploits. The meaningful question is whether they can be found and fixed by the people using the software. If not, you'd be a fool to use that software.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    33. Re:Wat? by nomanisanisland · · Score: 1

      What the OpenSSL team seems to have failed to do is to perform a really serious amount of destructive testing on their library which, as you pointed out is essentially what black hats do to find these kinds of vulnerabilities anyway. This is not surprising since quality assurance and testing seems to be a bit of a poor relations many FOSS projects just like it is in the closed source community.

      Actually that surprised me quite a bit. A lot of FOSS projects do perform testing, at least automated testing. And some even do fuzz testing. And some even run static code analyzers. So considering how important and widely-used OpenSSL is, I was surprised to hear they didn't. So I went and checked and they do appear to have some test code. Obviously not enough, or at least not for this new hearbeat feature, but they do have some.

      Finally, when something is as widely used and fundamental to the workings of the internet and online commerce as OpenSSL is one would expect that perhaps some of the big beneficiaries of the OpenSSL project like Google, Apple, Amazon, Facebook etc. could foot the bill to do some suitably paranoid amount of quality assurance on it and other such FOSS projects.

      I'm with you 100% on that. They have no legal obligation of course, but damn they look really cheap and slimy right now. (except for maybe Apple since they don't use OpenSSL, but then again they had their own embarrassing security bug just a few months back)

    34. Re:Wat? by fractoid · · Score: 1

      This one time this guy died in a car crash and he was driving a Volvo.

      Therefore motorbikes are safer than Volvos.

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    35. Re:Wat? by Darinbob · · Score: 2

      And sometimes it took months or years for any patches to come out, sometimes never.

      I remember the first internet worm that attacked via sendmail. The thing was that a core group of insiders knew about the bug and had patched their systems, but the larger community of sysadmins had no idea that the vulnerability existed. It was especially a problem for those systems were the people operating it relied only on official documentation from vendors and who didn't hang out on usenet or at conferences. It wasn't open source, as only people who spent the extra money could get the source and recompile to fix things, assuming they knew something needed fixing. I think one of the big changes from how I saw it was that after the worm the communication became more open about security issues.

    36. Re:Wat? by Anonymous Coward · · Score: 0

      If by "they" you mean people with a vested interest in closed source, then yet, "they" have been saying/implying such things for years.

      Once you realize that there is more than one group at play here, you'll see that no back pedaling is required.

    37. Re:Wat? by fluffy99 · · Score: 1

      You seriously think that black hats bother with reading millions of lines of code in the hope of finding an exploit when all they have to do is play with the data sent to services/applications and see if it misbehaves. Which is why exploits are equally found among closed and open softwares.

      This is true, and exactly how this was found by Codenomicon. Having access to the source code actually makes it far easier to turn the bad behavior into a working exploit, particularly for something like buffer overflows. Although in this case, there wasn't much work needed as the bad behavior was returning the contents of memory in response to a bad parameter.

    38. Re:Wat? by darkonc · · Score: 1
      Anybody who states it that categorically is stupid, ignorant, full of hubris -- or setting up a straw-man.

      The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility.

      Pretty much anything built by man is subject to errors. That includes source code -- open or closed. Any sane programmer knows this. The difference with open source is that the code is open to the users. Especially in the case of security, correctness is a high priority for many users, and those users can drive the bug-hunt process. As such, bugs tend to get found and fixed (sometimes proactively) faster with Free and Open Source code than with proprietary code.

      For companies, on the other hand, security and correctness, in general, is a cost centre. It's often only pursued to the extent to which ignoring it affects profits. If it's considered better for the bottom line to ignore/hide a critical security bug than to fix it, then it may never get fixed. -- "Better for the bottom line" includes being paid to keep a bug open by the NSA/KGB/MOSAD/etc. The well-being of the customer base is only a (indirect) part of the profit calculation.

      "Bad for the bottom line." Includes fixing code that you're no longer actively selling -- unless the bug hurts your public image too badly.

      That's why, for example, XP is no longer going to be supported -- despite the fact that perhaps hundreds of millions of machines still use it.

      Redhat 7.2 isn't officially supported by Red Hat, either -- but despite the fact that the current user base is probably in the range of hundreds or thousands, somebody who considers it critical infrastructure and can't/won't upgrade it can still arrange to get bug fixes because the source is legally available. RedHat isn't the gatekeeper for support the way that Microsoft is for Windows. RedHat is simply the (highly) preferred source of support.

      --
      Sometimes boldness is in fashion. Sometimes only the brave will be bold.
    39. Re:Wat? by mcrbids · · Score: 1

      Your points are valid, in a sense. But do you really think that people are going to stop trusting Open Source technologies? What isn't part of the conversation is just how terribly horrible OpenSSL actually is. It's a readability nightmare. The patch makes my eyes bleed, makes me weep gently to myself as I rock myself in an attempt to succor the horrific nightmare that code of this quality is what drives most Internet "security".

      I so sorely wish more consideration was given towards NACL as a replacement for OpenSSL. It's clean, elegant, readable. Bugs will be shallower because readers might have *some idea* what is going on. And with an LGPL license, it should be quite embeddable.

      IMHO, OpenSSL should be toss summarily as soon as possible. Beneath its horrific API and code lurk untold numbers of nascent, undiscovered holes no doubt already being exploited by our good friends at the NSA.

      Writing security code is *hard*, folks. Making it hard to read only makes it impossible to debug...

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    40. Re:Wat? by Lodlaiden · · Score: 2

      This one time this guy died in a car crash and he was driving a Volvo.

      Pics or it didn't happen.

      --
      Suborbital [spaceflight] is the special olympics of spaceflight. - Rei
    41. Re:Wat? by Barsteward · · Score: 1

      Read and understand the quote.. "bug are shallow" doesn;t mean there are none

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    42. Re:Wat? by rtb61 · · Score: 1

      Specifically bugs are shallow means, once found they can be readily fixed by any person or group with the ability. Bugs are deep in closed source proprietary code because they are buried and hidden and can not be fixed by the market. Of course with FOSS if you are not happy with the implementation of any security fix or method you are free to change it for one you prefer.

      All FOSS packages are simply library locations, you choose which library to pick your software from, based upon how it is secured, how it adds changes to the software, how accessible the software is and how well documented that particular library is. So no, it is not for any one to decide how particularity FOSS Libraries are controlled, except for those who are directly involved in it and contribute to it. PS bugs in closed course proprietary software are only kept secret from customers, the suckers and not the exploiters and that is just for marketing purposes.

      --
      Chaos - everything, everywhere, everywhen
    43. Re:Wat? by Anonymous Coward · · Score: 0

      Bugs happen because those who write code aren't perfect. But that is another discussion. The system worked perfectly the bug was caught because someone read the code. If you want to avoid having bugs out in the wild you need to do a code audit and revamp how software releases pass security. How many "code audit" groups do you see in the community?

    44. Re:Wat? by Anonymous Coward · · Score: 0

      It helps the people who want to fix the bugs an awful lot more.

    45. Re:Wat? by Anonymous Coward · · Score: 0

      Well, you wouldn't start by reading millions of lines of code but it certainly helps to have access to it. Especially for people with serious resources, governments etc.

      Given people with serious resources, governments. etc., they have access regardless open/closed flag.

    46. Re:Wat? by williamhb · · Score: 1

      Huh? The quote is "given enough eyeballs, all bugs are shallow." That's a clear admission that open software, like all other software, contains bugs; that's why you want the many eyeballs. Any claim otherwise is a symptom of not understanding plain English. Eric's whole point was that the bugs in open software will be found and fixed faster than the bugs in other software, due to the population of interested people who will study it, looking for the bugs.

      To coin a corollary, because "given enough eyeballs, all bugs are shallow" (Raymond), in practice "given enough eyeballs, each eyeball will all assume the others have inspected the code, and even shallow bugs can remain."

      This bug wasn't some deep complex intricacy. It was an incredibly simple and straightforward blunder that went unnoticed for years. If it had broken requests that should succeed, those many eyeballs would have felt some pain and been prompted into finding the bug. But because instead it let you do something you shouldn't be able to (a security hole), people using the library normally did not feel the pain of things breaking. And so, it seems, they weren't motivated to review the code until much later.

      The big problem, as consumers of libraries, is that reviews cost. If every update of an open source library means its users then need to review the code change (in case it's brought in a heart bleed like bug that the committers did not check for), then free software becomes more expensive than it used to be. As programmers, each of us uses a lot of free software in most of our projects. And I suspect on average we read less than 5% of the code that is brought in (dependencies can have transitive dependencies... have you reviewed the entire code of the web framework you use plus all its supporting libraries and all those libraries' supporting libraries...?) We are all deeply dependent on some of the other eyes having looked because we simply can't afford the time to look at it all ourselves.

      It's not a distinction between open versus closed per se. But as open source has become ubiquitous, so too has a disclaimer of liability. Almost every library we (collectively) use is licensed "AS IS, WITHOUT WARRANTY OF ANY KIND, INCLUDING... FITNESS FOR PURPOSE". In other words, we live in an era where for pretty much every software product, either itself or at least one of its dependencies, carries an all-caps notice that it might be rubbish, unfit for purpose, burn your house down, set fire to your cat. This runs completely counter to an idea of building in safety -- instead, we just disclaim away liability for unsafety.

      Here we could perhaps divert into alarmist analogies ... fire extinguishers labelled "WE DO NOT GUARANTEE THIS IS IN ANY WAY SUITABLE FOR PUTTING OUT FIRES" and potentially containing flammable foam? Building industries with no planning, certification or inspection requirements, and where the only requirement for the structural engineer of a skyscraper is that the untrained interviewer thought he answered that brainteaser about how many marbles you could fit in a space helmet very eloquently. But that would be being provocative for its own sake.

      More realistically, we're in a world where a very large amount of software development assumes that it is non-critical and that breakage is minor ... even as it runs more and more of the economy. And pretty much everyone does it because we're all so economically optimised that it's the only way we can afford to get anything done.

    47. Re:Wat? by Anne+Thwacks · · Score: 1
      IMHO, OpenSSL should be toss summarily as soon as possible.

      And replaced with what, exactly? ftp?

      --
      Sent from my ASR33 using ASCII
    48. Re:Wat? by Anonymous Coward · · Score: 0
    49. Re:Wat? by sjames · · Score: 1

      Count me out of they. I and many others state explicitly that Open Source reduces but cannot absolutely eliminate security bugs. Go ahead, dig up my posts on archive .org.

    50. Re:Wat? by ShakaUVM · · Score: 1

      >You seriously think that black hats bother with reading millions of lines of code ...yes?

      That's what we did in Bennett Yee's security class. "Here's the source code for a server I'm running. Go break it."

    51. Re:Wat? by Anonymous Coward · · Score: 0

      Just shows foss-being-secure-because-source-code-is-open was never a valid argument to begin with. Obscurity does not afford security, but advertising your unfixed vulnerabilities openly is worse. Way worse.

      I'll pick open source every single time over closed source. Because when I have the source, I don't have to wait months for official fix. I can simply fix it myself within a few minutes or maybe hours from finding out about the bug. And heartbleed specifically was the kind of bug that I could fix myself in less than an hour starting just with a description of how to exploit it and no prior knowledge of OpenSSL codebase.

      In truth, the world does not share FOSS altruism. We open source things hoping people will abide by , contribute fixes and share alike. You get some of that, but you also get people looking for vulnerabilities to exploit or profit from. And finding them in source code is easier than wading through obfuscated binaries.

      Finding a security hole in several million lines of code is only marginally easier than finding it in a binary. Nobody scans for vulnerabilities by reading the code (code audits are expensive and therefore rare). When you scan for vulnerabilities, you build a binary and then hammer it with automated testing tools until it breaks. The marginal advantage of open source is in automated code scanners which can report potential bugs that binary scanner often miss.

      And this example begs another question - if this was present in the venerable OpenSSL, what of thousands of smaller projects?

      OpenSSL has only 4 part-time developers working on it. It's small by any definition that takes the number of developers into account.

    52. Re:Wat? by Gunboat_Diplomat · · Score: 1

      In the self-mythology of FOSS, bugs like Heartbleed aren't supposed to happen when the source code is freely available and being worked with daily.

      False. Bugs can and do happen. However, what can also happen with open source software is that entities other than the group working on the project can find bugs. In this case, Google found the bug. If the source were not open, maybe it would have never been officially recognized and fixed.

      The Hartbleed bug was found using automated testing by two researches from Codenomicon and one from Google, and they disclosed it with enough detail to replicate. Closed or open source wouldn't have made a difference in how this was discovered or reported. It might have made a difference in how it was responded to, but that is hard to prove.

    53. Re:Wat? by Anonymous Coward · · Score: 0

      Better re-read what the GP poster put. They're NOT going to bother with it. Seriously. Having the code available doesn't help them in any more ways than anything else. Most of the exploit finders? They're NOT software engineers. They're social engineers and the like. But...go ahead...be an idiot. No skin off my nose either way,

    54. Re:Wat? by Anonymous Coward · · Score: 0

      The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility.

      Open Source is better because you don't have to wait months for official fix of critical bugs. You can write a quick and dirty fix yourself or pay somebody to do it for you immediately. It was never about the openness making search for bugs easier because it doesn't. The "all bugs are shallow" part of ESR's famous quote applies to tracking down known bugs and fixing them, not finding as of yet unknown bugs.

    55. Re:Wat? by Anonymous Coward · · Score: 0

      The only software that is bug and exploit free, is one that doesn't do anything.

    56. Re:Wat? by F.Ultra · · Score: 1

      Thas was becaue Codenomicon tried to develop a scanner cabable of catching errors such as this. Which is another side of the many eyeballs, i.e companies such as these uses the large amount of available source to develop and fine tune their scanners and we the community thus gets a free analysis of the sources.

    57. Re:Wat? by F.Ultra · · Score: 1

      So you and your classmates drove through millions of lines of code during class?

    58. Re:Wat? by F.Ultra · · Score: 1

      Not really ad-hoc, in protocols such as this which is well defined any way, you know that there is a lenght. Playing tricks with that length to see what the server does is black hat 101. In my youth I used this to create cracks for copy protected games, if we have had access to the source code of these games it would still have been faster for us to attack the protocols, and I'm sure that black hats attacking systems such as these feels the same these days. Hard to explain the enormous exploits in the wild for closed sources otherwise don't you think?

    59. Re:Wat? by Anonymous Coward · · Score: 0

      Google wasn't the only one to find the bug, there was another independent discovery within 24 hours.

      That was a joke, right? Bug was in the wild for 18 months, and suddenly discovered independently by two orgs?

      What this means is it's functioning EXACTLY as intended.

      If what you are saying is true (you didn't name who discovered independently), this means EXACTLY the opposite of what you are suggesting - that OpenSSL being open source had nothing to do with discovering the bug.

      There wasn't a second discovery, there was a duplicate CVE from the same researchers. And you are absolutely right in that source code played no role in the discovery, it was automated testing tool that would have worked just as well uncovering this if OpenSSL was closed source.

    60. Re:Wat? by Anonymous Coward · · Score: 0

      And yet, closed source bugs are found and exploited just as effectively, but rarely fixed as a result.

      Rarely fixed? Sounds like you have forgot to turn on the update functionality in your OS/software, then you would have seen a regular string of security fixes fyi.

      The thought that a bug with such massive impact as Hartbleed would not have been recognized or fixed if it was closed source -- after being disclosed publicly with detail enough for everyone to replicate -- is so far bizarrely fetched that I can't believe anyone actually believes that, but rather use it as a mis-direction attempt for this embarrassment.

    61. Re:Wat? by Anonymous Coward · · Score: 0

      A much more useful conclusion from this story (if you're serious about computer security) is that this bug has been found and fixed in OpenSSL, but with its proprietary competitors, we have no way of knowing what horrible exploits they may be hiding. And you'd be a dummy to think they don't have exploits; every chunk of security-related software has exploits.

      That is complete and utter FUD. This bug wasn't found because OpenSSL is open source, it would have been found and disclosed the exact same way if OpenSSL was closed source. To try to imply that it would have gone unnoticed and unfixed if it wasn't for open source is an extremely disingenuous attempt at misdirection, that does not serve OSS well.

    62. Re:Wat? by herve_masson · · Score: 2

      The visibility doesn't make it so bugs don't exist. It makes them more likely to be found. This one existed and was found.

      I see another lesson here. We (i mean, people in the IT industry) rely on ultra sensible piece of code like openssl, and we blindly use it. We don't question much about how the way this software is created and by who. That's the problem. We put our trust on something we know very little about. Discovering the small team coding openssl is quite a surprise to me. I feel really ashamed to discover this that late. How stupid is that... The feeling that "because so many smart people use openssl must imply strong coding reviews and intense testing" is just plain wrong, period. I should have known that before. I should have care. Open source makes possible to educate yourself on stuff like that.

      The lesson is enormous, and comes with an great price tag.

      How many of this kind of software is vulnerable and used by all our clients ? How can we improve this efficiently ? Is the openssl a unique case study, or is [your favorite software's name] equally risky ? Real questions with tough answers...

      Still, I feel open source will shorten the path to solutions more than closed sources would, as long as we change some important things in our habits. Just my one cent anyway.

    63. Re:Wat? by BluenoseJake · · Score: 1

      Just because you don't understand women do not make them worse drivers, all you've really stated with your anecdote is that YOU can't predict what women will do while driving.

    64. Re:Wat? by Anonymous Coward · · Score: 0

      Bugs happen because those who write code aren't perfect. But that is another discussion. The system worked perfectly the bug was caught because someone read the code.

      People keep repeating this here when it simply isn't true. The bug was (as with far the most security vulnerabilities today) caught using an automated testing tool, not by reading code. This tool would have found the bug even if OpenSSL was closed source.

    65. Re:Wat? by RabidReindeer · · Score: 1

      Actually, my first disassembly efforts were directed against the IBM System/370 FORTRAN runtime libraries. When I later took integral calculus I instantly recognized the algorithms as well as the tricks used to fold values over to make them converge more rapidly.

      Just because SSL is encryption doesn't mean that the algorithms should be more cryptic. We're still talking polynomial math here to do the heavy lifting. In fact, "clever" code will generally make the encryption less secure, since the more complicated you make things, the more places they can fail.

    66. Re:Wat? by ShakaUVM · · Score: 1

      You don't need to do "millions of lines of code". Hitting server and protocol codes is a very productive exercise - we turned up security vulnerabilities every time we did source code analysis.

      OpenSSH is only 60,000 lines of code.

    67. Re:Wat? by dag · · Score: 1

      Indeed, "Given enough eyeballs, all bugs are shallow.".

      In this specific case there are rumors that there we probably only 4 eyeballs involved, which apparently was not enough ;-)

      Whatever said and done, there is big responsibility with the various Enterprise distributions and various hardware/software vendors that relied on OpenSSL for their business without doing their due diligence. Whether it was because they all expected the other to have covered that space, or because the particular source code is not easy to audit is less relevant. And I am sure that many companies are looking what can be done to improve their processes in this space.

      I expect in the coming months to see more fixes for new vulnerabilities because of new audits and security testing.

  3. Mr Fixit by frisket · · Score: 5, Insightful
    All that has happened is that FLOSS has been shown to react faster to security revelations than closed or proprietary softwarre.

    That's fine with me.

    1. Re:Mr Fixit by iluvcapra · · Score: 4, Insightful

      That it reacts fast is good. That the bug could be audited in the source, in public, is good.

      We should remember that FLOSS reacted very quickly to the "revelation," but the bug itself has been sitting there for years, which isn't really supposed to happen.

      It's nice we know how long it's been there, and can have all kinds of philosophical discussions about why the OpenSSL folks decided to write their own malloc.

      Also OpenSSL was effectively a monoculture and just about every SSL-encrypted internet communication over the last two years has been compromised. OpenSSL has no competition at its core competency, so the team really has no motivation to deliver an iteratively better product, apart from their need to scratch an itch. FLOSS software projects tend not to operate in a competitive environment, where multiple OSS products are useful for the same thing and vie for placement. This is probably bad.

      --
      Don't blame me, I voted for Baltar.
    2. Re:Mr Fixit by Anonymous Coward · · Score: 1

      No, you've got the timeline wrong on the bug. The bug was committed to the repository more than two years back, but it wasn't in major use until more recently. RHEL, for example, didn't ship the buggy code until November 2013. And, by extension, Centos, Oracle Enterprise Linux, Amazon Linux AMI, etc.

    3. Re:Mr Fixit by CajunArson · · Score: 4, Insightful

      " just about every SSL-encrypted internet communication over the last two years has been compromised."

      No, it really hasn't.

      It's accurate to say that just about every Open-SSL encrypted session for servers that were using NEW versions of OpenSSL (not all those ones out there still stuck on 0.9.8(whatever) that never had the bug) were potentially vulnerable to attack.

      That's bad, but it's a universe away from "every SSL session is compromized!!!" because that's not really true.

      --
      AntiFA: An abbreviation for Anti First Amendment.
    4. Re:Mr Fixit by Desler · · Score: 3, Interesting

      Which is a ridiculous statement to make in this situation. That's like patting your security company on the back for not noticing for two years that someone was secretly stealing money out of your bank vault and they only did something after being told by a third-party that there was a problem. But hey they reacted fast two years after the fact, right?

    5. Re:Mr Fixit by MightyMartian · · Score: 2

      Debian was a bit longer, so far as mainline releases go (I don't use testing branches). I have several servers and routers running 6.0, and they're all using OpenSSL 0.9.8, whereas my servers I use as KVM virtualization hosts are running Wheezy and did have vulnerable versions of OpenSSL. I had been thinking over the last few months that I should upgrade my old Debian Squeeze servers and appliances, a number of which are used for my OpenVPN WAN routers and remote client servers. I'm very glad my business/procrastination prevented me from upgrading these systems, and hence they remained untouched, and I don't have to go through the pain of regenerating keys and rolling them out to remote routers and to all the road warriors and work-at-home types.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    6. Re:Mr Fixit by Anonymous Coward · · Score: 1

      Also OpenSSL was effectively a monoculture and just about every SSL-encrypted internet communication over the last two years has been compromised.

      Microsoft IIS begs to differ.

    7. Re:Mr Fixit by Anonymous Coward · · Score: 0

      OpenSSL shouldn't *have* any competition. The problem with security is that it's hard to even validate that any given implementation even works and a lot of security software is just snake oil. If we had too many security implementations going on then we'd make it even harder to suggest that our services are in any way secure.

      Simple security is the best security, we don't need bells and whistles.

    8. Re:Mr Fixit by Anonymous Coward · · Score: 0

      It's nice we know how long it's been there, and can have all kinds of philosophical discussions about why the OpenSSL folks decided to write their own malloc.

      Heh. I've done that. In fact, I've kept my (with several contributions from a few others) own implementation around for a few decades, and have re-used it in a number of projects. In one of them, about 10 years ago, I plugged it into one of their projects and produced an order-of-magnitude increase in its speed. Granted, the project was a bit unusual in that it was calling malloc() a lot as it collected data, then called free() a lot as it processed completed subsets of the data. I was able to show that this was a major time-eater, got permission to try my "hack", and they were duly impressed with the results.

      Not to say that I think everyone should do this on every project, of course. I sure don't. But I have little trouble thinking of reasons that people might decide to make the effort to write such an "unneeded" package.

    9. Re:Mr Fixit by Anonymous Coward · · Score: 0

      Please don't fuck us all over by using the term floss. You make us sound like a bunch of deranged dentists. I know you hate us and want to make us look stupid like all Republicans of your kind, but just fucking stop. We get it. You hate us and this site. You're trying to embarrass us and shutdown this site. This dental analogy game needs to end now. I wish you Republicans would stop making everything about politics.

    10. Re:Mr Fixit by Anonymous Coward · · Score: 0

      We should remember that FLOSS reacted very quickly to the "revelation," but the bug itself has been sitting there for years, which isn't really supposed to happen.

      Everybody's happy to write code, nobody really reads it. This is where "many eyes" hypothesis gets a bloody nose.

      If there ever was a piece of software that needed "many eyes" that's OpenSSL. Where were these eyes for the last few years?

    11. Re:Mr Fixit by Anonymous Coward · · Score: 0

      The bug has been there for less than a year.

    12. Re:Mr Fixit by drinkypoo · · Score: 1

      We should remember that FLOSS reacted very quickly to the "revelation," but the bug itself has been sitting there for years, which isn't really supposed to happen.

      Unfortunately, the very same thing happens in proprietary software. And "isn't supposed to happen" is a misunderstanding. It's just supposed to happen less, and it's supposed to get fixed easier. The latter, at least, has been proven out.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    13. Re:Mr Fixit by Anonymous Coward · · Score: 0

      Ding ding ding. The biggest take-away from this whole episode should be that while OpenSSL has been great, having nearly the entire internet relying on it for security is a bad idea. Not because OpenSSL is bad, but because monoculture is bad. Always and everywhere. That's true elsewhere in life as well.

    14. Re:Mr Fixit by Anonymous Coward · · Score: 0

      And I can fix my now unsupported Fedora 18 install myself. Try that when the next XP bug shows up.

    15. Re:Mr Fixit by Gunstick · · Score: 1

      for years yes, but not for very long.
      Especially professionals have a very long software cycle, still hanging around with redhat5 and other old stuff.
      The bug was introduced in 1.01 and RH5 still runs 0.9.8
      I have seen that a lot of times, bleeding edge may be cool, but not necessarily secure. Staying too far behind (into the non supported area) is not secure either.
      So the "one release back" strategy is not bad. In this aspect debian stable is a bit too up to date.

      --
      Atari rules... ermm... ruled.
    16. Re:Mr Fixit by Anonymous Coward · · Score: 0

      " just about every SSL-encrypted internet communication over the last two years has been compromised."

      Just every OpenSSL one has. In the case of, say for example, Hiawatha, it has SSL- but it doesn't use OpenSSL. It's Internet communcations hasn't been compromised. Same way with IIS.

      The problem isn't even the code. It's an "innocent" feature in a security piece of security software that's an ease of use thing, really.

      XKCD basically spelled out the problem even.

      You don't design things like this into a security software to begin with- and a *DESIGN* review should've been done to it starting from the notion of is it even a good idea to begin with, not is the code "fine". Sure, you SHOULD make it relatively easy to use- but an ease of use feature should be thought through for soundness before anything else. Does it present an attack face? Once you answer that as a "yes" (which this would've...)- you ask yourself is there ANY buffer overflow potentials (you don't offer lengths, etc. An are you there or similar feature or the like shouldn't have *EVER* provided a user controllable knob. Just a reply. This flunked on the length score out of box.

      This failing would've happened in a FOSS context or a closed one. To say that the onus is on checking for this stuff in a closed source shop is LYING to yourself and others. To say that it's prevented in a FOSS project because all eyes make the bugs become shallow...that too would be LYING to yourself.

      FOSS caught it out quicker and it got fixed vastly quicker because of the oft quoted remark about bugs. How it happened? Pure and simple sloppiness combined with the wrong-headed notion that Security is a Technology and the like. Security has tech as a component. But it's more of a philosophy and way of viewing everything. This crap, if you were security conscious would've been a red-flag. Not the code that "innocently" produced it (sorry...not buying the author's take on this...he's very much at fault as are any of the others that even thought the feature that allowed the "innocent" mistake in...)- but the original feature that allowed it to be "oopsed" in the first place. It should've flunked the sniff test at the stage it was conceived because there's no good way to guarantee the implementation being safe and properly secure regardless of how it was implemented.

  4. we don't know what happened AT ALL by globaljustin · · Score: 3, Insightful

    Yes, we can trace the changelogs in the software & note who was checking the changes and missed them, but that all can be circumvented.

    The fact is we don't know if Heartbleed was an honest mistake or not...we don't know who knew and when...we don't know alot

    FOSS is nowhere in the conversation, btw...this has absolutely nothing to do with the fact that this was Open Source project.

    Private company's products have ridiculous security issues...comparing this to that is not helpful.

    --
    Thank you Dave Raggett
    1. Re:we don't know what happened AT ALL by Anonymous Coward · · Score: 0

      Well, the dude to which the change is attributed has acknowledged his mistake and his reviewer has too, for what it's worth.

    2. Re:we don't know what happened AT ALL by Cid+Highwind · · Score: 5, Informative

      "Yes, we can trace the changelogs in the software & note who was checking the changes and missed them, but that all can be circumvented."

      Actually it can't. That's kind of the point of git.

      "The fact is we don't know if Heartbleed was an honest mistake or not...we don't know who knew and when..."

      We do know who and what and when, because the person who wrote it and the person who signed off on it have commented publicly about the bug.

      Maybe you're thinking of Apple's "goto fail" SSL exploit where we really don't know who or what or when and probably never will because it's not likely Apple is going to release their RCS logs.

      --
      0 1 - just my two bits
    3. Re:we don't know what happened AT ALL by ffkom · · Score: 1

      Plus you can have a look at what the person who contributed the code and the reviewer programmed/did elsewhere in their lives, and by that you can judge whether you think it's likely they acted on purpose. In this case it seems to me the probability of this bug having been introduced intentionally is pretty low.

    4. Re:we don't know what happened AT ALL by Karlt1 · · Score: 1

      Maybe you're thinking of Apple's "goto fail" SSL exploit where we really don't know who or what or when and probably never will because it's not likely Apple is going to release their RCS logs.

      Well we know the when and we know the what .

      http://www.theguardian.com/tec...

    5. Re:we don't know what happened AT ALL by Antique+Geekmeister · · Score: 1

      > Actually it can't. That's kind of the point of git.

      Unfortunately, many git users keep their SSH keys unencrypted on their local hard drives or on network accessible home directories. This means that a careless git admin may have their SSH keys stolen by quite amateur crackers, and leave the public repositories open to quite malicious changes. I've had precisely such discussions with personnel who insist that they trust the people they work with and they have a firewall, so they're not at risk.

    6. Re:we don't know what happened AT ALL by Anonymous Coward · · Score: 0

      There would be a commit id for any changes they added presumably someone reviews pushes to master. They can't rewrite history without everyone with a clone of the repo noticing a error next time they push or pull.

    7. Re:we don't know what happened AT ALL by exomondo · · Score: 0

      FOSS is nowhere in the conversation, btw...this has absolutely nothing to do with the fact that this was Open Source project.

      Well it does show that the often-used argument that open source is better because "I can review the code to make sure it is secure and not malicious" is false, not even the biggest vendors did that before using this code.

    8. Re:we don't know what happened AT ALL by TsuruchiBrian · · Score: 1

      The claim was never "All bugs will be found before being used if software is open source". The claim was merely that it is more likely for a bug in open source software to be found (i.e. by either good guys or bad guys), and that this is a good thing overall.

    9. Re:we don't know what happened AT ALL by exomondo · · Score: 1

      No it has been that open source can be verified to be secure and non-malicious, which is true only in theory, not in practice.

    10. Re:we don't know what happened AT ALL by TsuruchiBrian · · Score: 1

      This is like asking "In the USA, am I free to get married to whoever I want?", and then complaining that you were lied to because Angelina Jolie didn't want to marry you.

      In the same way that it was (maybe incorrectly) assumed the person who wanted to get married to "whoever he wanted" was really asking "Am I prevented from marrying anyone that I want provided they also want to marry me?"...

      It is also common to assume that when someone says "Anyone can verify open source software to be secure and non-malicious", they are saying "No one is prevented from verifying open source software", rather than "Anyone (regardless of their software engineering ability) will find every single bug in a piece of open source software."

      If you thought that it was claimed that every piece of open source software was bug free (contingent upon being "verified" as such), I'm sorry to tell you that you were misinformed.

      Not only is both open source not able to be verified with 100% certainty. It is impossible to prove that software in general (open or closed) is bug free as a corollary to Alan Turing's proof that no solution exists to the halting problem.

    11. Re:we don't know what happened AT ALL by exomondo · · Score: 1

      It is also common to assume that when someone says "Anyone can verify open source software to be secure and non-malicious", they are saying "No one is prevented from verifying open source software", rather than "Anyone (regardless of their software engineering ability) will find every single bug in a piece of open source software."

      It isn't a matter of "every single bug in a piece of open source software", this is a hugely deployed piece of open source security software and you would expect that if the "many eyes" thing were indeed true then this is exactly the place it would be demonstrated yet what we have here is one of the most widely deployed critical security bugs ever. This isn't a condemnation of open source in any way, just of the misguided vocal advocates that pad their arguments with falsehoods rather than focussing on the real advantages of open source (like the speed at which bugs like this can be patched).

      If you thought that it was claimed that every piece of open source software was bug free (contingent upon being "verified" as such), I'm sorry to tell you that you were misinformed.

      I know such claims have always been false and this is just more proof of it at the most prominent and non-theoretical level so I'm not quite sure what your point is. This alone didn't disprove the claim, it just added more proof (and at an extremely high visiblity) that the claim is false.

    12. Re:we don't know what happened AT ALL by Anonymous Coward · · Score: 0

      Stop shitting your pants you fucking muppet.

    13. Re:we don't know what happened AT ALL by m.alessandrini · · Score: 1

      Maybe unrelated, but the bug revelation too is a bit suspect to me. I mean, look at the Heartbleed web site, it seems they are showmen rather than scientists, they registered a domain expressely, they drawn a logo... Seems much like self-advertising.

    14. Re:we don't know what happened AT ALL by TsuruchiBrian · · Score: 1

      It isn't a matter of "every single bug in a piece of open source software", this is a hugely deployed piece of open source security software and you would expect that if the "many eyes" thing were indeed true then this is exactly the place it would be demonstrated yet what we have here is one of the most widely deployed critical security bugs ever. This isn't a condemnation of open source in any way, just of the misguided vocal advocates that pad their arguments with falsehoods rather than focussing on the real advantages of open source (like the speed at which bugs like this can be patched).

      And the bug was found by people who were not the developers, but rather people using the software. This is unlike bugs which are not as widely deployed, and are far less likely to ever be found.

      I know such claims have always been false and this is just more proof of it at the most prominent and non-theoretical level so I'm not quite sure what your point is. This alone didn't disprove the claim, it just added more proof (and at an extremely high visiblity) that the claim is false.

      My point is that nothing about this situation is any kind of failing of open source software if you had realistic expectations to begin with. There was a really bad bug that was introduced into a widely distributed piece of open source software and after a few years, some people found it and it's now getting fixed.

    15. Re:we don't know what happened AT ALL by exomondo · · Score: 1

      My point is that nothing about this situation is any kind of failing of open source software if you had realistic expectations to begin with. There was a really bad bug that was introduced into a widely distributed piece of open source software and after a few years, some people found it and it's now getting fixed.

      Of course, but it's those people that perpetuate the unrealistic expectations that have been put in their place. The fact that such people spread that nonsense is entirely the reason you have people now saying "a bug in widely used open source software?! how could that happen?!"

    16. Re:we don't know what happened AT ALL by TsuruchiBrian · · Score: 1

      The whole point of wanting to have many eyes on open source code is *because* there are bugs in it, and every software.

      I am not aware of any claims made by anyone remotely reputable that open source software doesn't contain bugs.

      Even if the claim is that open source software contains fewer bugs, finding one bug does not disprove that sort of claim.

    17. Re:we don't know what happened AT ALL by exomondo · · Score: 1

      I am not aware of any claims made by anyone remotely reputable that open source software doesn't contain bugs.

      I didn't say anyone did, in fact such a thing is demonstrably false so I'm not quite sure what you say that.

      Even if the claim is that open source software contains fewer bugs, finding one bug does not disprove that sort of claim.

      No but when a bug this severe is discovered in something so widely deployed it certainly does damage the "many eyes" claim, it has about as many eyes on it as any open source program is likely to get so clearly that isn't the answer. Having "many eyes" doesn't necessarily diminish the quality, but obviously it doesn't necessarily improve it either so saying it's better because it has "many eyes" looking over it is disingenuous at best.

    18. Re:we don't know what happened AT ALL by TsuruchiBrian · · Score: 1

      I didn't say anyone did, in fact such a thing is demonstrably false so I'm not quite sure what you say that.

      I don't understand how else it could be shocking to find a bug in a piece of software unless it didn't contain any bugs.

      No but when a bug this severe is discovered in something so widely deployed it certainly does damage the "many eyes" claim, it has about as many eyes on it as any open source program is likely to get so clearly that isn't the answer.

      It's not as if "severe" bugs are easier to find. Why does it damage the many eyes claim? It had many eyes on it, and it eventually got found by a few of those many eyes. Nothing is *the* answer. Open source is one of many ways to *improve* the quality of code.

      Having "many eyes" doesn't necessarily diminish the quality, but obviously it doesn't necessarily improve it either so saying it's better because it has "many eyes" looking over it is disingenuous at best.

      I think it quite clearly does improve the quality. Even if 1 bug was found by someone looking through open source code this is an improvement over not finding this bug. The question is how much is the code improved by it being open source.

      Better doesn't mean good. Better means better.

      Spell checking your English paper makes it better if you find even one spelling mistake, it doesn't make it good.

    19. Re:we don't know what happened AT ALL by exomondo · · Score: 1

      I don't understand how else it could be shocking to find a bug in a piece of software unless it didn't contain any bugs.

      It's not just a bug, it's this bug. Clearly a bug this severe is a much more shocking revelation than say an issue with toolbar location persistence in libre office.

      It's not as if "severe" bugs are easier to find. Why does it damage the many eyes claim? It had many eyes on it, and it eventually got found by a few of those many eyes. Nothing is *the* answer. Open source is one of many ways to *improve* the quality of code.

      And it has dubious value given that this bug was committed, reviewed and accepted then extremely widely circulated despite many eyes being on it. It's not about having heaps of people look at it, it's about having a few people with the right knowledge and understanding of the system looking at it.

      I think it quite clearly does improve the quality.

      So what's the argument? That you have many eyes on it so this is less likely to happen than...what? Closed source software? Lower profile Open Source software? This is why it has dubious value, yes you might happen to fluke it but you're just as likely to have many eyes that completely miss it. Touting it as an advantage (even if it is in some circumstances) does it a disservice because you end up with people trusting that "it's open source so many other people are looking at it" and then you get a situation like this where it is used in literally billions of situations and the critical flaw was missed just like can happen in closed source projects. The advantage is the ability to find and fix issues yourself, not that many other people may or may not be doing it for you.

    20. Re:we don't know what happened AT ALL by TsuruchiBrian · · Score: 1

      It's not just a bug, it's this bug. Clearly a bug this severe is a much more shocking revelation than say an issue with toolbar location persistence in libre office.

      There are bits of software where bugs tend to be more likely to have security implications. Things like the kernel, encryption libraries, etc. It is still not shocking that these bits of software contain bugs.

      And it has dubious value given that this bug was committed, reviewed and accepted then extremely widely circulated despite many eyes being on it

      Having the software be widely circulated is *how* there are many eyes on it. If hardly anyone used this software then far fewer people would be looking at it, and this bug would likely never have been caught.

      It's not about having heaps of people look at it, it's about having a few people with the right knowledge and understanding of the system looking at it.

      That's like how winning the lottery is not about buying lots of tickets, it's about picking the right numbers on a single ticket.

      So what's the argument? That you have many eyes on it so this is less likely to happen than...what? Closed source software? Lower profile Open Source software?

      My argument is that the more eyes you have on the software, the more bugs you find and at a fester rate. One way to increase the eyes is to have software be open source, another is to have it be higher profile, another is to pay thousands of programmers to look at at. My point is that open source can only help the situation and often does. It makes your software more accessible to more eyes, and typically increases it's profile, and none of this precludes other people from being paid to hunt down bugs.

      This is why it has dubious value, yes you might happen to fluke it but you're just as likely to have many eyes that completely miss it.

      Even if you are just as likely to miss the bug as find it, you've increased your odds of finding a bug due to the source code's openness from 0% to 50%.

      Touting it as an advantage (even if it is in some circumstances) does it a disservice because you end up with people trusting that "it's open source so many other people are looking at it"

      Whats the alternative? Not using software? Using it while being very nervous? You should already be assuming that bugs pose a constant risk to computer security.

      The advantage is the ability to find and fix issues yourself, not that many other people may or may not be doing it for you.

      So if I find and fix the issue myself, you have just had the issue fixed for you. If you find and fix an issue yourself, then I have had the issue fixed for me. We all benefit from bugs found and fixed by other people.

      Do you ever notice how software versions keep incrementing? That's because people are adding new features and fixing bugs. The fact that you aren't helping doesn't mean other people aren't.

  5. Even a bestselling novel can have a typo by sandytaru · · Score: 5, Insightful

    We're surrounded by tiny errors in the world. Heck, they're even built into our DNA. The vast majority of tiny little errors do no harm, and we don't notice them. We gloss over them, like a typo in a book. It's just that every once in a while, a tiny little error can occur that snowballs into something much greater. Like cancer. Or a massive, accidental security leak.

    More eyeballs usually do make bugs more shallow, but only if the eyes know what to look for.

    --
    Occasionally living proof of the Ballmer peak.
    1. Re:Even a bestselling novel can have a typo by unimacs · · Score: 2

      More eyeballs usually do make bugs more shallow, but only if the eyes know what to look for.

      And only if a significant number of sophisticated and knowledgeable eyes have the time and interest to dig through lines and lines of code looking for vulnerabilities.

      The reality is that the majority of eyeballs looking at code are the ones that have other reasons to be looking at it. They aren't necessarily looking for vulnerabilities but maybe they spot something.

      The eyes that might be interested in scouring code looking for vulnerabilities could be the ones wanting to exploit them rather than fix them.

    2. Re:Even a bestselling novel can have a typo by unixisc · · Score: 2

      The 'millions of eyeballs' meme is just that. How many people actually know how to read code? Just b'cos it's open doesn't mean that it's comprehendible, and therefore, the fact that the code is open & out there doesn't have that much of an advantage, particularly when it's such complex code.

    3. Re:Even a bestselling novel can have a typo by chipschap · · Score: 1

      Not saying that heartbleed wasn't / isn't a huge problem, but I think most analysts would agree that by far the biggest security problem is (collectively) bad corporate or bad individual security practices. I realize that heartbleed is not the same in that it is not within the control of the end user, but still, things like poor passwords, clicking on every email attachment, etc., are much bigger aggregate problems.

    4. Re:Even a bestselling novel can have a typo by Virtucon · · Score: 1

      We're surrounded by tiny errors in the world. Heck, they're even built into our DNA.

      Speak for yourself! I just got my 23andMe report and it says there are no errors, therefore I'm special!

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
    5. Re:Even a bestselling novel can have a typo by mattack2 · · Score: 1

      like a typo in a book.

      I hate typos in books, or even in the newspaper, though the latter seems to happen much more frequently nowadays.

    6. Re:Even a bestselling novel can have a typo by TapeCutter · · Score: 1

      Sophisticated and knowledgeable eyes don't go trawling trough code looking for bugs, they test the functionality of the binary. They only turn to the code to explain/fix what they have found.

      --
      And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
    7. Re:Even a bestselling novel can have a typo by Anonymous Coward · · Score: 0

      There's an interesting thought - a 0-day vulnerability in Human DNA. That would make for a great novel.

    8. Re:Even a bestselling novel can have a typo by TsuruchiBrian · · Score: 1

      How many people actually know how to read code?

      A lot.

      Just b'cos it's open doesn't mean that it's comprehendible

      It makes it comprehensible to *more* people.

      and therefore, the fact that the code is open & out there doesn't have that much of an advantage, particularly when it's such complex code.

      The code at the center of Heartbleed was not complex at all. It's just that no one noticed it.

    9. Re:Even a bestselling novel can have a typo by Anonymous Coward · · Score: 0

      Herpity derpity. You fuck cows, don't you....

    10. Re:Even a bestselling novel can have a typo by Anonymous Coward · · Score: 0

      This is one of the reasons that I switched from Linux to FreeBSD in the lat 90s. I could see every commit that went into the source tree and even though I wasn't personally looking at them, on many occasions I saw other developers jump in and demand the commit be backed out because of some problem. It made me feel good about the OS that people really were looking at every commit.

      Yes FreeBSD-10 was impacted by Heartbleed, but openssl is a "contributed" package, much like the compiler toolchain. So individual commits don't show up on the tree, rather the import of an entire new release.

    11. Re:Even a bestselling novel can have a typo by Barsteward · · Score: 1

      every human is an error, its 23rd and 24th chromozone is fused as opposed to all our mammalian relatives, so we are all mutants and possible X-Men

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    12. Re:Even a bestselling novel can have a typo by jones_supa · · Score: 1

      How many people actually know how to read code?

      A lot.

      Yeah, well... Even I can read the C code of most OSS projects that are written in it, but that does not mean that I understand the architecture of the project. It is crucial to actually understanding what is going on. I bet that there isn't too many people that accurately know how OpenSSL works either.

    13. Re:Even a bestselling novel can have a typo by jones_supa · · Score: 1

      Heh, chromozone...

    14. Re:Even a bestselling novel can have a typo by TsuruchiBrian · · Score: 1

      Even if you didn't know anything about the architecture of openssl, you'd probably be able to spot heartbleed if you knew a about buffer overflow bugs. Even if you didn't know about buffer overflow bugs, a static code analysis tool would have probably caught this bug as buffer overflows are very fairly easily caught in this way.

    15. Re:Even a bestselling novel can have a typo by Virtucon · · Score: 1

      so we are all mutants and possible X-Men

      Well I guess that would be better than being an X-Woman like Chaz Bono! I'm getting my money back from 23andme!

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
  6. Wait until things are over before you cry wolf by slincolne · · Score: 4, Insightful
    It's probably better to let the situation run on a bit longer before people start criticising Open Source.

    Nobody is going to discard OpenSSL due to this - the majority of people are patching systems and reminding people that security is important (a side benefit of this incident)

    The next step will be when someone puts up the money for a proper code review of the OpenSSL codebase and fixes up any other issues that may exist.

    It's reasonable to say that there are more people and organisations able to resolve this issue than if it were a closed source proprietary solution.

    1. Re:Wait until things are over before you cry wolf by eric_harris_76 · · Score: 1

      Sounds like there might be a semester project in there: review the security of such-and-such a portion of this-or-that open source software. Find a security problem that's validated by the project, automatic A.

      Document what you did, how you did it, provide adequate proof that you really did it, and have it graded accordingly. If the open source project has standards for security reviews of its work, and they certify you met them completely, also automatic A.

      Teensy problems: if the project doesn't reply to the students' efforts quickly enough, finishing well before the end of the semester won't be soon enough. How to confirm the review really was done?

      --
      There's no time like the present. Well, the past used to be.
  7. Security is hard. Encryption is even harder. by kriston · · Score: 1

    All this episode does is to remind us that security is hard. Encryption is even harder.

    --

    Kriston

  8. Original premise is false by bazmail · · Score: 5, Insightful

    Many eyeballs may make bugs shallower, but those many eyeballs don't really exist. Source availability does not translate to many people examining that source. People, myself included, may like to build to install packages but that's it.

    What we need are intelligent bots to constantly trawl source repositories looking for bugs. People just don't have the time any more.

    1. Re:Original premise is false by jklovanc · · Score: 2, Insightful

      What we need are intelligent bots to constantly trawl source repositories looking for bugs.

      If we had bots that intelligent they would be intelligent enough to write the code without bugs.

    2. Re:Original premise is false by unixisc · · Score: 1

      Many eyeballs may make bugs shallower, but those many eyeballs don't really exist. Source availability does not translate to many people examining that source. People, myself included, may like to build to install packages but that's it. What we need are intelligent bots to constantly trawl source repositories looking for bugs. People just don't have the time any more.

      Not just that, the only people who'd find such bugs are the people actually working on those programs. Usually, not their downstream users.

    3. Re:Original premise is false by F.Ultra · · Score: 2

      Well some one must have been looking since the bug was found?

    4. Re:Original premise is false by Anonymous Coward · · Score: 0

      They certainly exist now given the recent revelations. The code is now being examined with a fine tooth comb. The problem in the past was probably no-one was doing so because they were assuming others already were/had done so.

    5. Re:Original premise is false by Anonymous Coward · · Score: 0

      The bug was found because someone figured out the exploit, not because someone looked at the code and noticed a problem. I believe a major problem for FOSS is the lack of organized QA, code reviews are one thing but proper regression testing is too often left to the end user.

    6. Re:Original premise is false by suutar · · Score: 1

      I dunno. Coverity can catch a lot of stuff (in fact, I recall reading that they had to limit what they caught on the basis of what they could explain to the programmer, because confusing the programmer led to incorrect 'false positive' decisions). I don't know if it would have caught this, but it would be worth trying.

    7. Re:Original premise is false by quantaman · · Score: 1

      I don't think Heartbleed says anything fundamental about open source security, but it might alter the discussion of how certain low level packages are managed. By any measure OpenSSL is a very important package, but it's also a bit generic. It has a very defined role that everyone needs, but I'm not sure how many people really have a motive to work on it in specific. It might be that the community needs to find a way to devote more resources to maintaining and auditing those packages.

      --
      I stole this Sig
    8. Re:Original premise is false by Anonymous Coward · · Score: 0

      You can spend forever looking for things that aren't there. It's not that we don't have the time, it's that we'd rather spend the time on doing more productive things. ...like writing more bugs.

    9. Re:Original premise is false by s.petry · · Score: 1

      Not just that, the only people who'd find such bugs are the people actually working on those programs. Usually, not their downstream users.

      Which introduces another potential benefit to OpenSource (inadvertently perhaps). Many times bugs are reported "with" a fix to the bug. This is why impact is generally much lower than closed source. This cuts a few steps out of the bug correcting cycle.

      I have on rare occasion seen similar reports on bugs to Microsoft, so realize it's possible to some extent with closed OS code. Without your name getting attached to the bug or bug fix there is little incentive to do so as a developer.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    10. Re:Original premise is false by Error27 · · Score: 2

      This code could have easily been detected with static analysis. It's a common failure pattern. You just taint data from the network as untrusted and look for when invalid use cases.

      I do static analysis like this on the linux kernel for a living.

    11. Re:Original premise is false by Anonymous Coward · · Score: 0

      I dunno. Coverity can catch a lot of stuff ... I don't know if it would have caught this, but it would be worth trying.

      It was tried, and it did not catch it. Frama-C apparently would have caught it, but wasn't used.

    12. Re:Original premise is false by Anonymous Coward · · Score: 0

      Maybe HN, /., et al. should implement a CAPTCHA displaying a function from an OS lib and make the readers do things like bounds checking to ensure it's correct.

    13. Re:Original premise is false by bazmail · · Score: 1

      I like the way you think sir. I'm sure there is a practical angle there somewhere.

    14. Re:Original premise is false by TsuruchiBrian · · Score: 1

      Many eyeballs may make bugs shallower, but those many eyeballs don't really exist. Source availability does not translate to many people examining that source. People, myself included, may like to build to install packages but that's it.

      There are 7 billion people in the world. It doesn't take a large percentage of people to look at the code for there to be a large number (i.e. larger than the number that would have looked at the code if it were closed)

      I don't look through open source code very frequently, but I stumbled upon a bug in openmotif and submitted a fix. This was not possible before motif was open sourced.

      What we need are intelligent bots to constantly trawl source repositories looking for bugs. People just don't have the time any more.

      We have software that analyzes source code for common programming errors of the sort that heartbleed was. These tools can simply be integrated into the build, so that you get a warning when you introduce a potential bug and try to compile it.

    15. Re:Original premise is false by TsuruchiBrian · · Score: 1

      Even if 99% of bugs are found by the developers, why wouldn't you want that last 1% that is found by random people? I've found bugs in libraries for software that I was using. I'm sure lots of developers do this every once in a while.

    16. Re:Original premise is false by brantondaveperson · · Score: 2

      There are 7 billion people in the world. It doesn't take a large percentage of people to look at the code for there to be a large number

      I'm sorry, but that's a really silly argument. You can't create a significant number of people doing a particular thing by doing the 'big number times small number = medium size number' trick. We hear that from marketing here at work, and it doesn't make any sense there either.

    17. Re:Original premise is false by FormOfActionBanana · · Score: 1

      Yes, exactly. (My day job is static analysis)

      "Many Eyes" are great for identifying and fixing the broken build... but have no good track record for monitoring security design and implementation flaws.

      For security infrastructure critical code, the available tools should be coming up spot clean. This is absolutely not the case with Openssl.

      --
      Take off every 'sig' !!
    18. Re:Original premise is false by PhilHibbs · · Score: 1

      Not true. Writing code is very hard to automate. Finding bugs like this is easy to automate. In fact, the OpenSSL team specifically turned off all the memory overrun checks on all platforms, because some platforms have performance problems with them. So, the automated checks should have spotted this problem (at run time, rather than compile time, but there are other tools for that), but they were turned off.

    19. Re:Original premise is false by Jahta · · Score: 1

      Many eyeballs may make bugs shallower, but those many eyeballs don't really exist. Source availability does not translate to many people examining that source. People, myself included, may like to build to install packages but that's it.

      It's not the quantity of eyes, it's the quality that counts. A million script kiddies can read the code and not spot a serious bug. This is particularly true of security/cryptography software.

      What we need are intelligent bots to constantly trawl source repositories looking for bugs. People just don't have the time any more.

      Before bots, what about unit tests? It seems to me that a decent test suite would have caught what is essentially a buffer overflow.

    20. Re:Original premise is false by jklovanc · · Score: 1

      The automated check that was turned off was the one that checked to see if the memory be accessed should have been accessed. The bug only showed itself when two mismatched parameters, the string and the length of the string, were sent through. That check was more of a security guard saying "no you can't do that" and not a bug checker saying "in certain cases of parameters will cause problems so re-write the code". Bug checkers are good at catching common errors but are not a perfect solution. There are many bugs that have never been seen before or are too complex for a bug checker to find. A total reliance on bug checkers is not the way to go. We need to do both automated checks and human checks. They help each other.

    21. Re:Original premise is false by TsuruchiBrian · · Score: 1

      7 billion * 0.001% = 70,000. There I just did it.

    22. Re:Original premise is false by F.Ultra · · Score: 1

      No the bug was found because some one was looking at the code. In fact it was a company developing a static code analyzer that used the available source of OpenSSL to test their analyzer that found it, interestingly enough also a Security Engineer from Google found it at roughly the same time. So yes it was found exactly because people where looking at the sources.

      Had this been close source then none of the above would have found it.

    23. Re:Original premise is false by PhilHibbs · · Score: 1

      I was probably over-optimistic when I said "finding bugs like this is easy to automate". What this would probably need is runtime access checking turned on, and a test case that has mismatched lengths. The latter would require the tester to implement what I call C4 tests, or "comprehensive corner case coverage".

  9. Overstating the case by kurisuto · · Score: 5, Insightful

    I don't think anyone claims that open-source software won't ever have security issues. The claim is that the open-source model tends to find and correct the flaws more effectively than the closed-source model, and that the soundness of the resulting product tends to be better on average.

    One case does not disprove that. The key words there are "tends" and "on average".

    1. Re:Overstating the case by Zocalo · · Score: 3, Insightful

      This, and I suspect a lot of shilling by proprietary software vendors playing up the "many eyes make bugs shallow" thing. This wasn't so much a failure of the open source model as it was a failure to properly vet commits to the code of a project before accepting them into the main tree, and that could happen just as easily on a closed source development model as an open source one. That might be OK for small hobby projects, and perhaps even major projects that don't have quite so major ramifications in the event of a major flaw, but hopefully this will serve as a wake up call for projects that aim to form some kind of critical software infrastructure. For such projects requiring that commits be reviewed and "signed off" by one or more other developers would perhaps have caught this bug, and others like it, and could perhaps work very well in conjuction with some of the bug-bounty programmes out there. Of course, "Find a flaw in our pending commits, and get paid!" only works if the code is open for inspection...

      --
      UNIX? They're not even circumcised! Savages!
    2. Re:Overstating the case by Anonymous Coward · · Score: 0

      This wasn't so much a failure of the open source model as it was a failure to properly vet commits to the code of a project before accepting them into the main tree, and that could happen just as easily on a closed source development model as an open source one.

      Correct, these are both things that could happen in closed and open source. The difference is open source proponents say that nonetheless, open source has a leg up because the code is available to anyone, so bugs are found and patched faster after they are created. The argument from the closed source side is that this doesn't happen in practice because no one is looking at the code, or those that are really don't understand it. Therefore, developers are still doing the majority of the work, rather than the general community.

      Heartbleed is a score for closed source. Those trying to spin it like this is open source working are delusional.

    3. Re:Overstating the case by Anonymous Coward · · Score: 0

      > The claim is that the open-source model tends to find and correct the flaws more effectively than the closed-source model

      This this was proven true. An exploit of this size was patched and released in 1 month and most distros had a fix for it in their repos the day the embargo ended.

    4. Re:Overstating the case by Virtucon · · Score: 1

      There are companies that sell vulnerabilities to anybody with deep enough pockets. They're looking at software constantly to find exploits and I wouldn't be surprised if open source wasn't on the menu for them as well. I think open source does lead to quicker fixes once they're discovered by white hats out there unlike closed source models where a company has a vested interest in not disclosing exposures while either muddling through a fix. Case in point, the fact that Oracle knew about the zero day vulnerabilities in Java for months before addressing them. The problem is that businesses and developers seem to shrug that off rather than saying it's not acceptable and other companies just follow the same pattern. In the case of Oracle it didn't hurt them much at all and validates their lousy business practice on addressing vulnerabilities. Just looking now, in early summer 2012 when the news hit, their stock sank to $25.61/share and it just hit $42 on 4/2. So in under two years that's an almost 64% increase in their stock price.

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
    5. Re:Overstating the case by Anonymous Coward · · Score: 0

      If anything, this ase seems to pro ve it. Can you image a bug like this in a proprietary system being made public and dealt with this fast?

    6. Re:Overstating the case by Zocalo · · Score: 1

      Heartbleed is a score for closed source. Those trying to spin it like this is open source working are delusional.

      So, if this were to have happened in a closed source library, another company would have been looking at the code in order to discover the bug *how*, exactly? Even if the bug had been found by a white hat, the only recourse would have been to raise a bug report with the vendor and hope they actually did something about it. The failure for open source here isn't the development model, it's the fact it took two years for the vaunted "many eyes" to get around to looking at new code in a critical piece of the tool chain. As I noted, that's something that can easily be addressed by forcing commits be vetted before acceptance, and potentially other ways too, but again, you could also apply that approach in a closed source shop.

      --
      UNIX? They're not even circumcised! Savages!
    7. Re:Overstating the case by Anonymous Coward · · Score: 0

      The argument from the closed source side is that this doesn't happen in practice because no one is looking at the code, or those that are really don't understand it. Therefore, developers are still doing the majority of the work, rather than the general community.

      Except that that's not much of an argument. To note that the developers are the main developers in most code is near a tautology* and a near forced one if only the developers have the source code. Better arguments are: a lot of open code is created once and hardly worked on after (much like closed source, actually) so most open code isn't likely a good base for further development, too many open source developers rely too much on others to test their code or fix it, and malicious people have an easier time examining open code to hone an attack (finding the attack is likely just as much work for open/closed source in most cases since automated fuzzy testers work a lot better than trying to pour through code analyzers but actually figuring out how best to get the attack to work can make looking through the disassembly easier). In short, transparency comes with costs.

      Heartbleed is a score for closed source. Those trying to spin it like this is open source working are delusional.

      Except it's not really a score for closed source. It's just not a win for open source. As I stated above, closed source is attacked all the time with fuzzy testers. And the malicious will just disassemble the code to craft an attack. Meanwhile, as horrible as having the exact code to work off for the malicious is, it also means the virtuous can legally patch the code and release it instead of being strung up for months or years on a vendor who can't or won't release a fix. Yes, sometimes a fix is impossible--the code is in rom--, but hiding that fact to prevent exploits is shitty at best.

      So, more than anything, the biggest downside to closed source isn't that you can't patch bugs or they're harder to patch. The biggest issue is that being closed tends to imply that there's one or more entities with a possibility vested interest and ability to stop disclosure. Finding and fixing the bugs is, for most people, a much mooter point to being able to avoid the whole situation by being well informed.

      I emphatically agree with the idea that open source is no panacea towards bugs and "more eyes make bugs shallow" and other such is nonsense. But what open source is a panacea towards is the legal system being used to hinder full disclosure in the name of protecting some company's bottom line or supposedly protecting users.

      *The Linux kernel is one of the few exceptions to the rule.

    8. Re:Overstating the case by Anonymous Coward · · Score: 0

      The bug wasn't found by looking at source code; it was found via static analysis. This could have been used on closed or open source.

  10. FOSS is still safer... by jonwil · · Score: 2

    How do we know that serious security flaws don't exist in the SSL implementations used by Microsoft or other proprietary vendors?

    1. Re:FOSS is still safer... by Anonymous Coward · · Score: 0

      How do we know that serious security flaws don't exist in the SSL implementations used by Microsoft or other proprietary vendors?

      We don't. However, "Microsoft or other proprietary vendors" aren't going around making asinine claims about "many eyes making all bugs shallow" either.

      (Seriously, how did you manage to miss the point of the entire article?)

    2. Re:FOSS is still safer... by Anonymous Coward · · Score: 0

      We don't. Just as apparently we don't know if serious security flaws exist in open source projects. Just because the source is there, doesn't mean anyone is looking at it. Heartbleed shows this is true no matter how wide-spread or popular the project is.

    3. Re:FOSS is still safer... by Virtucon · · Score: 1

      We don't but that goes with any product out there. The difference is software has things like License Agreements and Terms of Service most of which give the software vendor no liability whatsoever for their product if it fails to perform. Imagine if you bought a car with a License Agreement that said "you have a license to use this vehicle however we assume no liability for it's use or damages caused by or within the vehicle." In the case of software vendors when problems are found they shrug their shoulders and introduce a patch or fix. If the software is no longer supported, they'll just direct you to their professional services folks and sign you up for custom support or the sales department to get you to buy their latest offerings.

      Another aspect of vulnerabilities like this isn't from a security but also a safety perspective. Bad software has killed people. Read "Fatal Defect." It's an older book but it's a fascinating study of bad software design that's actually killed people.

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
    4. Re:FOSS is still safer... by Anonymous Coward · · Score: 0

      We don't, but those issues can't be discovered by third party by simply looking at the source code.

    5. Re:FOSS is still safer... by Barsteward · · Score: 1

      they do... microsoft always promotes their new OSes as the "most secure ever" with saying its a comparison to their own previous OSes. they imply its the most secure OS compared to its competitors...

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    6. Re:FOSS is still safer... by Anonymous Coward · · Score: 0

      How do we know that serious security flaws don't exist in the SSL implementations used by Microsoft or other proprietary vendors?

      This is FUD - you can't prove a negative. But if there was a similar bug the same tool that found this one would have found it. Most security vulnerabilities are found by automated tools, regardless of closed or open source, and a number of security researches are pointing these tools at Microsoft's software, as regular reporting of vulnerabilities document.

  11. It doesn't. by BronsCon · · Score: 4, Insightful

    It's 6 of one, half-dozen of the other.

    Anyone can view the source of an open source project, which means anyone can find vulnerabilities in it. Specifically, hackers wishing to exploit the software, as well as users withing to audit and fix the software. But, someone who knows what they're doing has to actually look at the source for that to matter; and this rarely happens.

    Hackers must black-box closed source software to find exploits, which make it more difficult than finding them in open source software; the flip-side is that they can only by fixed by the few people who have the source. If the hacker doesn't disclose the exploit and the people with access to the code don't look for it, it goes unpatched forever.

    Open source software does provide an advantage to both sides, hackers can find exploits more easily and users can fix them more easily; with closed source, you're at the mercy of the vendor to fix their code but, at the same time, it's more difficult for a hacker to find a vulnerability without access to the source.

    Then, we consider how good fuzzing techniques have gotten and... well, as it becomes easier to find vulnerabilities in closed source software, open source starts to look better.

    --
    APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    1. Re:It doesn't. by BronsCon · · Score: 1

      And anyone who's serious about security is taking mitigation steps for every scenario that can conceive, known exploit or not. That should be SOP whether or not you have source available.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    2. Re:It doesn't. by Tontoman · · Score: 2

      It is also trivial to disassemble and decompile closed-source software. Starting with the names of routines from the public entry points, trace arguments through the code, and thus find potentially exploitable defects. It's almost as easily as the rather obscure "style" of the openssl code that had the heartbleed bug. The problem is, there is a chilling effect because of laws and uncertainty surrounding reverse engineering: http://www.chillingeffects.org... . Therefore, perhaps only criminals will do it looking for exploits, Rather then well-funded (fat enforcement target) Google development teams. Therefore closed source is more vulnerable.

    3. Re:It doesn't. by Anonymous Coward · · Score: 0

      It's 6 of one, half-dozen of the other.

      Imperial, metric, or baker's dozen?

    4. Re:It doesn't. by ratboy666 · · Score: 3, Interesting

      This myth gets trotted out again. It is arguably easier to find exploits without source. The source distracts from the discovery of an exploit. The binary simply is. The black-hat is looking for a way to subvert a system. Typically she is not interested in the documented (by source or documentation) functionality. That simply distracts from the issue which is finding out what the software actually does, especially in edge circumstances.

      This is what fuzzers do. Typically not aware of the utility of the program, they simply inject tons of junk until something breaks.

      Source availability tends to benefit people auditing and repairing more than black-hats.

      Yes, it took years for heartbleed to surface. If heartbleed (or a defect like it), was discovered due to a code audit, that speaks to the superiority of open source over closed source. If this defect is found by fuzzing or binary analysis, it is much harder to repair, as users are now at the mercy of the holder of the source. Build a matrix of Open/Closed Source vs. Bug found in Source, Bug by fuzzing/binary analysis.

      Bug found in source vs Closed Source is not applicable, giving three element. Found in source vs. Open Source (where the bug will be repaired in the source by anyone). Bug found by fuzzing... where the bug will be repaired in the source by anyone (Open Source) or the Vendor (Closed Source).

      The question then is (as I started the article): Is it easier to find bugs by source inspection? Assume big threats will HAVE the source anyway. If it was easy to find by inspection, it would be easy to fix (for examples: OpenBSD continously audits, and security has been a priority at Microsoft for the past decade). Fuzzing and binary analysis is still the preferred (quickest) method, giving the edge to Open Source. The reason is simple -- the black-hat cares about what is actually happening, and not what the source says is happening.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    5. Re:It doesn't. by BronsCon · · Score: 1

      Reading comprehension? You just agreed with me... I ended my comment by pointing out that fuzzing is super-effective. You can ignore the source and just fuzz away with open source, just like you're forced to do with closed. And, as a user, you can fix vulnerabilities in open source software, rather than having to wait for the developer to do so. In fact, as a user, you can fuzz *and* fix your open source application.

      That is to say, having the source doesn't make finding vulns easier (or harder, as you imply), it does, however, make fixing them easier.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    6. Re:It doesn't. by Anonymous Coward · · Score: 0

      This myth gets trotted out again. It is arguably easier to find exploits without source. The source distracts from the discovery of an exploit. The binary simply is. The black-hat is looking for a way to subvert a system. Typically she is not interested in the documented (by source or documentation) functionality. That simply distracts from the issue which is finding out what the software actually does, especially in edge circumstances.

      Actually, that's a rather insightful observation, which has been documented in the past. Back in the 1970s, I read an interesting test of software development that included several different styles of documentation, both inside and outside the code. The researchers salted the code with bugs, and asked programmers to fix them, with each given one of the varieties of documentation. Being good scientists, the researchers also included a "control" case which gave the programmers just the code with no documentation or comments at all. They had a very tongue-in-cheek discussion of their "dismay" with the results: The control case won hands down. The programmers with nothing but the bare, uncommented code were consistently able to find and fix the bugs faster than those who had documentation and/or internal comments in any of the styles they included.

      For some reason, this study sorta dropped out of sight. Even those of us who read it and nodded our heads tend to still pepper our code with comments, put documentation at the head of routines, and write separate user manuals, knowing full well that "studies have proven" that this is all not just useless, but actively delays the debugging process for our successors.

      Maybe it's just hard to believe that your own style of documentation isn't actually useful to the readers. Or maybe the real story is that it's only the code itself that "explains" what it's doing; everything in English or any other human language is subject to all the ambiguities that any translation entails. Only study of the code itself will really explain to you the details of what it's doing. But it's hard to accept that we're all so incompetent in our own native language that we can't explain our own work to others ...

    7. Re:It doesn't. by Anonymous Coward · · Score: 0

      The analogy is good except that vaccine manufacturers have money to combat that perception (and rightly so) they do. In the case of the Open Source vs Proprietary Product. It's the for profit companies who have the money to shout loudly about this anecdotal failure of an Open Source product. Notice the media attention on this one is a bit louder than about other bugs of a proprietary nature. "Is it OK to report this as news? Our sponsor, Microsoft, says 'yes, go ahead'."

    8. Re:It doesn't. by Anonymous Coward · · Score: 0

      also keep in mind that closed source code can still be acquired through various channels.
      if someone really wants to exploit Internet Explorer, there are probably ways to get your hands on the code.

    9. Re:It doesn't. by ratboy666 · · Score: 1

      BronsCon

      Yes, I am in violent agreement with you. I think that this is such an important point that I wanted to (re) emphasize it. You know the drill: tell them what you're going to tell them; tell them; tell them what you've told them...

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    10. Re:It doesn't. by BronsCon · · Score: 1

      Thank you for clarifying that... a bit frazzled today, bad day at work.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    11. Re:It doesn't. by BronsCon · · Score: 1

      Or, you know, fuzz the hell out of it until you find something, like I said in my post. No source necessary. At least with open source, I can fuzz it until I find a vulnerability, then find the code that caused the vulnerability and fix it.

      I mean, I suppose if I got my hands on the source for IE, I could fix that, as well, but why go through the trouble when I can readily obtain the source for a number of other browsers?

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    12. Re:It doesn't. by BronsCon · · Score: 1

      Absolutely! This isn't something that could have been foreseen, but I've been noticing more of a tendency toward "well, I can't stop everything, so why bother" lately, and I'm beyond not sure I like it; I'm sure I don't. You seem to get this, thank you for giving me hope for humanity. :)

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
  12. Not enough eyes by Phillip2 · · Score: 4, Insightful

    So, the "with many eyes all bugs are shallow" notion fails. There were not enough eyes on the OpenSSL library, which is why nobody discovered the bug.

    Except that someone did discover the bug, when they were looking at the code because it was open source. And they did report it. And it did get fixed. Later than anyone would want of course. But it happened. Maybe the similar errors would and are being missed in the Windows and Mac implementations.

    1. Re:Not enough eyes by Marginal+Coward · · Score: 1

      Good point. But maybe they would have been missed by the bad guys, too. Maybe open source makes it easier for the good guys to find bugs but it also makes it easier for the bad guys to find bugs that the good guys haven't found yet. I don't know if there are bad guys who are scouring open source code for things like this, trying to find it first, but bad guys who enjoy finding exploits like this (or get paid to), might prefer to look at open source than disassembly.

      My point isn't that open source is or isn't better than closed in this regard, but that the important factor is who finds an exploit first - whether it's in open source or not. And that probably depends mostly on who's focusing their attention on it.

      That said, if I were a bad guy, the rest of the OpenSSL library's open source would seem like a pretty juicy read right now. Then again, it probably sounds like fun to the good guys too.

    2. Re:Not enough eyes by Rich0 · · Score: 1

      That said, if I were a bad guy, the rest of the OpenSSL library's open source would seem like a pretty juicy read right now. Then again, it probably sounds like fun to the good guys too.

      Do you think that the bad guys never thought to read the source before now? I'm sure the NSA has a dozen more exploits against every SSL implementation out there, open or closed. It isn't like the Germans published the specs for Enigma, or that the Iranians posted the design of their centrifuges for all to see.

    3. Re:Not enough eyes by Kjella · · Score: 1

      So, the "with many eyes all bugs are shallow" notion fails. There were not enough eyes on the OpenSSL library, which is why nobody discovered the bug.

      I think that's a lie, the truth is everybody thought there were so many eyes on the code they all glazed over and nobody really looked. After all, if this was my company and the line was "Well everybody who works here has access to the source repository so I'm sure that someone would find it..." there'd be plenty alarm bells going off in my head. For sure, bumping into buggy code is often the way you find out about bugs but for security critical code it's review, more review, audits, all that really boring red tape that counts to stop it getting through in the first place. If the rumors are true, the NSA caught on pretty quick which is because they have lots of smart people getting paid well to look for exactly these kinds of issues. This is not magic. But it's the kind of boring shit you usually have to pay people to get done.

      Except for corporate sponsored positions - which also typically have their own agendas - the work that gets done is the work people feel like doing. If what you need is 50% development, 50% review but 90% of what the people involved are interested in is the development of their own pet features well you don't have any authority to boss people around. You can ask the reviewers to be a bottleneck which will quickly turn sour, you can ask them to rubber stamp it faster or you can add people who really shouldn't be reviewers but you can't hire more qualified reviewers. Waiting a few years for someone to stumble into it just isn't a good process, no matter how much people pretend this proves how OSS "works".

      --
      Live today, because you never know what tomorrow brings
    4. Re:Not enough eyes by Marginal+Coward · · Score: 1

      Do you think that the bad guys never thought to read the source before now?

      [head slap!] Gosh, maybe you're right - maybe they did think of reading the source code to a library that's widely used to help enforce security. In fact, being bad guys and all, that sounds like exactly the kind of thing they would do. Now, why didn't I think of that?...

      Actually, I was just trying to make the point that this kind of issue draws particular attention to the offending library. Sorry if I didn't spell that out clearly enough for the casual reader.

    5. Re:Not enough eyes by Cl1mh4224rd · · Score: 1

      Except that someone did discover the bug, when they were looking at the code because it was open source.

      I don't know how Google's Neel Mehta discovered the bug, but Codenomicon didn't discover it by looking at the code.

      “We developed a product called Safeguard, which automatically tests things like encryption and authentication,” [Codenomicon's CEO, David Chartier] said. “We started testing the product on our own infrastructure, which uses Open SSL. And that’s how we found the bug.”

      Source

      --
      People will pass up steak once a week, for crap every day.
    6. Re:Not enough eyes by Anonymous Coward · · Score: 0

      Black Hats don't give a shit about the source code. How many times does a "Grey Hat" have to tell all of you STUPID FRIGGIN' IDIOTS that?

      The source code's a distraction. It doesn't do anything but MAYBE provide confirmation after the fact that you've found the weakness you thought you had. The NSA might do a code analysis and review after the exploit's found to do just that. But they'd part of a very small crowd that bothers there. Looking at the code doesn't always reveal the exploitable flaw. Sometimes it's a particular piece of code cowpiled by a given version of the C or C++ cowpiler that does it. Sometimes, even, it's in the specification of a given protocol and ALL implementations are fried out of box. Flaws that are leveraged by exploits aren't always like this- they're not always in the source code of the exploitable app.

    7. Re:Not enough eyes by Capt.Albatross · · Score: 1

      So, the "with many eyes all bugs are shallow" notion fails. There were not enough eyes on the OpenSSL library, which is why nobody discovered the bug.

      Except that someone did discover the bug...

      The 'many eyes' principle (aka Linus' Law) states "with enough eyes, all bugs are shallow". This claims a good deal more than simply that bugs are likely to be found eventually. Given the seriousness of this bug and the length of time taken to expose it, any claim that 'many eyes' worked in this case depends on a useless definition of 'worked'.

      Maybe the similar errors would and are being missed in the Windows and Mac implementations.

      That is quite likely, but irrelevant. This severity and duration of the OpenSSL bug are not mitigated by the hypothetical (or even real) failings of closed-source vendors.

      The open source community should move beyond this self-serving aphorism and adopt a more engineering-like approach to the correctness of critical software. Fortunately, I think the people actually doing the development are well aware of this.

    8. Re:Not enough eyes by Anonymous Coward · · Score: 0

      When I look for it I can find nothing that suggests this bug was found by code inspection. It's hard to find anything, but it looks like Codenomicon found it by black box testing. If you have different data please post it.

  13. Looking forward by petes_PoV · · Score: 1

    The issue is not that some open source software has a bug in it. We're all grown-up enough (I hope) to realise that NO software is ever perfect.

    The only interesting point about this situation is how the Open Source world reacts to it and what processes get put in place to reduce the risk of a similar situation arising in the future.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
  14. It doesn't. by Anonymous Coward · · Score: 0

    The point of open source is that it allows independent code inspection, not that it promises security. Microsoft has had many vulnerabilities discovered and exploited without releasing source code. The vulnerability in question may not have even been discovered by an inspection of the code. All it would take is a typo to have your code request bob (4 letters) instead of bob (3 letters).

  15. Given enough $, all people are shallow... by Anonymous Coward · · Score: 1

    Bugs happen, leaving the source open just gives individuals an opportunity to find them. It doesn't imply that all bugs will be found instantaneously, just that anyone can look for the bugs. Compare this to closed source, which has a very narrow group of people examining the code base, and only their word that everything is sound. I hate to think how long, if ever, a flaw like this would go unchecked and exploited if only the gatekeepers where allowed to check out the goods.

  16. Uh, what? by Zontar+The+Mindless · · Score: 5, Insightful

    Q: How Does Heartbleed Alter the 'Open Source Is Safer' Discussion?

    A: It doesn't. OSS is purported to be a *better* software development methodology. "Better" != "perfect". TFS is a troll.

    --
    Il n'y a pas de Planet B.
    1. Re:Uh, what? by Anonymous Coward · · Score: 0

      Hi APK's Mom!!

    2. Re:Uh, what? by Anonymous Coward · · Score: 0

      Another typical internet tard throwing around the word 'libel' without really knowing what it means...you can't write code to save your life and your grasp on legal matters is even worse.

  17. This bug was found in OpenSSL because it was open by Anonymous Coward · · Score: 5, Insightful

    What hasn't been found in closed source software because it is too inconvenient to look?

  18. Re:Open source was never safer by Anonymous Coward · · Score: 5, Insightful

    I don't know, Microsoft got caught about being able to waltz through the password check with full spaces, which is slightly worse than forgetting to place a character limit back onto something. Admittedly the stakes are not the same, but you can check it, and enough do that it works.
    It's safer in terms of checking for back doors, sloppy coding anyone can do.

  19. security through obscurity by Anonymous Coward · · Score: 0

    /sarcasm/ And proprietary software's security through obscurity is a so much better model. /end sarcasm/

    At least it's known if this has gotten fixed and it will hopefully keep developers from getting too lax in the future. Both of which are unkowns in proprietary software.

  20. NSA by Anonymous Coward · · Score: 1

    The huge problem with OSS is that if no one takes the responsibility to do a good code audit for a project, the NSA will do that independently, file the found exploits, and tell nobody.

    1. Re:NSA by hawguy · · Score: 1

      The huge problem with OSS is that if no one takes the responsibility to do a good code audit for a project, the NSA will do that independently, file the found exploits, and tell nobody.

      Of course, the flip side is that if you *want* to do a good code audit for software you're using, you can do it on your own with open source software (and you can review code changes in patches before applying them). However, with closed source software, you can (usually) only take the word of the closed source company and have to trust that they haven't purposely inserted back doors into the code.

      And once one company does the audit, they can share it with others (or a group of companies could share the costs of the audit), and all users, no matter how large or small, can validate that the code they are running matches the audited code.

      Of course, an audit isn't a guarantee of finding a bug (which is just as true for closed source software as it is for open source software), but at least with open source code, a company that finds a bug can choose to fix it immediately without waiting for it to filter through a large company's release process.

  21. w/o disclosure, exploiting closed source tempting by anapsix · · Score: 1

    similar issue in closed source would have less chance of discovery, and if/when discovered would not be disclosed in the same way, but most like attempted to be kept on the dl.. while being exploited by interested parties.

  22. Code written by Humans is always flawed. by jlbprof · · Score: 1

    At least with FOSS, you can quickly identify and fix problems that show up. Proprietary software fixes only happen when they have no other choice but to fix it.

    --
    I go out of my way to complicate the simple things, so that I can simplify the complicated things.
    1. Re:Code written by Humans is always flawed. by Anonymous Coward · · Score: 0

      Especially when said code is written in C.

  23. Security vs insecurity by Anonymous Coward · · Score: 0

    Proponents of open/closed source both make valid points about security, however both leave you with a FALSE sense of security.

    Both these statements are false at some level:
    Open source because so many look at it, it has to be secure. (But obviously, things can be missed)
    Closed is written by professionals (hopefully) and even if there's a flaw, no one has the code to detect it, so it has to be secure.

    The biggest difference that I see is that leaks like this in open source blow up bigger and get a lot more media attention. Bugs just as bad hit closed source all the time, but have an active effort by the company (Again, hopefully) to keep the bugs quiet and patch them. If this wasn't a problem with closed-source, there would be no patches, which is true in open source as well. Obviously, I have a bias towards the open source model. But these are my random thoughts.

  24. switch to wind, solar, magnetic etc,, power by Anonymous Coward · · Score: 0

    that'll be bollixed by the WMD on credit cabals too http://www.youtube.com/results?search_query=weather+manipulation+energy+costs but we we might not be paying to poison ourselves quite so much

  25. What if... by chiefcrash · · Score: 4, Insightful

    If the bug was in some proprietary SSL stack, would we even have heard about it? Would it have even been fixed? Who knows. That's the WHOLE POINT...

    --
    Show me on the 1st Amendment bobblehead where the moderator touched you...
    1. Re:What if... by qzzpjs · · Score: 1

      Apple - two months ago with the misplaced goto statement. We certainly heard about it and it was fixed pretty quickly.

    2. Re:What if... by chiefcrash · · Score: 2

      You mean the bug that was spotted by a non-Apple researcher after reviewing Apple's publicly posted source code? The bug Apple didn't want to admit to, tried to quietly fix for *some* devices, understated the problem, then spent several days delaying the fix for the rest of their devices? What was the point you were trying to make again?

      --
      Show me on the 1st Amendment bobblehead where the moderator touched you...
  26. How would proprietary software have handled this? by Todd+Knarr · · Score: 4, Insightful

    This doesn't really change it, because think how a proprietary SSL library would've handled this. The vulnerability was found specifically because the source code was available and someone other than the owners went looking for problems. When was the last time you saw the source code for a piece of proprietary software available for anyone to look at? If it's available at all, it's under strict license terms that would've prevented anyone finding this vulnerability from saying anything to anyone about it. And the vendor, not wanting the PR problem that admitting to a problem would cause, would do exactly what they've done with so many other vulnerabilities in the past: sit on it and do nothing about it, to avoid giving anyone a hint that there's a problem. We'd still have been vulnerable, but we wouldn't know about it and wouldn't know we needed to do something to protect ourselves. Is that really more secure?

    And if proprietary software is written so well that such vulnerabilities aren't as common, then why is it that the largest number of vulnerabilities are reported in proprietary software? And that despite more people being able to look for vulnerabilities in open-source software. In fact, being a professional software developer and knowing people working in the field, I'm fairly sure the average piece of proprietary software is of worse quality than the average open-source project. It's the inevitable effect of hiring the lowest-cost developers you can find combined with treating the fixing of bugs as a cost and prioritizing adding new features over fixing problems that nobody's complained about yet. And with nobody outside the company ever seeing the code, you're not going to be embarrassed or mocked for just how absolutely horrid that code is. The Daily WTF is based on reality, remember, and from personal experience I can tell you they aren't exaggerating. If anything, like Dilbert they're toning it down until it's semi-believable.

  27. Comment removed by account_deleted · · Score: 4, Interesting

    Comment removed based on user account deletion

  28. "many eyes" by Anonymous Coward · · Score: 0

    Only true when the developer(s) can own up to the problem. Last time I tried reporting a problem, it took 18 months to get a fix. A majority of that time was spent proving that there was indeed a bug, and it took another developer confirming it's existence before the issue was promptly reopened and fixed.

    That's how you end up with so many duplicates on bug trackers, closing reports while other users run into the same problems.

  29. This is more like... by Anonymous Coward · · Score: 0

    The series of process errors that resulted in Chernobyl(sp?), Three Mile Island, and Fukushima Dai(ii?)chi.

    A small series of 'innoculous' oversites leading to the sort of far reached disaster that could end the lives of a non-trivial number of people.

    And don't think that it couldn't, since any number of other countries could have been using this to catch insurgents or free thinkers for up to the last 2 years!

  30. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  31. SChannel by infernalC · · Score: 2

    Most of the non-OpenSSL instances of TLS implementations out there are probably SChannel.

    I would be shocked if Microsoft hadn't had equally severe bugs, and further surprised if they could fix them as fast.

    1. Re:SChannel by Anonymous Coward · · Score: 0

      Worst case scenario for Microsoft software is that after all the work to fix said bug, you have to wait $DAYS_IN_Month -1 to even get the fix.

  32. Comment removed by account_deleted · · Score: 3, Informative

    Comment removed based on user account deletion

  33. Well written code by Anonymous Coward · · Score: 0

    Just because it is open source, it does not make it well written. If a project does not have enough resources, it will suffer. If you try to write it yourself, you will introduce bugs. Existing code isn't better, but it has been tested longer.

    This is a project that is supported by mostly one person. They wrote their own memory management when others exists that have been tested for these types of mistakes (It was done for legacy support and performance).

    I don't want to say that this code was poorly written. It was more of a general statement. I did look at the code for this and I saw where the fix was refactored a bit. Wrapping magic numbers into a variable did make it easier for me to read. I spent a long time looking at what was wrong with the original code. I knew where it was wrong, but could not follow it back to see where it went wrong. I decided to just trust that it was wrong and move on.

    I think anyone could have made this mistake and I am sure others are out there. I think we got lucky. This could have gone the other way to be the worst worm we have ever seen.

    Quick disclaimer: I learned C++ once and can kind of still read it. Some code is obviously easier than other for a novice like me. I have mad respect for devs that work at this level. I mean no disrespect with these comments.

  34. Two things to note by goathumper · · Score: 1

    "Given enough eyeballs, all bugs are shallow" has proven true time and again. The key point in the phrase is "enough eyeballs". In this particular case, the affected software was OpenSSL. Let's examine that for a second.

    OpenSSL is a cryptography library. Cryptography is, by definition, a very "exclusive" field of development due to the complex mathematics and rigorous rules that have to be followed in order to successfully contribute. It then follows that the audience that is both capable and willing to contribute to the project is very, very small in relation to the audiences readily available to other projects such as Apache Tomcat or GNOME.

    This is where the "enough eyeballs" comes into play: clearly, for the longest time, there weren't enough. The reason is understandable and explained in the above paragraph - the vast majority of software developers out there are probably not able to contribute meaningfully to a project such as OpenSSL.

    However, and echoing on other comments that have already been posted, the good news is that because it was open source the vulnerability was detected and corrected. Had it been closed-source it might never have been found - let alone acknowledged or even fixed. I'll take that over a walled garden any day of the week and twice on Sunday. That - to me, at least - reinforces the argument that open-source is safer and more secure than closed-source, not the other way around as some would like to believe. This is by the simple fact that larger number of eyeballs can be brought to bear on a piece of software in order to eventually shallow out the bugs.

    How many closed-source companies are willing to make that level of investment in their software quality if they can still be profitable without having to do it? Further still, what if making that investment would bring profitability into question? Would they still make the investment? I think not...

  35. It is still safer by Anonymous Coward · · Score: 0

    Safer means less chance for an issue. But just like in gambling, as the odds get worse, the jackpot goes up.
    We have seen now someone win 100M, somthing that happens every 40 years.

    Vajk

  36. it IS safer by roman_mir · · Score: 2

    What if this was not 'OpenSSL' but instead it was some form of 'ClosedSSL' library that had this problem in it?

    NSA would still have access to THAT code, you can bet your ass they would, they wouldn't leave a project like that alone. However nobody else would know (unless stumbling upon it by chance or being able to access the source OR if some insider SOLD that information to somebody on the outside and now you'd have a vulnerability that is exploited by the gov't and by shadiest of the organisations/people out there).

    This does not change the discussion in terms of open source code being safer, this changes the discussion around certain practices of development / testing and also this may attract more attention of people towards the SECURITY of our information on the Internet and hopefully we'll move in the direction of working out the details of actually much more SECURE methods of communications.

    I certainly have a few ideas of my own that I would like to implement now, but never mind that. The point is that this is good stuff, it finally shed a light on this topic, that should have had much more light on it for a much longer period of time in the first place.

    We need better methods around building security within our systems and I think this raises the bar.

  37. Re:Open source was never safer by unixisc · · Score: 1

    How?

  38. Re:Open source was never safer by LordThyGod · · Score: 5, Insightful

    Closed source was always safer.

    One word for you: Microsoft. Maybe two: Adobe.

  39. Re:This bug was found in OpenSSL because it was op by Anonymous Coward · · Score: 0

    All the convenient "leaks" that are placed there to be helpful to the NSA?

    You know - the "all American Microsoft" that is bowing for their master, being a trustful servant?

  40. Re:Open source was never safer by Jeremiah+Cornelius · · Score: 3, Interesting

    Closed source is not inherently safer. Raymond's proposition is theoretically sound, however in actual practice, the NSA has "many eyes"...

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  41. Eric Raymond Delusional Asshat by Anonymous Coward · · Score: 0

    Eric Raymond famously said, 'given enough eyeballs, all bugs are shallow.'

    In the delusional make believe world of open source, yes. In the real world, no. In the real world, the only people spending any meaningful amount of time scrutinizing the source code of ANY project are the few people actually working on it.

    In addition to once again disproving the delusional 'all bugs are shallow' bullshit, the real problem with OpenSSL was lack of proper testing, another problem that plagues open source projects because proper testing isn't fun.

  42. Re:Open source was never safer by MightyMartian · · Score: 4, Insightful

    Only if one buys that "security through obscurity" is a legitimate form of network safety. A decade's worth of Internet Explorer and ActiveX vulnerabilities would suggest you're wrong.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  43. Eric Raymond is more or less right by Anonymous Coward · · Score: 0

    When a bug makes itself obvious to many users, then many eyeballs do get applied, find it, and come up with a fix more quickly. Heartbleed was not obvious to anybody except it's perpetrators. Also, the general case implicit assumption of Raymond's assertion is that many users means many programmers who can understand the code and will bother to look at it before they use it. This is demonstrably false to even the most casual observer.

    The problem with code that provides "infrastructure" like operating system kernels or internet/network stack software is that when they run smoothly, almost nobody outside it's small group of developers bothers looking at the source. Heartbleed runs quite smoothly as it sends off those passwords, so nobody looks.

  44. Better != Perfect by DrJimbo · · Score: 0

    Next question.

    --
    We don't see the world as it is, we see it as we are.
    -- Anais Nin
  45. bugs are not the issue by csumpi · · Score: 1

    bugs are not the issue. it's how systems get updated once the bugs are fixed. without automatic security updates, heartbleed will be with us for a long long time.

    1. Re:bugs are not the issue by Anonymous Coward · · Score: 0

      I think it's time for distributions to start distinguishing themselves again.
      And i don't mean by marketing.
      I wonder who will be the first to dump openssl.
      It deserves a quick death.

  46. Re:This was positive by dublin · · Score: 1

    So there was a bug in OpenSSL. Big bug, yes, but that's not the reason it was (and still is!) a big problem.

    The genesis of the big problem is one of monoculture, not only of OpenSSL being the dominant SSL implementation, but probably more importantly, the fact that pretty much all Internet security that is accessible and matters to ordinary users is SSL/TLS in the first place.

    If you think this is bad, imagine what happens if the fundamantals of SSL itself are compromised: What would we replace it with? How, considering this is effectively the only secure connection technology available across all common OSes and embedded devices? How long would that take? (Years, at least, I'd wager...)

    What we need is more flexible security methods in the first place, and open, standard implementations (like OpenSSL, but growable) that can allow us to proactively extend security methods as the net matures, and *quickly* address bug-based vulnerabilities when that approach fails. (Note that this may require the implementation of some kind of standard "secuirity code VM", so new code and new methods can be easily distributed even to older systems that may not be fully supported anymore. And no, I'm not glossing over things like limits on code space, memory, and the like, nothing will allow every system to be upgraded, but we do need some way to allow and authenticate that (while preventing bad guys, including governments, from using the mechanism to create weaknesses.))

    --
    "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
  47. It doesn't. by Anonymous Coward · · Score: 1

    This alters the "Open source is safer" discussion in the same way that someone dying from an allergic reaction to a vaccine would alter the "Getting vaccinated is safer" discussion.

  48. Re:Open source was never safer by erroneus · · Score: 5, Interesting

    Closed source is hazardous in many ways. Along with being more frequently targeted, the NSA revelations showed that Microsoft worked with the NSA when deciding how quickly to close some holes. Another hazard is the threat of being attacked and/or sued by companies whose products were found to have problems.

    No question the heartbleed thing is a huge and embarassing problem. But you know? It's actually kind of hard to count the number of high-profile vulnerabilities in F/OSS software as not a whole lot come to mind. On the other hand, the list is enormous for closed source from large companies... also hard to count but for another reason.

    It does highlight one important thing about F/OSS, though. Just because a project has enjoyed a long, stable and wide deployment, code auditing and other security practices are pretty important and just because it's a very mature project doesn't mean something hasn't been there a long time and had simply gone unnoticed for a long, long time. People need wakeup calls from time to time and F/OSS developers can be among the worst when it comes to their attitudes about their territories and kingdoms. (I can't ever pass up the opportunity to complain about GIMP and GNOME... jackasses, the lot of them.)

  49. The bug was found because it was open source.. by Black+Copter+Control · · Score: 4, Informative
    Nobody was seriously inerested in forking it... But the OpenBSD people have now gotten their claws into it, and chances are it's gonna be fixed bigtime .... or else!.

    The problem was found because the code was Open Source. If it had been closed source, then the bug would still be secret. To the extent to which the bug was recognized (or commissioned) and exploited by the likes of the NSA, it would have probably remained secret for a lot longer.

    According to Microsoft's EULA, for example, finding -- much less fixing -- such a bug is illegal. If the NSA had paid them to put such a bug into the Windows version of SSL, then it would probably remain unpatched for years after someone had pointed it out to them as an exploitable bug.,, and anybody openly reporting such a bug, even after 6 months of trying to get MS to fix it, would be roundly criticized for disclosing the bug 'prematurely'.
    Even then, it would probably not be fixed by Microsoft until at least the next monthly bug release cycle (or even the one after that.

    With the code being Open Source, the problem got fixed faster than yesterday. Period. If the OpenSSL people refused to fix it, then it would have been forked. ... and more to the point: Such a security-centric fork would have been legal.

    .. and that is the power and freedom of Free, and Open Source software.

    --
    OS Software is like love: The best way to make it grow is to give it away.
    1. Re:The bug was found because it was open source.. by Anonymous Coward · · Score: 0

      Epic history fail for the win!

      OpenBSD has had this in their tree since 2000. It started out as a fork of SSLeay in 1998 when Young of SSLeay went off to work for RSA. It became part of the OpenBSD project two years after that as part of their cryptographic stack.

      They just decided it was time to do proper audits on the project again to catch screwups. Which is what you should be talking to. If anything, they're not cleaning it often enough. The real root cause for Heartbleed isn't that someone added a feature and then added another one that broke the first one (bullshit.)- the root cause is a notion of adding an ill-advised feature to TLS and then not vetting/crippling the behavior so that it can't really be misused or "oopsed" or of one where they didn't push back. This "feature" is beyond tragically idiotic. There should be no lengths of things involved with an "are you there still" query- just a yes/no, a boolean single character response was all that was needed.

      Are people sure that it's not something the NSA wended into the whole thing? They've been guilty of injecting exploits into other security frameworks in development by RFC or by standards committees other than the IETF. I can't say that I am- and that many of these things are...heh...suspect.

  50. Windows source code is open source to US governmen by Anonymous Coward · · Score: 0

    Lets not forget that the NSA has Windows source code and can find and exploit bugs without reporting them to Microsoft.

    The heartbleed bug is mostly only useful to the NSA because once you extract the servers private key you still need to be able to eavesdrop on the targets communications. Most people don't have the ability to do that.

  51. Re-engineering the web by Anonymous Coward · · Score: 0

    Do we want incubated and awesomely connected, or do we want "free" and unchallenged? This duality is basic to our human nature but again and again its simply a matter of choosing this way and that way without a need to "battle it" out for ever? We are social creatures and we associate everything with everything, technology is a particularly important expression of it.

    Should we re-engineer the idea that makes the web, the web? In other should we really venture out to recreate a smarter engine behind the hardware platform? Mobile particularly shows the need for a stronger hardware platform integration. This seems daunting and it truly is however it means that we have re-engineer the root foundations of the internet, meaning the network systems that connect the device platforms. IF we are able to successfully re-envision both, than yes we aptly have the opportunity to leave the "old world" in the dust.

    Retweet about this tonight: Let me tell you about a company that wants to re-engineer the IRS. Talk about daunting. The site: thenewirs.com a private allocation vote directly submitted to the IRS. Think about it like this, why do we hold elections? So that elected officials can send tax monies to where we want so we can get the things that we want. This stands to integrate even further our direct will as a democratic power system. [check my tweets @Rvela82]

    What can be the catalyst for a tighter internet to device to human (i.e.. the Home)? The possibilities are quite varied so my idea is just prospect. Internet fed through the electric outlet. This technology came as quick as it went away from the media's attention. This could be a means to make "the power lines" of the internet to make it truly open yet employ key encryptions on the outlet circuitry itself and in conjunction with the device platform level security initiator, this can create new methodologies for the new web.

    I hate to build upon this idea because as I truly said possibilities exist to widely for one person to conceptualize. We have to open the discussion and use the ideas as inheritantly employable configurations. Yet I will continue in the aspect that the integration has to happen systematically, and that theorizing on it is truly the whimsey and muse of a man.

    Take for example, a user end software layer to this model, call it 'The Uniform Web Internet Console' its a console written directly on the device that configures the internet for the individual users. In essence making it impossible for device to be reached by externally controlled networks. Think like negating websites based on their hosting platform, from the top builders down to custom written programs written on IBM versus coded on HP? etc. If this system seems to complicated it actually isn't - I'm a millennial I definitely know it can be made quite easily interpretable for my relative audience as a user experience.

    We need this program so that world wide corporate entities will seek the new types of partnerships that they never thought they needed. Is this effect a truly feasible outcome from such a programming perspective. Yes because it reengineers the internet in a way that secures it at its roots. In other words its revolution.

    Just like www.newirs.com reinvents establishments based on certain aspects of political oversight, the people's primary responsibility, to make it simpler, easier, more agile. This does it for the world wide web and it causes more free technologies at a local level to sprout with new embedded logic capabilities, hence more change at the human level.

    Consortium is the lifeblood of civilization.

    Oh and Slashdot I'm not an anyomous coward, I'm RJ betch.
    For more material on the UWIC that I've written about, reach out to me via twitter @rvela82

  52. And.. by Anonymous Coward · · Score: 0

    it had been run through automated analysis software and passed because a different part of the code was doing something naughty for which there hadn't been a testcase previously. (Mallocing, freeing, then remallocing a section of memory and assuming the pointer address would remain the same).

    A bigger issue might be the 'tunnel vision' approach of analysis. This bug was the result of *MULTIPLE* little issues resulting in a big issue. If anybody had actually stepped through that entire process of code this problem would've been found earlier, but most likely the function itself was scrutinized, passed 'first glance' muster, then was forgotten about as a non-critical codepath.

    As this issue has shown however, the non-critical codepaths are ripe for exploitation by malicious actors, be they private or state.

  53. Better documentation of source code is needed by Eravnrekaree · · Score: 2

    I do believe open source is safer as it does absolutely allow for independant party review, which is how this bug was found. Because outside parties had access to OpenSSL they were able to find the problem, whereas with closed source software it might have never been found, or found but hushed up by the company. Proprietary software has just as many bugs as open source, if not more, the difference is there is less accountability.

    That being said, the full potential of open source software in independant party review is not brought to its full potential but the fact that a lot of open source software is poorly documented as to the internal construction of the code. This ends up wasting time for programmers to basically have to spend more time than it should to learn the internals, and even wastes time of those running the project basically repeating explanations of the code whereas if they were to make some documentation people could get many more answers without having to bother the project leads. It makes the learning curve much steeper that when dealing with software that has a lot of code, to not have any documentation on how that code fits together. On one hand, we say that open source allows people to review the code, but just opening the source alone does not make it easy as possible for this to happen, the code needs internals documentation or else it often will take simply too much time for people on the outside for people to penetrate it. Many open source software projects end up with a cliche who understands the internals of the software because they wrote it, but its difficult for those on the outside to penetrate. Even for an expert programmer, being able to access documentation speeds up the time to become familiar with the code immensely.

    Not doing code documentation is a poor practice and open source developers should document what they are doing for others and as well to save time by preventing having to explain things over and over again to newcomers.

    1. Re:Better documentation of source code is needed by Anonymous Coward · · Score: 0

      As well as code documentation Heartbleed also shows that open source projects need to up their game by publishing test plans and test reports for the original project and for all changes. This includes all the testing done by the developers before submitting changes to a release candidate branch as well as any independent integration testing exercise. This applies especially to critical projects like OpenSSL. All those eyeballs can then look for significant omissions in the test plans as well.

      Of course test planning, test execution and test reporting is pretty boring stuff, so the problem then is how to incentivise enough people to spend enough time and effort on it. Commercial organisations incentivise their testers by paying them. Any organisation handing out money to improve open source could usefully spend some of it this way. Advocates of open source should be doing this with any open source project that they are responsible for, to demonstrate their commitment to the quality of open source software.

  54. Oh well by mx_mx_mx · · Score: 1

    How 'bout that SSL bug discovered not recently in OSX/iOS?

    Sure the open source is not a silver bullet, nobody argues this.
    And law of big numbers sure does it thing, yes, shit happens in open source just as well.
    But how often this happens in open source vs closed source?
    How often such incidents go unnoticed in closed source world?

    --
    Linux forever
  55. Re:Open source was never safer by Anonymous Coward · · Score: 4, Insightful

    PlUU-lease! Where is my "overrated" mods when I need them?

    The NSA is why my hair has fallen out and my gut has gotten big. They're also behind the big mudslide in Washington. In fact, they are the boogeyman for EVERYTHING!

    God you people get annoying.

  56. Open Source by mfh · · Score: 2

    It's BECAUSE of open source we even learned about Heartbleed. If it was closed source the hole would still exist hidden in the shadows.

    --
    The dangers of knowledge trigger emotional distress in human beings.
    1. Re:Open Source by Z00L00K · · Score: 1

      If I had mod points I would mod parent up!

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  57. social engineering flaw by globaljustin · · Score: 0

    Actually it can't. That's kind of the point of git.

    so 'git' is just unhackable...its perfectly secure...no way someone could've put a gun to the guy's head while he sat in front of his computer to make these changes...

    if I was the criminal/CIA agent, i'd actually help the guy with an alibi..maybe tell him to claim it "was an accident"

    no way that people would infect a system ***and*** lie about it...b/c that never happens simultaneously /sarcasm

    --
    Thank you Dave Raggett
    1. Re:social engineering flaw by Anonymous Coward · · Score: 0

      So you are a witness to the conspiracy to hide a backdoor into OpenSSL? No? You're just fabricating speculation about what possibly happened and you've got no eyewitness testimony? Cool story bro.

    2. Re:social engineering flaw by yanyan · · Score: 1, Informative

      so 'git' is just unhackable...its perfectly secure...no way someone could've put a gun to the guy's head while he sat in front of his computer to make these changes...

      with a hot chick giving him a blowjob, can't leave that part out.

  58. Could bad guys be staring at git feeds? by cant_get_a_good_nick · · Score: 1

    If I'm a malicious hacker, or the NSA, but I repeat myself....

    I'd be now (if i wasn't before) checking the feeds for gnutls, nss,, and openssl, hoping to catch he bug before anyone else, so i can exploit it.

    That said, I'd also be checking out the best decompilers to see if that helps me find bugs in closed source code. Im sure people have looked online for Windows source code to see if there are any ways to exploit it. In this case, a small group of hackers would have the code, and would necessarily want to limit the number of people aware of those exploits.

    In a nutshell, we're all screwed.

  59. Re:Open source was never safer by Joe+U · · Score: 1, Interesting

    One word for you: Microsoft.

    2003 called, they want your Microsoft back. The Microsoft of 2014 has a better security record than almost every other vendor in the consumer field.

    I would worry more about Flash, Java, Firefox and Android.

  60. Pedantic Man to the rescue! by almitydave · · Score: 3, Informative

    " just about every SSL-encrypted internet communication over the last two years has been compromised."

    No, it really hasn't.

    It's accurate to say that just about every Open-SSL encrypted session for servers that were using NEW versions of OpenSSL (not all those ones out there still stuck on 0.9.8(whatever) that never had the bug) were potentially vulnerable to attack.

    That's bad, but it's a universe away from "every SSL session is compromized!!!" because that's not really true.

    They were vulnerable to attack, that is to say, the security was compromised. He didn't say they were hacked, stolen, eavesdropped, or surreptitiously recorded.

    compromise: to expose or make vulnerable to danger, suspicion, scandal, etc.; jeopardize: a military oversight that compromised the nation's defenses.

    I've noticed that a lot of TV sci-fi confuses "compromise" with "breach"; as in hull, shields, defenses, etc.

    --
    my, your, his/her/its, our, your, their
    I'm, you're, he's/she's/it's, we're, you're, they're
    1. Re:Pedantic Man to the rescue! by the+phantom · · Score: 2

      Except that the argument wasn't really "potentially vulnerable to attack" is not the same as "compromised" (though it is certainly easy to see how one could come to that conclusion by ignoring the context---and maybe I am misinterpreting the parent, as well), the argument was that all (but only) SSL sessions using the newer versions of OpenSSL were/are vulnerable (i.e. compromised), and that by virtue of not every server in the world automatically being updated to these newer versions, the statement "every SSL session is compromised" was hyperbole.

      One should also note that while the dictionary definition of "compromised" is essentially identical to "vulnerable," there are nuances of meaning in the way in which the two words are used. I would suspect that most people would regard something being "compromised" as more severe than something being "vulnerable." In fact, your example of science fiction seems to make my argument for me. You aren't really disagreeing with the parent, only nitpicking semantics (unless you really do believe that "every SSL session has been compromised," in which case there is a bigger problem with SSL than Heartbleed). If you are going to argue the point (viz: "compromised" and "vulnerable" are synonyms without distinction), why don't you explain what it means to "decimate" something, and how too many people seem to use the word incorrectly.

    2. Re:Pedantic Man to the rescue! by TsuruchiBrian · · Score: 2

      OK so if you are using "compromise" to mean "Every SSL session in the past 2 years was potentially vulnerable to danger", then I guess that's true in the sense that almost every computer is compromised since there are probably many unnoticed security holes in just about every OS and commonly used library.

    3. Re:Pedantic Man to the rescue! by iluvcapra · · Score: 1

      there are probably many unnoticed security holes in just about every OS and commonly used library

      Yeah that's the distinction. The point is that we noticed, and this *single* security hole has an enormous reach.

      --
      Don't blame me, I voted for Baltar.
    4. Re:Pedantic Man to the rescue! by TsuruchiBrian · · Score: 1

      Is your point that it's good that this hole was noticed or bad that it was noticed?

    5. Re:Pedantic Man to the rescue! by iluvcapra · · Score: 1

      My point is that we cannot say something is (or has been) compromised unless we have concrete evidence of the compromise in hand. We can't just say, in the abstract, "everything's compromised" simply on the basis of the assumption that all software is fatally flawed.

      --
      Don't blame me, I voted for Baltar.
    6. Re:Pedantic Man to the rescue! by lorinc · · Score: 1

      " just about every SSL-encrypted internet communication over the last two years has been compromised."

      No, it really hasn't.

      It's accurate to say that just about every Open-SSL encrypted session for servers that were using NEW versions of OpenSSL (not all those ones out there still stuck on 0.9.8(whatever) that never had the bug) were potentially vulnerable to attack.

      That's bad, but it's a universe away from "every SSL session is compromized!!!" because that's not really true.

      They were vulnerable to attack, that is to say, the security was compromised. He didn't say they were hacked, stolen, eavesdropped, or surreptitiously recorded.

      No, not if they didn't enabled the compromised feature.

    7. Re:Pedantic Man to the rescue! by swillden · · Score: 1

      You missed his point completely. The point was that many production systems weren't running the new version. Of the 2/3 of web servers that use OpenSSL, it's likely that only half were running a newer OpenSSL. So it's not "every SSL session was (potentially) compromised", it's "about a third of SSL sessions were (potentially) compromised".

      That's bad. Really, really bad. But it's not as bad as if OpenSSL really were a monoculture.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    8. Re:Pedantic Man to the rescue! by TsuruchiBrian · · Score: 1

      My point is that we cannot say something is (or has been) compromised unless we have concrete evidence of the compromise in hand. We can't just say, in the abstract, "everything's compromised" simply on the basis of the assumption that all software is fatally flawed.

      I certainly don't think so either, but I don't use the definition of "compromised" that almitydave suggested.

    9. Re:Pedantic Man to the rescue! by almitydave · · Score: 1

      You missed his point completely.

      No, I was replying specifically to the compromised/vulnerable confusion regarding affected versions of OpenSSL, not to the clearly hyperbolic and incorrect statement that indicated that all SSL-based communications were vulnerable.

      It's "Pedantic Man", not "Basic Fact-checker Man". Different line of work.

      --
      my, your, his/her/its, our, your, their
      I'm, you're, he's/she's/it's, we're, you're, they're
    10. Re:Pedantic Man to the rescue! by Anonymous Coward · · Score: 0

      "Compromise" has 2 meanings
      (A) to reach a mutually accepted position by negotiation
      (B) to put in a bad situation

  61. It means we need to verify development methods. by VortexCortex · · Score: 0

    It means we need to raise the bar for contributors and maintainers. If they are not using 100% code coverage fuzz testing in their unit tests (the bare minimum a security researcher will use against a product to detect exploitable code) then they don't need to be a maintainer. End of discussion. Period. You either maintain unit tests with at least range checking (which you can automatically generate if your doc comments aren't stupid) and fuzz tests for the same unit tests (which can be generated from the unit tests) for every damn line of your code, or you need to STOP. Period. No one else should be running your fucking piece of shit untested code. If you CAN'T do this basic fucking step of code coverage, unit tests for edge cases and fuzz testing then you should not be releasing open source software. Period. If you're not doing this and you're the maintainer of a security related product? Well, then you should hang yourself as soon as possible, because you are a worthless despicable piece of shit. Period.

    And, if you are an arm-chair apologist who thinks I'm being too harsh in my insistence maintainers and developers follow basic security precautions or not work on open source, because you don't give a flying fuck about security: Fuck you too, You're part of the problem. Go jump in a tar-pit because you're hindering the herd.

    Bottom line: People who don't give a flying fuck about security shouldn't be producing software. You shouldn't let such people maintain FLOSS projects. You get the fucking security you pay for. Yes it's free, but I'm talking development costs. Since NONE OF YOU FUCKERS actually cares about security YOU DO NOT HAVE ANY.

    Either SHUT THE FUCK UP, or USE THE DAMN TOOLS WE GAVE YOU AND DEMAND THE OTHER IDIOTS DO TO.

    "Wah, we don't fucking care about security! Why don't we have any security?!" Blow it out your ass, morons. This is why I develop my own hobby OSs and compilers. Because you really can't trust ANYONE to do it right in this day and age. Your moronic double standards are your own damn fault. You don't want to pay the time in development costs to test your software properly, but you want it to be secure. Something has to give, idiots! All the pundits sound like a bunch of imbeciles. Fact: The were NOT using the available memory checking, code coverage and input fuzzing tools. OF COURSE IT'S NOT SECURE!

  62. Re:Open source was never safer by Anonymous Coward · · Score: 0

    Yeah, because closed source companies like Microsoft never copy code between versions of Windows, so simple vulnerabilities in things like Windows Metafiles would never affect the security of the entire userbase of Windows 3.0, 3.1, 3.11, NT 4, 2000, ME and XP at the same time. Who knows what other closed source vulnerabilities are lurking out there?

  63. "Many eyes" discovered quickly, didn't disclose by drdrgivemethenews · · Score: 1

    Data point: the NSA reportedly discovered this bug within days of its placement, and didn't disclose it.

    When the bad guys have a lot more eyes than the good guys, it skews the math.

    1. Re:"Many eyes" discovered quickly, didn't disclose by nomanisanisland · · Score: 1

      Data point: the NSA reportedly discovered this bug within days of its placement, and didn't disclose it.

      And a source for that "data point" would be...?

  64. Closed source won here by Ted+Stoner · · Score: 1

    I've read the FOSS argument for years and I guess I have leaned in favor of it from a bug perspective. But in this case, I think closed source would have won, at least to the current point in time. If OpenSSL is truly behind 60-75% of the world's web servers, then the value in hacking it is enormous. Thus if I am a criminal organization, it might be worth spending $1M for guys to read that open source code and find problems that I can then monetize for a big profit.

    I don't think you are going to get $1M worth of code inspection on the white hat side for OpenSSL. Maybe going forward it will, and companies may be willing to invest in the upkeep. Not out of goodness, but because it makes good business sense. For a large organization, how many soft and hard dollars have been chewed up in the last week doing analysis, patching, client communication and general PR for Heartbleed? Probably enough that a $10K donation in time or money to OpenSSL upkeep would be feasible.

    There is also evidence that the bad guys have been exploiting this in the wild. So the usual argument of "we found the bug quicker with open source" is probably wrong here. The better-funded and more highly motivated bad guys found it quickest.

    My guess is the bad guys have been working this bug against Yahoo for awhile. Yahoo told me a couple of months ago (and others I know) that someone was attempting to login to my account from Russia. I would now suspect Heartbleed here.

    The logic for finding bugs on the black hat side is OR (find any bug and exploit). The logic on the white hat side is AND (prevent all bugs). The table is always tilted like this unfortunately in the security arena. Bugs will always happen and the good guys can't win every time, regardless of code access.

    1. Re:Closed source won here by Eric+Smith · · Score: 1

      Would you argue that if a Microsoft (or other vendor) SSL implementation was used by most of the world's web servers, this would have been less likely to happen? As far as I know, there's no reason to think that any other implementation, open or closed, would be any more immune to such problems. There is little or no evidence that closed source software is generally more reliable, or that substantial effort is made to audit it.

      If you're arguing that it's bad that such a high percentage of the world's web servers use the same software, I might agree, but that is completely orthogonal to whether that software is open or closed.

    2. Re:Closed source won here by Ted+Stoner · · Score: 1

      I would say that open source bugs are easier to exploit because you have the source. Closed source bugs rely on reverse engineering and should in theory be harder to find. So yes bad guys can focus on a high-value product or target whether closed or open source, but I think their job is a lot easier if it is open source.

      To reiterate my point, I think that this argument is applicable to high value targets mostly. For non-security code or that without strong monetary implications tied to it, open source should still be better than closed source from a bug perspective.

  65. Heartbleed disclosure timeline .. by DTentilhao · · Score: 1

    "Ever since the "Heartbleed" flaw in encryption protocol OpenSSL was made public on April 7 in the US there have been various questions about who knew what and when."

    Company | Codenomicon: "Howard A. Schmidt, Chairman of the Board .. His private-sector experience includes serving as Vice President, Chief Information Security Officer and Chief Security Strategist at eBay and as Chief Security Officer for Microsoft ."

  66. Honestly, the "OSS is safe" discussion is over. by Anonymous Coward · · Score: 0

    One of the critical parameters that is studied in the art of defect analysis and prevention is "scope of loss."

    The scope of loss of the heartbleed bug is huge. Not only is the scope huge, but it is completely unknown what was lost in the two years that the bug was in the wild before it was discovered.

    In general, this situation demonstrated the complete lack of review, effort, and professionalism that goes into open-source. Really, it has proved to be simply a hobby, and hobby code simply doesn't cut it.

    Without professional, thorough engineering review and analysis (not even millions of people "just playing around in linux"), no software can be considered safe. Open source software is generally woefully underfunded in this respect, and since it can't possibly be tested with any degree of confidence, it is only appropriate for anyone who cares to ditch it immediately, until such time as there are thorough processes in place to guarantee good code.

    1. Re:Honestly, the "OSS is safe" discussion is over. by Eric+Smith · · Score: 1

      That OpenSSL is open source is irrelevant. This bug could just as easily have happened in closed source software. Using closed source software does not give any higher confidence in the quality of the code; many studies (e.g., 2012 Coverity Scan Open Source Report) show generally comparable code quality, with some open source projects scoring substantially better than average.

    2. Re:Honestly, the "OSS is safe" discussion is over. by Anonymous Coward · · Score: 0

      Your examples are flawed. Many people are paid to work on Linux. There is a huge commercial interest in the operating system. It started as a hobby OS but today it's a commercial success in addition to hobbyists submitting code.

      OpenSSL has a healthy contribution and there is a full time developer working on it.

      Your example might apply to my project where I'm practically the only person working on it these days and it is a hobby. Any project of the scope of Linux is going to get a lot of good developers reviewing pieces of it as they add new functionality to it. I'm a BSD guy, but I can assure you that there are talented guys working on Linux. There is some ego and some other things there too but that's true in many open source communities including *BSD.

      Apple had a recent bug in their SSL implementation. They're a professional organization with good developers and they had a simple typo that was quite bad.

      Let me let you in on a little secret, no software can be secure or bug free. Even if you prove the algorithm is correct, have it peer reviewed and run it through static analyzers, things can be missed, bugs can be in dependent libraries, or even a security flag or bug in the compiler used to run it. Heck, you're even assuming the hardware is safe.

  67. It's not a discussion... by moronikos · · Score: 2

    It's a statement. It's a statement by a dogmatist on one side, and there will be statements by dogmatists on the other side. Two dogmatists don't have discussions--they just try to shout one another down.

    Yeah, if you get enough eyeballs on a problem, sure it might be easier to solve. But users != eyeballs. I suppose being open source, it is easier to get eyeballs on something, but it is also easier for the black hats to get eyeballs on something as well and exploit it.

    In the end, neither side in the dogmatic divide is likely to listen let alone switch sides.

  68. Re:This was positive by Anonymous Coward · · Score: 0

    Do you have a source for your claim that heartbleed was found by code review? As far as I knew, it was found by researchers at Codenomicon who were trying to test their software by trying to act as attackers. The fact that the bug slipped through code review exposes one of the major issue with open source software, that there are lots of developers working on code but little to no organized QA beyond code review.

  69. Given the number of Windows exploits... by iamacat · · Score: 1

    I would take my chances with FOSS. How crazy is the statement that XP can not be safely used without Microsoft support, given that they had 13 years to fix bugs in a feature-frozen release? In an open source release used for so long and on the same scale, chances of finding a new catastrophic bug would be slim. For example, Heartbleed was found in 3 years. Likewise goto fail bug in Apple open source was discovered in a relatively short time.

    Not to mention that if new bugs were found in desupported but still somewhat popular open source software, users would create their own fix in no time rather than having to pay millions to Microsoft.

  70. safe languages by Eric+Smith · · Score: 1

    Heartbleed is a perfect example of why software should be written in "safe" languages, which can protect against buffer overruns, rather than unsafe languages like C and C++.

    Of course, the problem is that if you try to distribute open source software written in a safe language, everyone bitches and whines about how they don't have a compiler for that language, and how run time checking slows the software down by 10%. Personally I'd rather have more reliable software that ran 10% slower, than less reliable software that ran faster. It's also crazy to turn off the run-time checks "after the software is debugged", as if the debugging process ever succeeded in finding all the bugs. As C.A.R. Hoare famously observed in 1973, "What would we think of a sailing enthusiast who wears his lifejacket when training on dry land, but takes it off as soon as he goes to sea?"

    The "with enough eyes" argument, and "if programmers were just more careful" arguments don't justify continued widespread use of unsafe languages. Granted, safe languages don't eliminate all bugs, but they eliminate or negate the exploit value of huge classes of bugs that are not just theoretical, but are being exploited all the time.

    I keep hoping that after enough vulnerabilities based on buffer overruns, bad pointer arithmetic, etc. are reported, and cost people real money, that things will change, but if Heartbleed doesn't make a good enough case for that, I despair of it ever happening.

  71. It makes it even safer by FuzzNugget · · Score: 1

    Without the ability for anyone, not just a limited subset of employees, to access and modify the source code, the bug may have never been found. At best, it would have been found later and taken longer to fix.

  72. Zontar, why're you "running" forrest? by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    ---

    You avoided backing up your accusation where YOU said I say you are Barbara, not Barbie = TomHudson (same person http://tech.slashdot.org/comme... , & sockpuppeteer like you) -> http://slashdot.org/comments.p...

    Funny you can't back up your "bluster" there either, lol...

    ---

    Why, Lastly?

    You're crackers! See here multiple personality disorder http://slashdot.org/comments.p... + manic depression http://slashdot.org/comments.p...

    APK

    P.S.=> So, THIS quote below is my policy on sockpuppeteers like you Zontar = TrollingForHostsFiles (your sockpuppetry):

    "The only way to a achieve peace, is thru the ELIMINATION of those who would perpetuate war (sockpuppet masters like YOU, troll -> http://slashdot.org/comments.p... ). THIS IS MY PROGRAMMING -> http://start64.com/index.php?o... & soon, I will be UNSTOPPABLE..." - Ultron 6 FROM -> http://www.youtube.com/watch?v...

    Which quite obviously, I am, since none of you DOLTISH TROLLS are able to validly technically disprove my points on hosts enumerated in the link to my program above of how hosts give users of them more speed, security, reliability, & anonymity... period!

    (Trolls like YOU that use sockpuppets http://slashdot.org/comments.p... (your sockpuppet "alterego" TrollingForHostsFiles) & TomHudson - Barbara, not Barbie too http://tech.slashdot.org/comme... before you)

    ... apk

    1. Re:Zontar, why're you "running" forrest? by Anonymous Coward · · Score: 0

      Thx for helping Zontar rank up. The karma + replies helps his score.

    2. Re:Zontar, why're you "running" forrest? by OneAhead · · Score: 1

      Ahh a rare specimen of a mentally ill person on /.

    3. Re:Zontar, why're you "running" forrest? by Anonymous Coward · · Score: 0

      We see others opinions of you too asshole http://slashdot.org/comments.p...

    4. Re:Zontar, why're you "running" forrest? by Anonymous Coward · · Score: 0

      We see other trolls posted against perceptive Slashdotters like you http://slashdot.org/comments.p...

      (Correcting APK's numerous typos.)

  73. Re:Zontar eats his words vs. apk AGAIN? by Anonymous Coward · · Score: 0

    Nobody clicks on THE links. Nobody READS your comments. Everybody CAN see you need proFESSional help.

  74. Re:w/o disclosure, exploiting closed source tempti by qzzpjs · · Score: 1

    You forget that this just happened to Apple a couple months ago in their SSL implementation. The misplaced goto statement caused them to ignore all certificate chain checking. Apple was quite fast in notifying people and working on a fix for it.

  75. It doesn't. by nashv · · Score: 4, Insightful

    1. Proprietary software could have a million bugs like this. You just wouldn't know it. They do not become less dangerous because they are proprietary, nor do security flaws become more dangerous because they are in open-source code.
    2. Open-source software at least has the possibility of being looked at over and over. Proprietary code may be reviewed or not depending on the resources, interest, and monetization capability of that code. A possible review by all relevant coders in the world is always more review than by a limited team of programmers and analysts at one company.
    3. The real problem with Heartbleed is the time that passed between code being written and a bug being discovered. That delay exacerbates the security problem. However, there will be some sort of statistical (probably Poissonian or normal) distribution of the time required to catch a bug since introduction into code. As with anything, there are outliers. Heartbleed with its serious and longstanding flaw must be considered an outlier unless shown otherwise. I have not seen evidence that this happens on a regular basis with any software, FOSS or otherwise.

    I would appreciate it if future Slashdot discussions were let out through the upper orifice with some maturation period in the brain, rather than through the lower orifice after festering in the colon.

    --
    Entia non sunt multiplicanda praeter necessitatem.
  76. Re:This was positive by Anonymous Coward · · Score: 0

    "and no one is seriously interested in forking it or doing a new implementation."
    I'll be removing oppenssl from every macine i touch and recommending the same to everyone. There are demonstrably better alternatives available. (some at a cost).
    Any sysadmin who wants to back openssl with HIS job and declare that is the best he can do for his business and his customers is welcome too. I will simply provide better alternatives to CHEAP and LAZY wannabees.
    You can't be cheap, lazy and stupid at the same time. there is a rule against that.
    I'm not saying I'm smarter than you because of some stupid bug by some stupid programmer who thought he knew C. I am just saying I'm smarter than you.
    OpenSSL's well is poisoned just like indian rivers. Because the people who are supposed to take care of it keep shitting in it. But IT IS FREE!
    eat your shit. Go ahead

  77. Re:Zontar "eat your words" libelous troll by Anonymous Coward · · Score: 0

    Look! It's the wannabe 'developer'. It has no skills, so it adds some crap to a text file and declares itself a 'programmer'. Your "host file" solution doesn't work, it is spam and it offers *NO* protection, you dribbling idiot. Too bad when they turkey-basted your mom, they didn't shove it in her ass instead. Or did they...

  78. Re:That's kind of curious by Johnny+Loves+Linux · · Score: 1

    I've heard other people say this too, but I don't see how that can be. Are there any stats that convincingly prove this? It seems to me that proprietary companies have some advantages when it comes to marketing. They can always sue people who claim they have found an exploit in the software. And there is no law obligating a proprietary company to announce when someone has found an exploit in their proprietary software and informed the company about it. So I would take claims that Microsoft has a "better" security record with a mountain of salt. Who is Microsoft being compared to? SCO? What is the metric? Where is the data?

  79. eyeballs that aren't paying attention by Anonymous Coward · · Score: 0

    If an eyeball isn't looking for a security bug then an eyeball won't see a security bug.

  80. At what price freedom? by angularbanjo · · Score: 1

    But security and safety are not free, as peoples around the world are already familiar with. Free software in itself, as in the past few days has been laid out to dry by every VC-backed non-open idea factory in the US, is not the reason why you now need to change your passwords. The reasons should be self-evident.

  81. It confirms that open source is safer. by Kremmy · · Score: 2

    It has done so by making the issue public and allowing it to be given proper consideration, as opposed to being covered up by those in the know while people continue exploiting it. This is a significant step forward in the open source discussion because this is open source working as it should, the bug was found because there were many eyes in the general area. Open Source versus Closed Source is becoming the difference between systems you can vouch for and systems you can't.
    In a closed source world we would have everybody vulnerable without anyone knowing about it. That only helps if you're one of the people abusing it, because nobody is taking precautions against it. Now we are actually able to respond to a real threat that we can explore deeply. Sorry, closed source is not going to give me confidence.

  82. Why is Raymond's claim theoretically sound? by Anonymous+Brave+Guy · · Score: 5, Interesting

    Raymond's proposition is theoretically sound

    No, it isn't. It's nonsense and it always has been.

    There is plenty of evidence for the effectiveness of good code reviews, but most of it shows rapidly diminishing returns with the number of reviewers. You get much of the benefit from having even one or two additional people read over something. By the time you've had more than four or five people take a look, the difference in effectiveness from adding more barely even registers, unless one of the additional reviewers has some sort of unique perspective or expertise that makes them not like the others.

    Given that almost every major FOSS system software project has had its share of security bugs, there is really very little evidence to support Raymond's claim at all. It's not like it has ever been taken seriously outside the FOSS fan club, but there are a lot of FOSS fans on Slashdot, and so plenty of comments (and positive moderations) reinforce the groupthink as though it's some inherent truth.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Why is Raymond's claim theoretically sound? by TsuruchiBrian · · Score: 5, Insightful

      There is plenty of evidence for the effectiveness of good code reviews, but most of it shows rapidly diminishing returns with the number of reviewers.

      To me this is an argument *for* open source software. It *takes* LOTS of eyes to catch bugs, *because* there is diminishing returns by adding more code reviewers. It is only by having hundred or thousands of them that you can hope to catch those ones that would otherwise go unnoticed.

      By the time you've had more than four or five people take a look, the difference in effectiveness from adding more barely even registers, unless one of the additional reviewers has some sort of unique perspective or expertise that makes them not like the others.

      And one easy way to have a diverse group of code reviewers is to have a lot of them.

      Given that almost every major FOSS system software project has had its share of security bugs, there is really very little evidence to support Raymond's claim at all.

      Every piece of software of any reasonable size has security bugs. The fact that we know about them is because someone found them, which is exactly what is supposed to happen.

    2. Re:Why is Raymond's claim theoretically sound? by Anonymous+Brave+Guy · · Score: 0

      It is only by having hundred or thousands of them that you can hope to catch those ones that would otherwise go unnoticed.

      But how many FOSS projects really have diligent review of all their code by anything like that many people? For many projects, getting a change accepted requires only the approval of one or two others. Activities like the current detailed review of TrueCrypt are the exception, not the rule.

      If you really want a dramatic improvement in catching these kinds of bugs and you've already got a respectable code review process in place, you'd probably do better by considering complementary strategies instead of pursuing ever diminishing returns from throwing more people into the same informal code review process. Choose safer programming languages that don't admit certain kinds of programmer error in the first place. Employ formal methods to make sure the underlying algorithms are sound. Adopt different testing strategies.

      Sadly, using safer programming languages is still swimming against the flow of mainstream programming tools, while using formal methods or many testing strategies outside of having an automated unit test suite sounds like heavyweight design to some people, and this upsets all the newbies who think being "agile" and "moving fast and breaking things" are the way you make good software when quality really matters.

      Improving software quality is in significant part a social problem, but the solution is not requiring more people to be reviewers, it's getting more people to understand that just having more reviewers is not enough.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    3. Re:Why is Raymond's claim theoretically sound? by TsuruchiBrian · · Score: 2

      But how many FOSS projects really have diligent review of all their code by anything like that many people? For many projects, getting a change accepted requires only the approval of one or two others. Activities like the current detailed review of TrueCrypt are the exception, not the rule.

      A lot of the bugs are caught well after the code is accepted. People sometimes just randomly spot things. The probability is low, but over enough time and with enough eyeballs, you catch bugs this way.

      I was trying to hunt down a bug in my own code and ended up catching a bug in motif once. This was only possible because the source was open. I don't think this is such a rare occurrence. Even if 1 in 10 programmers spots 1 bug in open source software in their life, that's like hundreds of thousands if not millions of bugs being found, that otherwise wouldn't have been.

      If you really want a dramatic improvement in catching these kinds of bugs and you've already got a respectable code review process in place, you'd probably do better by considering complementary strategies instead of pursuing ever diminishing returns from throwing more people into the same informal code review process

      We definitely should be throwing people at the open source code. But having code be open, isn't throwing anybody at the code. It is just making it available to people who already want to look at it.

      Choose safer programming languages that don't admit certain kinds of programmer error in the first place. Employ formal methods to make sure the underlying algorithms are sound. Adopt different testing strategies.

      Yeah all that stuff. No one is saying that open source is the *only* way to find bugs.

    4. Re:Why is Raymond's claim theoretically sound? by amiga3D · · Score: 1

      I fully believe if the software in question had been proprietary then the bug would have gone unreported longer and we'd still be looking for a patch 3 years from now. This is generally how things are done in the proprietary world. In fact if anyone had shown proof of the bug with an exploit they'd likely have been sued or prosecuted.

    5. Re:Why is Raymond's claim theoretically sound? by brantondaveperson · · Score: 1

      Choose safer programming languages that don't admit certain kinds of programmer error in the first place.

      This. Have you seen the code that the heart bleed bug lay within? This love affair with bare-metal C, with hand-managing memory, etc etc - needs a really hard re-examination. Calling memcpy in a security-critical application? Seriously?

    6. Re:Why is Raymond's claim theoretically sound? by BlackHawk-666 · · Score: 1

      The problem is not with calling memcpy, it's calling it without sanitising or knowing the extents to which it needs to be bound.

      --
      All those moments will be lost in time, like tears in rain.
    7. Re:Why is Raymond's claim theoretically sound? by brantondaveperson · · Score: 1

      Well maybe. I'd argue the problem is the extent to which C allows you to shoot yourself in the foot, and therefore its suitability in security-critical environments like openSSL.

    8. Re:Why is Raymond's claim theoretically sound? by Barsteward · · Score: 1

      "Raymond's proposition is theoretically sound No, it isn't. It's nonsense and it always has been."

      it would be nonsense if Raymond said there are no bugs but he didn't. Maybe comprehension is required, "bugs are shallow" means there will be a few bugs.

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    9. Re:Why is Raymond's claim theoretically sound? by SkunkPussy · · Score: 2

      You should consider avoiding pretty much any OS kernel then for the same reasons!

      --
      SURELY NOT!!!!!
    10. Re:Why is Raymond's claim theoretically sound? by Anonymous+Brave+Guy · · Score: 1

      Please read what Raymond actually wrote in The Cathedral and the Bazaar. My criticism applies equally to his more formal definition of Linus's Law, and to his extended argument as a whole.

      No-one (sensible) claims that any code review process will find absolutely all bugs. But Raymond's article seems to be arguing that having enough developers and testers on a project will inevitably get you very close.

      And yet, we are talking about this in a discussion about a severe bug in one of the most widely used OSS projects on the planet that went undiscovered (or at least unreported and unfixed) for years.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    11. Re:Why is Raymond's claim theoretically sound? by SQLGuru · · Score: 1

      And a million monkeys will eventually type out the complete works of Shakespeare

      Open source is no more (or less) perfect that closed source at a fundamental level. Bugs are introduced in both. The difference is that once found, open source has more eyes looking to try to fix it.

    12. Re:Why is Raymond's claim theoretically sound? by TsuruchiBrian · · Score: 1

      And a million monkeys will eventually type out the complete works of Shakespeare

      If you had enough monkeys (or more suitably random typers), enough time, and enough energy, you would eventually get the complete works of Shakespeare.

      As Dan Dennett said about philosopher's syndrome:

      mistaking a failure of imagination for an insight into necessity.

      Open source is no more (or less) perfect that closed source at a fundamental level. Bugs are introduced in both. The difference is that once found, open source has more eyes looking to try to fix it.

      If that was the only benefit, then open source would be pretty useless. Once you find a bug, fixing it is usually pretty trivial. Heartbleed for example was just a simple buffer overflow and pretty much everyone came up with the same immediate solution.

    13. Re:Why is Raymond's claim theoretically sound? by BasilBrush · · Score: 1

      That's the point. It's not rational to write security applications with languages or libraries that rely on a programmer checking bounds and overlap before doing a copy operation. A copy function in a rational security language / library would do these checks itself. That way they are always done and they are always done correctly.

    14. Re:Why is Raymond's claim theoretically sound? by BasilBrush · · Score: 1

      Let's not forget that Heartbleed wouldn't have been a problem on OpenBSD, had they used the built in malloc. Whilst system programming in C is still unaccountably common, not all kernels are as insecure as others. And libraries can still be insecure no matter what the kernel does.

    15. Re:Why is Raymond's claim theoretically sound? by BasilBrush · · Score: 1

      I fully believe if the software in question had been proprietary then the bug would have gone unreported longer and we'd still be looking for a patch 3 years from now.

      Then you have religion. The number of contrary examples are myriad. Your blind belief can't change the fact that, for example, the recent much publicised iOS SSL bug was discovered by Apple, reported by them to the public CVE, and fixed all within 1 year and 4 months of it first appearing in code.

      And for comparison the very similar bug in GnuTLS laid undiscovered for 8 years, and was only discovered in the bow-wave of the discovery of the Apple SSL bug, which finally prompted someone to code review the equivalent GnuTLS code.

    16. Re:Why is Raymond's claim theoretically sound? by TsuruchiBrian · · Score: 1

      The problem isn't even with C. Sometimes it's nice to be able to shoot between your toes. We use C++ at my company but we only use frameworks and data structures that do proper bounds checking (e.g. Qt). We don't really ever do raw memcpy. We use QByteArray methods. This doesn't mean memcpy is bad. QbyteArray is surely using memcpy or something exactly like it under the hood.

      I personally like the versatility of C++. You can do memcpy if you really need the speed for some reason, or you can build something safer on top of memcpy and use that.

    17. Re:Why is Raymond's claim theoretically sound? by Rakarra · · Score: 1

      Maybe comprehension is required, "bugs are shallow" means there will be a few bugs.

      Raymond's proposition is that bugs will be easily or quickly found with lots of people looking at the code. That does not seem to be borne by reality.

  83. Oh grow up! by Anonymous Coward · · Score: 1

    There are no reliable metrics that indicate FOSS is safer. None. FOSS is an ideology to many and that means that it is beyond reproach. The hailstorm of excuses that surrounded the fiasco of the Gnome/KDE 3 rollout is a case in point.

    A big company that you hate does this and we have to hear about it for the next 20 years. FOSS does it and "oh it's open source so it's kinda OK, you know?"

    Get off the smug position you hold and enter the real world. Heartbleed costs the FOSS world reputational damage and the best you can do is "maybe it would have never been officially recognized"?? So how then, do the bugs get recognized and patches developed for MS Patch Tuesday? Do angels whisper into the ears of MS executives?

    I don't expect any of this to make an impact on you though. As I said going in, it's ideology you hold.

    1. Re:Oh grow up! by dbIII · · Score: 1

      enter the real world

      An air-conditioned office? Funny how that's what is mostly what people shouting "real world" mean.
      If you want to challenge the experience of others then provide your own "metrics" or anecdotes from your own experience.

  84. A shallow bug can still go unnoticed. by jcr · · Score: 1

    ESR's statement remains true.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  85. Ok, ok, I bite by Opportunist · · Score: 2

    After a lot of soul searching whether or not I should actually honor this obvious attempt at trolling with a comment, I think I should, lest someone actually take it serious and believe it.

    Allow me to take you on an excursion into the world of security. Before you get your hopes up, it's not as glamorous or kinda-sorta-shady-sinister-blackhat as you might think. But I'll try to make it as interesting as it can be.

    Part of security are audits. Audits are, in a nutshell, attempts to find out whether there are weaknesses in the surface you're auditing. For example, you prod at a server, check its ports, make sure that everything that answers does so in a way that cannot be exploited, and so on.

    Those that at least dabbled in security will know about the various "boxes" used to describe the "rules of engagement" in such an audit. Most commonly known, I'd guess, are "black" and "white" box tests. In a "black box" test, you get no or very little information about your target and your task is to find out whatever you can find about it. A "white box" test is the exact opposite, where you get full disclosure of your target's makeup, e.g. what services are running, at what patch level, often even what purpose they serve and what department they belong to, and so on.

    One might now think that the more "normal", more "useful" test is a black box test. Because, hey, if I tell you everything, what the hell would you test? But, know what? A black box tests is something that you'd do to test the tester's ability, not that of your target. With a black box test you can rather find out just how much the guy you hired to do your audit actually knows about the whole shit.

    If you actually want to test the target, you disclose about any information there is. That might sound odd now, but when you think about it, it starts to make a lot of sense. This information can be available to a potential attacker. A disgruntled ex-employee could have that information. Or someone who spends a lot of time social engineering and prodding can gain it somehow. Assuming that you could increase your security by withholding information from a potential attacker is at best giving you a false sense of security because you can NEVER actually say with at least a semblance of certainty that a potential attacker CAN NOT have that information. Like I said before, all it takes is a pissed off ex admin and this attacker would have ALL the information.

    And it's rather trivial to sell information these days...

    Now, what does this have to do with the question open vs. closed source?

    It means that just because YOU do not have the information does not mean that your attacker does not have it. Closed source is akin to the black box in the aforementioned example, open source the white box. When you audit closed source, you will learn more about the abilities of your auditor rather than about the security level of the software you audit.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  86. Re:Open source was never safer by aynoknman · · Score: 3, Funny

    2003 called, they want your Microsoft back.

    If only we could.

    --
    We need a "+1 -- nice sig" moderation.
  87. You clicked on it stupid (lol) by Anonymous Coward · · Score: 0

    Then again you ARE a nobody Zontar (lol). Reading? How about WRITING instead (lol) -> http://slashdot.org/comments.p...

    Now since you CLAIM to allegedly a writer by trade? How come "lil' ole' me" had to SCHOOL you in it. hmmm???

    Imagine that!

    Did your spellchecker & grammar assist features break down in your word processor (that guys like me wrote, that YOU ONLY MERELY "write about" no less) & that you are apparently helpless without and have the balls to even SPEAK to us? Please... lmao!

    APK

    P.S.=> Keep never failing to FAIL, Zontar... I love it! apk

    1. Re:You clicked on it stupid (lol) by Anonymous Coward · · Score: 0

      I didn't read your POST. You must KNOW, deep down, that you need help. Seek it. Urgently.

    2. Re:You clicked on it stupid (lol) by Zontar+The+Mindless · · Score: 1

      Your demonstrated chronic inability to appreciate any kind of humour whatsoever has absolutely no bearing on my qualifications or credentials as a writer. (And just because I don't normally bold every other word that I post does not mean that I don't know how to use bold tags.)

      BTW, if you look far enough back in my posting history, you'll see where I responded to comments about a book that I co-authored, and that was reviewed right here on Slashdot. This would have been late 2004 or early 2005, IIRC. I'm happy to wait while you go find the review and comments. I'm sure with your mighty sleuthing skills (*eyeroll*) it won't take you long.

      --
      Il n'y a pas de Planet B.
  88. Re:Security is hard. Encryption is even harder. by styrotech · · Score: 1

    All this episode does is to remind us that security is hard. Encryption is even harder.

    In general maybe. This issue had nothing to do with encryption though (or hard security stuff even).

    It was a very basic input checking error in a massively crusty overly obfuscated and badly written/documented codebase that all kinds of people have been tacking 'kitchen sink' style features onto for years. It's almost as if the codebase is actively trying to counteract the 'many eyes' effect.

    OpenBSD has already taken on their fork and started stripping out cruft - who knows that fork could end up having a portable version that everyone else starts using (like with OpenSSH).

    Companies like Google and RedHat etc are presumably going to be putting some extra resources into OpenSSL to help clean it up. It's importance means they would be crazy not to. Hopefully they also put some resources into funding/helping the OpenBSD fork too as a better longer term option.

  89. You're more than welcome... by Anonymous Coward · · Score: 0

    "Your "host file" solution doesn't work, it is spam and it offers *NO* protection, you dribbling idiot.} - by Anonymous Coward on Tuesday April 15, 2014 @07:04PM (#46762109)

    To validly technically disprove any of 17 enumerated points here http://start64.com/index.php?o... and prove me, wrong, on where & how I state custom hosts files give users of them more added SPEED, more added SECURITY, more added RELIABLITY, & even more ANONYMITY (to an extent on the latter only).

    ---

    * :)

    (Go for it - I will merely tear you apart Zontar, as you troll me by ac posts now...)

    Gotta admit, this is my favorite part of doing libelous lying little trolls like Zontar in, with facts & a challenge, with their bs.quoted above.

    APK

    P.S.=>It's YOUR reputation Zontar, Mr. Writer (not) - mine's safe & all the moreso when you "run, forrest: run!!!" here or spout totally invalid bs or more trolling... lol.!

    ... apk

    1. Re:You're more than welcome... by Anonymous Coward · · Score: 0

      Your hosts file solution is useless. You still don't know what the word libel means, either. You have not provided a single fact in any of your rants, but others, on numerous occasions, pointed out a significant number of flaws in your 'code'. Start64 is probably one of them malware-infested shareware sites - won't click on the link. Let's see, you must be around 45, still living with your mommy, haven't finished any significant education and suffer from more than one confirmed mental condition. Since you can't write software that anyone would pay for, I'm also going to guess that you collect some sort of disability income and that your mommy pays for your internet. We need to talk to her about that. Too bad you weren't just aborted...

  90. Re:That's kind of curious by styrotech · · Score: 3, Interesting

    I think the grandparent was right. MS now is hugely better than the MS of 10-15 years ago. I'm not going to try and objectively prove that as I don't care enough about MS and probably couldn't anyway.

    But the NT4 to XP/2003 era was appalling security wise - but they changed that. IIS went from swiss cheese to one of the tougher web servers to break. You just don't hear any more about the kinds of problems they used to have. If you endured those days or just laughed from the sidelines, you don't need any hard data to see that they have improved a lot.

    I found this paper from Theo de Raadt illuminating though. He steps through 10+ years of OS hardening techniques OpenBSD has put in place to prevent badly written applications misbehaving. Towards the end he summarises how other platforms do this stuff - the only other platform that did it all by default was Windows (yikes!).

  91. Re:Open source was never safer by Ol+Olsoc · · Score: 2

    Closed source was always safer.

    One word for you: Microsoft. Maybe two: Adobe.

    THIS! It's funny how Microsoft has all the issues that they do, and yet when a problem shows up in anything else, the fanbois instantly ejaculate LOOK!! SEE???

    Sorry kids, Windows has a many year legacy of needing constant security updates, way too many for you to be braying about this, as proof of the bankruptcy of FOSS.We get it, But Redmond products have a lead that will never be equaled.

    --
    The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
  92. Nonsense. by Anonymous Coward · · Score: 0

    A proper hacker doesn't care if the "source" they're reading has to be disassembled first, or if they have nice source code. All they care about is whether that code is worth exploiting to get personal information or other valuables, for a large enough audience. I'd think that the track record OpenSSL has compared to closed-source security products that have been compromised attests to this. If all it took was one huge vulnerability to discredit the paradigm, then closed source would have been discredited ages ago.

  93. Re:Another Zontar "ac drool"? LOL! by Anonymous Coward · · Score: 0

    You don't have a professional career seeing as you don't know how to write code. Trolling Slashdot and getting kicked off of many tech-related sites is not a career. You're just butthurt that Zontar (and many others!) have called your "hosts file" solution a complete waste and very similar to malware. Again, look up the definition of libel, though I expect your reading level to be that of a fifth-grader...much like your 'coding' ability. You fucked your own 'career' - ever do a Google search for yourself? First, find a dirt cheap bottle of booze and some of your moms anti-psychotics. Do that Google search for yourself. Read the results. Then read them again. Yes, you don't have a career, let alone a professional one, no good standing or good reputation to protect. You see, years ago you lost any potential to have a 'career' (not that you'd pass any exam, tech or othewise). You are a classic fuckup and you did that to yourself - no one to blame but you. Or maybe your mom. See, you can't feel 'libeled', or actually be libeled since you have no professional career, reputation or good will to be harmed. Nor has anyone here lied about the fact that your shit software has been identified as malware in the past. Stupid fucking douchenozzle...

  94. More Zontar libel by ac trolling now by Anonymous Coward · · Score: 0

    For a malware site it's listing good company in many categories http://start64.com/index.php/c... alongside his program so reconsider your words. They are, as always, obviously in error (especially considering you actually link to the companies that produce them, e.g. Microsoft, right next to my app). Others include Comodo, Panda, McAfee, Kaspersky, Malwarebytes, ZoneAlarm & other good names in the industry.

    See - I can run iwth them. You can't. That's only 1 category too... there are many others it fits.

    APK

    P.S.=> Sorry to burst your DELUSIONAL bubble, but I live on my own since the 80's & have my own spot however, occasionally while travelling worldwide for work I lived TONS of spots in the world (or for play too of course) or between jobs though, to save money, I'd live with family when I was younger (as I didn't have my own place then, I rented like young folks do, had a lot of wild crazy roommates, lol, male & female), like most do, when they're younger pursuing work, to save money - a smart move) but not with my Mom (some fool thinks Jan is a woman's name, but it's also JOHN in other languages so yea, I'd pop in @ my pop's place, we get along well (good man) in those circumstances for 1 yr. total time, maybe 2 over oh, 50 yrs. now way earlier on? There ya go on that).

    Educationally I was a lettering NCAA athlete (starter 1st year attackman - which they owe me 10 points for STILL pisses me off) for a great national power AND another letter too now that I think about it, lol -> http://lemoynedolphins.com/spo...

    On PAID jobs? One of my proudest things was increasing a MS certified partner's program up to 40% more efficiency (a block level device driven caching system) & ideas for ramdisk usage up to a finalist @ MS TechEd two yrs. in a ROW in its hardest categories: SQLServer Performance Enhancement 2000-2002 iirc... got paid. Was fun. Great company, good mgt. (Mr. Eric Dickman a pleasure to work with remotely).

    That & doing MIS systems for decades too... now I run my own businesses and survive that way (got smart, no more wageslave for me - get all the bennies that way, 10x the headaches, but all the cake)... apk

    1. Re:More Zontar libel by ac trolling now by Anonymous Coward · · Score: 0

      All lies. You should try some meds for these delusions. Face it, you are a nobody and there is not a single sane company that would hire you after performing a brief Google search - you're fucked and you know it. Otherwise you wouldn't be spewing spam all over Slashdot (150 + posts today alone, I hear). The only miserable 'accomplishment' you've had is that worthless "hosts" file abomination you call software. Does anyone see the irony in some douchefuck claiming that 'software' he wrote (and uses!!) to promote anonymity on the internet is widely known by name? How's that for anonymity. Zontar wiped your ass, now go crawl back into your mommy's bed, suck your thumb and try to be a good boy tomorrow. Maybe the voices in your head saying will stop.

    2. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      (150 + posts today alone, I hear)

      For those of you playing along with us at home, it's up 212 messages this morning. Looks like 5-10 of those are from non-AC replies to my posts. Pretty sure at least 90% of the remainder are from APK.

      --
      Il n'y a pas de Planet B.
    3. Re:More Zontar libel by ac trolling now by Anonymous Coward · · Score: 0

      You run from every one. Why's that Zontar? Your libel http://slashdot.org/comments.p... of apk he is only defending himself and his work from effectively since you evade that unceasingly perhaps?

    4. Re:More Zontar libel by ac trolling now by Anonymous Coward · · Score: 0

      Your job is a writer? Right. You must be paid to post on slashdot since you waste so much time here posting it's the only writing you do. Pay well? Yea, right.I see you actually do libel others. Something stinks about you. Bad.

    5. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      Let's put it this way: If APK writes that the sky is blue, I'm going to look out my window and check it for myself before believing him.

      --
      Il n'y a pas de Planet B.
    6. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      Excuse me? Time for a reality check here. Someone appears to have the time to troll someone *200+ times* in a single day. Just who might that actually be, APK? I'm pretty sure that it's not me who's been doing that.

      You have a really bad habit of seeing yourself in the mirror and claiming the reflection is a picture of someone else.

      --
      Il n'y a pas de Planet B.
    7. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      I'll bet that I've more accrued vacation days from my job right now than you've ever actually worked in your whole useless life.

      I could go on vacation *today* and not have to go back to work until the second week of August. And get paid for every single day of that time.

      --
      Il n'y a pas de Planet B.
    8. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      BTW, absolutely none of the AC posts in this thread were posted by me. In fact, I was asleep at the time those were made, having gone to bed about 20 minutes after I made the "Uh, What?" post (~2350 Central European Time), and not getting up until about 30 minutes after the AC grandparent of this post (~0830 CET).

      --
      Il n'y a pas de Planet B.
    9. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      APK, your *only* reputation is that of a spammer, troll, crapflooder, liar, and bully.

      Itching for another trip down Memory Lane, eh? Well, then, here's what some folks at ArsTechnica thought of you ca. 2000-2001:

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=324090429

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=779092009

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=508099016

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=666096306

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=583094285

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=901092665

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=112093523

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=106095103

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=723095213

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=624098213

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=570092603

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=302095503

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=937096103

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=796095503

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=749092603

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=757093113

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=769092603

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=451098103

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=969090603

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=420096503

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=165093103

      http://episteme.arstechnica.com/6/ubb.x?q=Y&a=tpc&s=50009562&f=12009443&m=437097503

      --
      Il n'y a pas de Planet B.
    10. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      Specifically? Everything, except for the errors and mischaracterisations.

      --
      Il n'y a pas de Planet B.
    11. Re:More Zontar libel by ac trolling now by Zontar+The+Mindless · · Score: 1

      Name some of the "spots" where you've lived outside the US, and tell us a little about them.

      I'd like to compare notes.

      --
      Il n'y a pas de Planet B.
  95. Correcting small typo (addendum) by Anonymous Coward · · Score: 0

    For a malware site it's listing good company in many categories http://start64.com/index.php/c... [start64.com] alongside This program so reconsider your words

    APK

    P.S.=> HAD to do THAT (lol), why? Zontar's a writer -> http://slashdot.org/comments.p...

  96. buffer overflow by Anonymous Coward · · Score: 0

    Can someone answer a technical question? My midunderstanding is that Heartbleed is a buffer overflow, which is also what a bunch of other security bugs have been over the years. (Obviously there are other ways.) Why is there no library code that one calls to set up a buffer, have the buffer read the input, and return the result? The caller would provide a buffer size (or maybe it can be inferred from a passed variable? my C is very rusty) and a few other args, and the library code would protect against any overflow.

    Or does such code exist, but people don't use it?

  97. one-word counter-argument by swschrad · · Score: 1

    Microsoft Windows.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
  98. Partent article is flamebait by virtualXTC · · Score: 1
    Articles like this make me wish we could moderate the articles as well as the comments.

    All heart-bleed proves is that C+ is a poor language to be programming security software in.

  99. Philosophy vs Substance by JCHerbsleb · · Score: 2

    Open Source vs Closed Source is as much a philosophy as it is substance. We can argue the benefits of having many eyes on the code from Open Source as opposed to having funded coders with Closed Source. In the balance, each project will be different based upon its own unique factors. The one constant is that Open Source does have superior transparency.

  100. No, what you said is lies Zontar by Anonymous Coward · · Score: 0

    Which is why you run from, & donwmod to hide, this http://news.slashdot.org/comme...

    APK

    P.S.=> I've worked in the Fortune 100-500 pal, in positions (network admin or programmer-analyst) - have you? No... prove otherwise. Again, you're more than welcome to take 'the APK challenge' here regarding my latest freeware -> http://news.slashdot.org/comme... (which, true to troll libeling form, ZONTAR does a "Run, Forrest: RUN!!!" from, every time trolling by ac, sockpuppet, or using his registered 'luser' account here... lol!)

    ... apk

    1. Re:No, what you said is lies Zontar by Zontar+The+Mindless · · Score: 1

      You DO realise that I can't post and moderate in the same discussion, don't you? In any case...

      APK, I absolutely do not now, and I am not *ever* going to be convinced you've ever worked anywhere except maybe Burger King.

      However, I AM convinced that you are a lying, bullying, spamming, crapflooding troll.

      You make increasingly grandiose and decreasingly believable claims about yourself. Whenever you're questioned about these, your lies get even bigger. When you're called out on them, you start attacking people.

      When you make idiotic claims about programming, and get called out on those... That's right, you start attacking people.

      You also apparently think that linking to any old thing proves your lies and mischaracterisations. Like when you linked to a joke you plainly didn't understand, claiming it was proof that I have MPD. Or when you linked to ANOTHER joke of mine that you ALSO plainly did not "get", and claimed this was "proof" that I'm not a writer.

      When your attempts at intimidation and mischaracterisation don't work, you just start repeating them... well, MINDLESSLY... in an attempt to turn up the volume and drown out dissenting voices.

      You have been doing this again and again and again and again for over a decade. It's all over the WWW. I'm not even going to bother to link to anything, because anyone with one good finger and half a clue can type "Alexander Peter Kowalski" into Google and read for themselves all about your little escapades.

      --
      Il n'y a pas de Planet B.
    2. Re:No, what you said is lies Zontar by Anonymous Coward · · Score: 0

      You're caught sockpuppeting (trollingforhostsfiles) so you could do it http://slashdot.org/comments.p... so cut the crap and own up to what's been asked you provide troll http://slashdot.org/comments.p...

    3. Re:No, what you said is lies Zontar by Zontar+The+Mindless · · Score: 1

      You're apparently the only person visiting this site who can't see that the TrollingForHostFiles account was created specifically in your honour, AFTER you started trolling me and crapflooding any and all threads I posted to.

      And I've made absolutely no secret of TFHF's origins, which kind of deflates your sockpuppet conspiracy theories.

      Oddly enough, the TFHF account already has positive karma, which means somebody's been modding up its posts in spite of the fact that it's an acknowledged alter ego. And I'm extraordinarily pleased to say that I (Zontar) have not had mod points since the TFHF account was created, so those upmods are not coming from me.

      --
      Il n'y a pas de Planet B.
  101. Heartbleed is Good for Opensource by ikhider · · Score: 3, Insightful

    How can you be a good chess player if you do not lose the odd game? So the opensource code got a strike against it, I am sure GNU/Opensource teams are coming back at this with a vengeance, developing better protection methods. Stuff like this will rally security teams. Sure, not all bugs/vulnerabilities can be caught, but the ones that are...will have the living s--t kicked out of it. Chalk it up to valuable experience. I am sure developers are whipping themsleves into a mea culpa frenzy. A bit of humility will go a long way to making something superior.

    --
    "SO we bide our time, waiting for a purer kick to bloom and the future is still bleak, uncertain and beautiful" -GSYBE
  102. Re:Open source was never safer by BitZtream · · Score: 0

    You do realize that encryption is security through obscurity ... right? ActiveX is just a plugin system, just like XPCOM in firefox, but you know that too ... right?

    Please don't quote shit that you utterly fail to understand. The only part you got right was that IE was buggy as shit. Of course, so is Firefox, but you ignore all the security fixes it has gotten. The only thing is does better, and that Microsoft sucks at is time to fix, which while extremely important, is only part of the equation.

    +5 insightful ... the ignorance runs deep here.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  103. Re:Open source was never safer by hajile · · Score: 2

    I think this says more about the prevailing view of security. Every programmer is told "NEVER roll your own encryption". The default result is that most programmers never even look at the code and instead assume it MUST be safe since the infallible "experts" wrote it. What we are seeing here is not the fault of open source vs closed source; it is about voodoo programming being considered good security practice.

    I'm not saying that everyone should be rolling their own encryption, but people should be looking over the experts implementations instead of assuming they are perfect (this bug could have been caught by any number of "normal" programmers had they simply taken the time to looked).

  104. Re:Open source was never safer by binarylarry · · Score: 1

    Hahaha, this is hilarious that the GP is +5 insightful.

    --
    Mod me down, my New Earth Global Warmingist friends!
  105. Re:the heartbleed bug was introduced by a jew by nomanisanisland · · Score: 1

    it's not a matter of open source but a matter of having israel partisans working on mission critical code.

    You're obviously a troll and an idiot, but just for the record: I don't know if Seggelmann is Jewish - his last name is, but then so are a lot of German last names... and he's German (not Israeli) and there aren't many German Jews left - but the reviewer of the code was Stephen Henson, who is not Jewish. Do you blame him too? RSA (the company that became synonymous with public crypto, and the algorithms they patented) stands for Ron Rivest, Adi Shamir, and Len Adleman. The last two are also Jews, and Adi Shamir is actually an Israeli. Do you blame them too? In fact, according to the Bible, there's this guy named Jesus who was also a Jew. Do you blame him too? As it happens, there are a disproportionate number of Israeli programmers in the tech space, mostly because as far as I can tell they've always had a high ratio of well-educated people in math and comp sci, and lately an influx of of well-educated former-Russians too. Thank god it wasn't an Indian or Chinese programmer who caused this, or /. servers would collapse from the comments.

  106. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  107. Re:Open source was never safer by Anonymous Coward · · Score: 2, Insightful

    Encryption is not security through obscurity. Encryption is security through rigorous openness and review.

    "Security through obscurity is generally a pejorative term referring to a principle in security engineering, which attempts to use secrecy of design or implementation to provide security." The secret key in cryptography is neither design nor implementation.

  108. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  109. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  110. What if by Anonymous Coward · · Score: 0

    WHAT IF comments are worthless. The facts are that a serious bug existed in a widely used open source component for several years. Comments like what if the software were written differently or better tested or were proprietary are fanciful speculations. The real issue is how to avoid or at least reduce the likelihood of this occurring in the future. Recommendations that people should work harder or write better code are of course equally worthless.

  111. Re:Open source was never safer by Darinbob · · Score: 4, Informative

    Encryption is meant to make the original text be obscure, however the means of encryption should not remain obscure. What "security through obscurity" refers to is the common and naive practice of assuming that no one will guess your security methods, and the problem is that people do find this stuff out. Ie, assuming that no one will guess your backdoor debugger password. Now it is fine to start with a strong set of security practices and then only after that is in place it can be made more obscure. But usually when something is made obscure it is because the security is really weak in the first place.

    As for ActiveX, the problem was not that the end user would go and hunt down a trusted plug in and install it, but that it relied upon the web to tell you if something was trusted and then automatically install it (and for the average user this happened even without their knowledge). This was done at the same time that Java was promoted as an alternative, a system that was intended to be designed for security by sandboxing the code (though of course it had flaws) as well as being cross platform, whereas ActiveX was all about taking plain x86 code and executing it as long as it was signed.

    The real problem with ActiveX was the idiotic idea from Microsoft that it should be installed automatically without bothering the users with annoying questions such as asking for permission first; they did the same boneheaded move by allowing executables in emails to be executed without a confirmation. It wasn't until they started added UAC that it seemed they understood what the problem was.

  112. It's not about open or closed source IMHO by Bugler412 · · Score: 3, Interesting

    I think that it's really not about open or closed source. It's about monoculture, the whole net is more resilient if we didn't do that. So many warned about that issue with the desktop/laptop running Windows, and that risk is there and real still, but while worrying about that we built it anyway in an a non-OS specific way on servers too

  113. Re:How would proprietary software have handled thi by Cl1mh4224rd · · Score: 1

    The vulnerability was found specifically because the source code was available and someone other than the owners went looking for problems.

    I keep seeing people claim this. Codenomicon didn't discover the bug by looking at the source, but I can't find any information about how Neel Mehta discovered the bug.

    --
    People will pass up steak once a week, for crap every day.
  114. Re:This was positive by Cl1mh4224rd · · Score: 1

    The bug was found by code review, twice independently in a short period of days.

    Codenomicon didn't discover the bug due to a code review (source). I can't find any information on how Neel Mehta discovered the bug, though.

    --
    People will pass up steak once a week, for crap every day.
  115. Re:Open source was never safer by Anonymous Coward · · Score: 0

    They have had many (and likely will continue to do so), but the fact is that never (not yet anyway) have they had one with as severe and wide reaching implications as this one.

  116. Open Source Saves The Day by greggman · · Score: 1

    It's all a matter if spin. It should be "bug found and patched because of open source" if it was closed few if any would have been able to look and find and patch the bug

  117. Re:Open source was never safer by mysidia · · Score: 2

    Safer != Perfect

    Open Source is not perfect. It also does not help when you have large commercial institutions RELYING on the source code in a security critical role under constant attack by well-funded adversaries, AND the developers of said open source code are so pitifully underfunded, AND the commercial proprietors that cause said open source library to become a high-value target are only willing to invest in features, and not improvements that would lead to better quality and lesser likelihood of serious bugs.

  118. Open Source doesn't always follow the Bazaar model by Anonymous Coward · · Score: 0

    May I remind everyone that unlike most GNU, Apache and Linux projects, OpenSSL and OpenSSH follow the BSD model of a small team of developers doing the work. Although the source is available the review and upgrades are limited by the small group of developers working on the project. This model of developer is somewhere between the Cathedral and the Bazaar. The number of eyes on the code may be reduced because of the lack of ability of being able to make direct contributions to the code base.

  119. Open Source Heartbleed by hackus · · Score: 4, Insightful

    Fixed within, 24 hours on 187 servers running open source openssl libraries, f and earlier versions.

    I still do not have fixes for about 5 proprietary customer products, and there has been no word from 3 of them if they intend to fix them.

    I have informed my customers that they should consider moving from the proprietary products IF they have the cash to do so.

    I really do not see your point in asking the question.

    You cannot design and build secure software to begin with.

    You need to have the source code for the forseeable future now because of the world we live in.

    Very very bad people are coming out of the pit and they want your infrastructure, your data and your intellectual property.

    But above all, they want control of you.

    Open Source can prevent a world like that from taking hold, but it cannot save a fool from his foolishness.

    --
    Got Geometrodynamics? Awe, too hard to figure out? Too bad.
  120. When you use Linux, you help the Republicans by Anonymous Coward · · Score: 0

    Randall Long, formerly of a Obama administration, joins Microsoft. This guy leaves MS for the Obama administration. Al Gore sits on Apple's board.

    When you use Linux, you hurt MS's and Apple's profits, which hurts Democrats. When you use Linux, you help the Republicans.

  121. Re:Open source was never safer by fluffy99 · · Score: 1

    I think this says more about the prevailing view of security. Every programmer is told "NEVER roll your own encryption". The default result is that most programmers never even look at the code and instead assume it MUST be safe since the infallible "experts" wrote it. What we are seeing here is not the fault of open source vs closed source; it is about voodoo programming being considered good security practice.

    I'm not saying that everyone should be rolling their own encryption, but people should be looking over the experts implementations instead of assuming they are perfect (this bug could have been caught by any number of "normal" programmers had they simply taken the time to looked).

    The irony is that the openssl authors chose to roll their own malloc implementation instead of using the default, trusted one which would have likely crashed instead of facilitating the leakage of memory. (I still blame the fundamentally flawed nature of C for even allowing this)

  122. It was found, it was fixed by Anonymous Coward · · Score: 0

    sounds like its working as hoped, right?

  123. Eyeballs did not find bug ... by perpenso · · Score: 2, Informative

    The quote is "given enough eyeballs, all bugs are shallow." That's a clear admission that open software, like all other software, contains bugs; that's why you want the many eyeballs. Any claim otherwise is a symptom of not understanding plain English. Eric's whole point was that the bugs in open software will be found and fixed faster than the bugs in other software, due to the population of interested people who will study it, looking for the bugs.

    Perhaps it is not being stated clearly but the point that you are missing is the fact that this bug in some of the most critical network software in use had been around for 2 years. This fact demonstrates the hyperbole of the quote. Its a well crafted quote, illustrates a concept well, but people read way too much into it. Few FOSS users are developers, few developers are qualified readers. Eyeballs are a plus, but not a panacea. The gap between proprietary and open exists but it is exaggerated.

    A second and more important fact is that the bug was not discovered by eyeballs on source code. The techniques used seem to be the same applied to proprietary closed source code.
    "“We developed a product called Safeguard, which automatically tests things like encryption and authentication,” Chartier said. “We started testing the product on our own infrastructure, which uses Open SSL. And that’s how we found the bug.”"
    http://readwrite.com/2014/04/1...

    Nothing in that quote implies (to anyone with reasonable understanding of English and basic logic) that open software doesn't have bugs.

    Straw man.

    1. Re:Eyeballs did not find bug ... by DerekLyons · · Score: 2, Insightful

      Straw man.

      Sadly, straw men dominate this discussion. Thank you for seeing them for what they are.

    2. Re:Eyeballs did not find bug ... by Anonymous Coward · · Score: 0

      Only 2 years? Pretty quick for uninteresting part of code. For comparison, there were 88 bugs fixed in 13 year old Windows XP last year, and most of those bugs were dragged for all 13 years from version to version, ending up even in Win7/Win8.

    3. Re:Eyeballs did not find bug ... by Anonymous Coward · · Score: 0

      Only 2 years? Pretty quick for uninteresting part of code.

      So eyeballs aren't worth a damn ... thanks for conceding that.

    4. Re:Eyeballs did not find bug ... by Anonymous Coward · · Score: 0

      Seems like they're worth at least 7 times as much as eyeballs watching the most popular OS. But do keep strawmanning - as GP noted, errryone here does this, why should you be an exception?

    5. Re:Eyeballs did not find bug ... by jc42 · · Score: 1

      A second and more important fact is that the bug was not discovered by eyeballs on source code. The techniques used seem to be the same applied to proprietary closed source code. "âoeWe developed a product called Safeguard, which automatically tests things like encryption and authentication,â Chartier said. âoeWe started testing the product on our own infrastructure, which uses Open SSL. And thatâ(TM)s how we found the bug.â"

      So you're say that when I, as a (professional ;-) programmer, create a chunk of code that tests for something, you don't think I should get any credit for what it discovers, because it's the code that discovered it, not me. This pretty much shoots down the value of nearly everything I do, because like most programmers, I spend most of my time writing and running my test suites; the actual product itself usually takes only a small percent of my work time.

      Maybe I'm overly arrogant, but I disagree with this. I think that whatever a chunk of code does, the credit (or blame ;-) should go to the programmer, not the code or the cpu.

      By similar reasoning, we might argue that the "many eyes" never actually discover any bugs at all, because the real work is done by the brain behind the eyes, not the eyes themselves. And with computer bugs, the human brain almost never figures out the bugs; it merely writes code that does appropriate testing, providing the brain with information that it could never have figured out by itself.

      This is sorta the inverse of the old saw that guns don't kill people; it's saying that the human that pulled the trigger should get no blame for a killing, because it was the bullet (or maybe the trigger mechanism) that actually did the job.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    6. Re:Eyeballs did not find bug ... by perpenso · · Score: 1

      A second and more important fact is that the bug was not discovered by eyeballs on source code. The techniques used seem to be the same applied to proprietary closed source code. "âoeWe developed a product called Safeguard, which automatically tests things like encryption and authentication,â Chartier said. âoeWe started testing the product on our own infrastructure, which uses Open SSL. And thatâ(TM)s how we found the bug.â"

      So you're say that when I, as a (professional ;-) programmer, create a chunk of code that tests for something, you don't think I should get any credit for what it discovers, because it's the code that discovered it, not me. ...

      You are offering a strange misinterpretation of what I have said. I am saying that this bug was not found by someone examining source code. That if you fuzz or otherwise test the binary then whether the code is proprietary or FOSS is irrelevant.

  124. its not any less secure than closed source by Anonymous Coward · · Score: 0

    It does have the assumption that if more people view the source they will automatically fix vulnerabilities. This however assumes that people will always do the right thing and report bugs. For security flaws in particular this is not a given a lot of people that would have the knowledge to spot a bug may also be from governements or organised crime and have a vested interest in the code not being fixed.
    If you look at something like vms or aix, there may be big security holes but because it's closed source.....nobody knows

  125. Proprietary or open seems irrelevant to discovery by perpenso · · Score: 4, Informative

    The visibility doesn't make it so bugs don't exist. It makes them more likely to be found. This one existed and was found.

    After two years in the wild. And apparently *not* by eyeballs on source code. Proprietary or open seems irrelevant to this discovery.

    "“We developed a product called Safeguard, which automatically tests things like encryption and authentication,” Chartier said. “We started testing the product on our own infrastructure, which uses Open SSL. And that’s how we found the bug.”"
    http://readwrite.com/2014/04/1...

  126. Same as always by Anonymous Coward · · Score: 0

    The Open Source "many eyes" philosophy is only relevant when there are many eyes. This works great for non-specialized tasks, and ok for specialized tasks. For highly specialized tasks, the "many eyes" dwindles to "few eyes", and so the opportunity for long-lived errors is longer. In commercial settings, this is counteracted by the profit motive. In open source, the only counterbalance is project discipline. The key takeaway is to support disciplined FOSS projects for specialized functionality, or pay for this level of suppport.

  127. Casual Coding by pwileyii · · Score: 1

    I am of the opinion, and have been for a while, that casual coding (i.e. coding something in your free time, not backed by hint of monetary gain) is at the heart of the problem. People code casually because it is fun to do. They don't like writing comments, documentation, or clean code. This is not to mention that these project need good people that can write this complex code and putting massive amounts of rules and coding practices is not going to attract people to code in their free time. When you have code that is backed by money and/or a company, the motivation exists to do the not fun stuff, but the required stuff to make code more secure, more easy to audit, and easier to understand. Without that type of backing, you have people hacking away writing code as quick and dirty as possible. That is the reputation that FOSS is trying to get rid of. That is the reputation that hurts its adoption rate, especially in critical and important systems. That is the reputation that the OpenSSL vulnerability drags kicking and screaming into the limelight. Unfortunately, it is a reputation that has a significant basis in reality and, in my opinion, the Heartbleed vulnerability will have lasting effects for years to come.

  128. Closed source doesn't have Heartbleeds by ignavus · · Score: 1

    Closed source just has deliberate NSA backdoors. Clearl superior and much more efficient than accidental backdoors.

    "I is in your PC reading all your emailz!" - lolcat works for NSA

    --
    I am anarch of all I survey.
  129. Re:Open source was never safer by Barsteward · · Score: 1

    no, Raymond said the bugs are shallow, not non-existent - i'm sure you can understand the difference....

    --
    "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  130. APK? No. He's defending himself vs. libel by Anonymous Coward · · Score: 0

    In Zontar's case absolutely manic depression http://slashdot.org/comments.p... + multiple personality disorder http://slashdot.org/comments.p... given that information it's easy to see who's a mentally disturbed individual who doesn't consider the consequences of his actions and what is legal or not in libel. Some say that is the very definition of insanity. Not considering the consequences of their actions. Zontar fits that. I have to disagree after reading some of this.

    1. Re:APK? No. He's defending himself vs. libel by Zontar+The+Mindless · · Score: 1

      APK, you appear to be capable of making 2 and only 2 sorts of statements:

      1. Mischaracterisations

      and

      2. Lies

      You seem to prefer the former, I guess because in your twisted world they're more difficult for someone else to disprove.

      --
      Il n'y a pas de Planet B.
    2. Re:APK? No. He's defending himself vs. libel by OneAhead · · Score: 1

      I was talking about you, APK. Zontar is not the one obsessively flooding the discussion with offtopic incoherent ramblings. It's not what you say, it's what you do.

  131. Re:Zontar = sockpuppeteer & lying libelous tro by Barsteward · · Score: 1

    will you just fuck off polluting the posts with this shit

    --
    "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  132. Developers need time to do a good job by Paul+Fernhout · · Score: 1

    To really understand a lot of projects to the point where a developer can make substantial contributions often takes a substantial investment of time by a developer. So some combination of full-time employment in the area, government grants, a basic income, or gifts of some sort are required for experienced developers to have substantial time to look at source code. It's true some developers have time to do it as a hobby, and others might have time as students. But to really dig into complex code and keep at it for a substantial period of time require, in US society at least, generally requires some kind of external support (even if just a spouse who earns money). This issue is not helped by the fragmentation of many software projects via forks, the competition between similar FOSS projects, and the proliferation of languages and not-very-good standards which all chew up vast amounts of developer time.

    Of course, some people, like Bill Gates, who was born with a substantial trust fund have inherited the wealth needed to allow them to develop free software the rest of their life. However, for good or bad, he did not pursue that choice.
    "How to Become As Rich As Bill Gates"
    http://philip.greenspun.com/bg...
    "William Henry Gates III made his best decision on October 28, 1955, the night he was born. He chose J.W. Maxwell as his great-grandfather. Maxwell founded Seattle's National City Bank in 1906. His son, James Willard Maxwell was also a banker and established a million-dollar trust fund for William (Bill) Henry Gates III. In some of the later lessons, you will be encouraged to take entrepreneurial risks. You may find it comforting to remember that at any time you can fall back on a trust fund worth many millions of 1998 dollars."

    A substantial "basic income" equivalent to US Social Security from birth would, in a sense, make everyone a millionaire overnight and give them the time they need to pursue public benefit projects, whether doing code review or raising children well. Linux in part is a result of Finland's generous support for students like Linus.
    http://www.linfo.org/linus.htm...
    "Torvalds thus decided to create a new operating system from scratch that was based on both MINIX and UNIX. It is unlikely that he was fully aware of the tremendous amount of work that would be necessary, and it is even far less likely that he could have envisioned the effects that his decision would have both on his life and on the rest of the world. Because university education in Finland is free and there was little pressure to graduate within four years, Torvalds decided to take a break and devote his full attention to his project."

    --
    A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.
  133. All programs have bugs. by Z00L00K · · Score: 1

    It's just a question of how many of them that are discovered and how serious they are.

    In this case it was a simple mistake, and had serious effects. In other cases the bugs may be caused not by simple mistakes but a very complex chain of mistakes and still just result in a small side-effect.

    As I see it - the best way to avoid simple mistakes like missing to set a character limit is to restrict use of languages where this check isn't built into the language itself. C and C++ is good for some coding, but that code has to be strictly reviewed and cross-checked to ensure that it's secure. Other languages has a lower risk of simple mistakes because they don't allow the user to address data outside the boundaries of a declared variable, or they do extend the allocation of a variable when needed.

    So looking into languages like Ada, Java, C# and Matlab/Simulink (or the clone Scilab) should be on the list of languages to consider. Even Basic would be worth to consider. Or if you want to be a bit more esoteric Erlang is not a bad choice.

    Just be aware that almost every programming language has a basic platform written in C, so it's important to make sure that the platform doesn't have any problems.

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  134. Re:This was positive by Barsteward · · Score: 1

    Bye

    --
    "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  135. Static analysis ? by savuporo · · Score: 1

    In all this hoopla i havent bothered to look at the code in question yet, but im always slightly dismayed when i throw some popular open source stacks at commonly available but expensive static analysis tools like Coverity or Klocwork.
    There are plenty of companies running full open source stack servers with the licenses available - i wonder how often things like OpenSSL and other critical infrastructure pieces go through the best static analysis tools available ? And how much of it gets addressed.

    --
    http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org Errors found while checking this document as HTML5!
    1. Re:Static analysis ? by savuporo · · Score: 1

      Lame reply to self but, yeah, according to the most basic static analysis tools, it was broken in 2012
      http://www.viva64.com/en/b/018...
      and still broken in 2013
      http://www.viva64.com/en/b/025...

      --
      http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org Errors found while checking this document as HTML5!
  136. Re:Open source was never safer by znrt · · Score: 1

    You do realize that encryption is security through obscurity ... right?

    i don't think this quote means what you think it does.

    Please don't quote shit that you utterly fail to understand.

    ditto.

    ActiveX is just a plugin system,

    as much as a shotgun against your head is just a metal tube.

    the ignorance runs deep here.

    don't be so modest. you just contributed a fair share.

  137. Re:This bug was found in OpenSSL because it was op by m.alessandrini · · Score: 1

    And don't forget the *deliberate* security holes placed in close software. A link that comes to my mind: http://en.wikipedia.org/wiki/N...

  138. Re:Open source was never safer by indeterminator · · Score: 1

    You do realize that encryption is security through obscurity ... right?

    No, it's not. The major difference is, that with a proper cryptosystem, if someone discovers your key, you can just switch to a new key and you're as safe as you were (not considering collateral caused by key leak). With security through obscurity, the once the genie is out of the bottle, you won't make it safe without changes to the design of the system.

    As someone said, the ignorance runs deep here.

  139. Re:Zontar = sockpuppeteer & lying libelous tro by Zontar+The+Mindless · · Score: 1

    I don't HAVE to say that your Hosts File Engine is crap, Spanky. Half the freaking Internet has already said it for me.

    Your app doesn't do anything that any text editor with basic regular expression support can't do better already, and do so WITHOUT pegging a 4-core CPU.

    And there is NO WAY IN HELL that I'm EVER going to let such an abomination override the OS task scheduler on any system I administer. That's just insane.

    --
    Il n'y a pas de Planet B.
  140. Why not teach more with open source? by hughk · · Score: 1

    The key issue with this is that many eyes did not check this code. One way to get many eyes is via university. Open source is great for learning about how existing code is written, including safe practices vs. "performance". Usually people are asked to review smaller pieces of code like kernel components as part of coursework. This demonstrates it is useful perhaps to consider other, less sexy bits. Note that changes are being committed over time so there is always new material.

    --
    See my journal, I write things there
  141. Re:Zontar: "Rinse, Lather, & Repeat" (lol) by Zontar+The+Mindless · · Score: 1

    How does linking to the top of the same thread help your case? Why do you keep doing that?

    Hyperlinks are not magic. There needs to be some meaningful content at the other end for them to be of any use.

    ProTip: Making a false claim which merely links to a repetition of the false claim does not make the false claim true.

    --
    Il n'y a pas de Planet B.
  142. Re:Open source was never safer by Anonymous Coward · · Score: 1

    Encryption is meant to make the original text be obscure, however the means of encryption should not remain obscure.

    That is true, but the problem with OpenSSL is that much of the code has been deliberately obscured.

    I once tried to use part of the encryption codes from OpenSSL in another project - after awhile I gave up and realized that the original implementation (can't recall which one - might have been Blowfish) was cleaner, and easier to understand.

    It seems that it in order to be included in OpenSSL it had been rewritten to conform to some coding standard that made it more fragile and less readable; I assume this was done because of some coding-hubris in the OpenSSL-team.

    Here are some others that also have issues with the OpenSSL code-base:
    http://article.gmane.org/gmane.os.openbsd.misc/211963
    https://www.peereboom.us/assl/assl/html/openssl.html

    So, I believe the conclusion is that "Open source can be safer - if done right".

  143. Re:Proprietary or open seems irrelevant to discove by rioki · · Score: 1

    Why are you so adamant that it was not "eyeballs". So they fizzed their own infrastructure and found the issue. The article you posted is scant on the details if the tool and a google search did not turn up any salient details on the tool. From the description it appears to be black box testing SSL/TLS for obvious overruns. Was this not open source software, we may not have had such a quick response to this issue.

  144. Re:Open source was never safer by Big+Hairy+Ian · · Score: 1

    Don't for get Oracle!

    --

    Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

  145. An oddity by sjames · · Score: 1

    The comment in TFA about marketing seems dead on. I honestly cannot think of any other disclose security vulnerability that got it's own logo.

  146. Can you propose one? by Ungrounded+Lightning · · Score: 1

    There are no reliable metrics that indicate FOSS is safer. None.

    Can you propose a metric that would compare the "safety" of FOSS versus closed-source/proprietary software?

    (I thought not.)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  147. Re:That's kind of curious by Caesar+Tjalbo · · Score: 1

    I think the grandparent was right. MS now is hugely better than the MS of 10-15 years ago.

    Hugely worse is hardly imaginable.

    --
    "I'm not much interested in interoperability. I want substitutability. I want to be able to throw your software out."
  148. Bell curve by Captain_Chaos · · Score: 1

    No matter how narrow the bell curve, outliers are still gonna happen.

  149. Re:Also by Anonymous Coward · · Score: 0

    I would like to just point out this is a huge win in my book for Debian.

    Are you kidding? Debian once implemented a custom change that deliberately weakened all SSL keys generated on Debian systems:

    http://www.debian.org/security...
    https://wiki.debian.org/SSLkey...

    Young whippersnappers with short-term memory...

  150. Re:Open source was never safer by amck · · Score: 1

    It is not the NSA's job to cause mudslides, or make peoples hair fall out.

    It is NSAs JOB to crack (other peoples) security systems. You are not being paranoid, they are out to get you.

    Of course, other agencies do this too ...

    --
    Anyone who believes exponential growth can go on forever in a finite world is either a madman or an economist
  151. Well.... the bug did get swallowed by nhat11 · · Score: 1

    eventually lol.

  152. Re:Proprietary or open seems irrelevant to discove by Anonymous Coward · · Score: 0

    Proprietary or open seems irrelevant to this discovery.

    You can't make such conclusions from one bug. Bugs will happen, and bugs will go unnoticed. The question is about whether the open source nature of a piece of software decreases the frequency of those events.

  153. Re:Security is hard. Encryption is even harder. by Anonymous Coward · · Score: 0

    For wont of mod points here... YES! THIS!

    Entirely too many point the fingers at FOSS coding practices, etc.

    A closed source business is actually quite a bit more likely to have made this screwup than a FOSS one because they're as often as not more inclined to give security only an afterthought- and many times features are driven by marketing than any sound design decisions. What we have here is a revelation that security is hard- the feature that was "innocent" should have never found it's way into the code base in the first place. At least not in the very ill-advised method that was used. This is a stupid thing that would've happened either side of the fence on the FOSS/Closed issue. This is because most fools think that security or encryption is "easy" or think that they should add any old sort of "ease of use" features on top of security functions, etc.

    Yes, you should try to make it very easy to use- but ease of use should be your LAST thoughts on a security related feature set. It's easy to weaken the security as shown by Heartbleed.

  154. Many bad analogies make comparisons useless by sirlark · · Score: 1

    "Many eyes makes bugs shallow" applies not only to people working on the buggy code itself, but also all the developers who use the code. Bugs are almost always almost found because of software behaviour, and in general bugs in closed or open software are equally likely to be discovered by end-users. Bug are far more likely to be found by developers though. Consider some different scenarios: (1) A bug is discovered because following the documentation on how to use some API doesn't work exactly as expected; a really bad bug because behaviour under normal conditions is wrong. (2) A bug is discovered because a developer makes an invalid call to an API and it doesn't error out gracefully; still a bad bug, but most developers are going to correct their code to use the API correctly, and maybe file a bug report if the problem is bad enough to break their software. In case (1) someone is always going to file a bug report, closed or open source doesn't matter. In case (2) is different; chances are a developer isn't going to bother submitting a bug report if the buggy code is closed source, they'll just write some validation around the API call to avoid the bug before it happens. If open source, this validation will probably be submitted as a patch upstream, or at least someone is likely to report the bug. But then there's case (3), heartbleed. What you've got here is a bug that for correct input works, no bug to file, for incorrect input appears to still work, so still no apparent bug, but for incorrect input it does extra stuff you don't know in advance to check for. A developer with a case (3) bug is far less likely to discover that bug. If the library is open, a developer debugging their code might step into the library code and see the problem, slightly increasing the likelihood of the bug being found in open source as compared to closed.

    The point is that downstream developers count as 'eyes', and probably make up the majority of those eyes. Because of lower barriers to entry, open source projects when compared to their equivalent closed-source counter parts tend to have many more downstream developers. Even is the case of non-library, end-user application projects, other devs are write plugins, extensions etc. so this remains mostly true. The argument that the eyes don't exist is not true. The eyes may not be looking directly at the code, but the code's behaviour is being tested in a variety of other ways. Case (1) bugs are going to be found and reported regardless of whether the source is open or not. Case (2) bugs are probably equally likely to be found, but far more likely to be reported and fixed if the buggy code is open source if there is a downstream workaround. Case (3) bugs are hard to find either way, but are MUCH easier to fix in the open source world.

  155. Re:Proprietary or open seems irrelevant to discove by TsuruchiBrian · · Score: 1

    After two years in the wild. And apparently *not* by eyeballs on source code. Proprietary or open seems irrelevant to this discovery.
    "“We developed a product called Safeguard, which automatically tests things like encryption and authentication,” Chartier said. “We started testing the product on our own infrastructure, which uses Open SSL. And that’s how we found the bug.”"

    Given the simplicity of this bug, it's not hard to imagine what the source code for the bug looked like given the behavior. It is also not hard to imagine that upon discovering the unexpected results, the bug was confirmed by looking at the source code. Maybe for this bug, looking at the source code was just a confirmation of what they already knew. For many other bugs, looking at the source code is necessary to efficiently figuring out what the code is actually doing.

    I'm not saying that this exact bug was found because it was in open source code. I am saying that it is not hard to imagine how a bug like this would be easier to find in open source software than closed source software.

    At my company we use open source software libraries for our commercial products. When we find anomalies, we are actually able to figure out if bugs are in our own software or in the open source libraries we use. In fact, we actually run static analysis tools on every piece of open source software that we use because we care about the security of our own applications. We don't use openSSL, but if we did, we may have actually found this bug. That wouldn't be possible if the source was closed.

  156. Re:How would proprietary software have handled thi by swillden · · Score: 1

    I can't find any information about how Neel Mehta discovered the bug.

    By looking at the source.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  157. No monoculture by DrYak · · Score: 1

    OpenSSL has no competition at its core competency, so the team really has no motivation to deliver an iteratively better product, apart from their need to scratch an itch. FLOSS software projects tend not to operate in a competitive environment, where multiple OSS products are useful for the same thing and vie for placement. This is probably bad.

    I definitely don't agree.
    Take any rant against FLOSS, the first thing you'll hear is complaints about "too much choices to pick from".
    Sorry, but you can both complain that there's too much choice (hard on the user) and at the same time not enough choice (hard on security).

    In the case of encryption, OpenSSL is far from the only present library. Its IS indeed very popular, but it's not the only used library.

    GnuTLS is another popular library, which wasn't affected by Heartbleed (not specifically by this bug. It's not without problems, but still).

    Mozilla's NSS seem popular with browsers (Firefox and Chrome use it, probably others too -and not only browsers: Pidgin uses it too). Again a different library, popular too

    And that's just he major libraries. Then there are ton of others to chose from.

    Some written in higher level language (Botan is in C++) and some (I hope, I haven't tested them all) probably using some facilities to abstract away a few pitfall like buffer lengths.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  158. Panglossian Nonsense by Capt.Albatross · · Score: 1

    ...Chalk it up to valuable experience...

    According to this sort of argument, nothing bad ever happens. The Air France 447 crash will improve pilot training, the Boston Marathon bombing will improve race security...

    This point of view gives us no insight in to how to improve things. It belongs in the 'not even wrong' category.

  159. Re:Leaked by codenomicon AND Google by Anonymous Coward · · Score: 1

    One Google researcher and two Codenomicon researches disclosed this together. Funny how that was left out.

  160. Need for better systems programming languages by Anonymous+Brave+Guy · · Score: 1

    I suspect you meant that sarcastically, but if system software (meaning OS kernels, network stacks, device drivers, etc.) were written in better languages, our computer systems could be far safer and more robust, quality of life could be better, and the benefit to productivity and the global economy could be substantial.

    For the computing industry, it is one of the great tragedies of our time that C and its derivatives have become so entrenched. There is absolutely no reason we can't have a systems programming language that offers the necessary low-level control without the limited programming model, error-prone syntax and weak safety features of C.

    Unfortunately, it is momentum and ubiquity that keep most of the industry using C and its brethren, not technical merit. The vast ecosystem surrounding C is hard to beat for scale. There is promising work being done in some places, Rust for example, but I know of no practical alternative that is ready for production use today.

    Of course, OpenSSL itself isn't running at the level of an OS kernel, so it doesn't need the same degree of low-level access anyway. But there is a wider point here about much more than just OpenSSL.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  161. She ? by Anonymous Coward · · Score: 0

    Seriously, who is "she" ?

  162. Re:Open source was never safer by Anonymous Coward · · Score: 0

    Saying Microsoft has better security record is like saying your shit-sandwich has nearly the least shit of any shit-sandwich vendor, but ignore that crazy guy selling sandwiches after washing his hands.

  163. 2003 called ? by Anonymous Coward · · Score: 0

    I hope you warned them about March 11th 2004 terrorist attacks in Madrid..

  164. Heartbleed is actually evidence that OSS is safer by Anonymous Coward · · Score: 0

    If OpenSSL was not open source, but some black box library from a major vendor, this bug would have never been found and fixed (many Windows or SCADA bugs going unfixed for years ...). Or it would have been fixed in silence, to avoid embarrassment of the vendor, leaving everyone else unsafe.

    I don't know what better evidence for open source software being safer do we need. OSS doesn't mean that there are no bugs, but that they get eventually found and fixed by someone, without being left at the mercy of the vendor of the software. This has worked really well in this case.

  165. They're a pack of pricks like YOU Zontar by Anonymous Coward · · Score: 0

    99% of Arstechnica = trolling TALKERS that haven't achieved squat who altered posts of mine on the arstechnica site itself, AND, on their own personal sites!

    They also stalked me all over the web harassing me.

    (Pime example thereof = Jeremy Reimer, & his pal Jay Little - BOTH of whom had their website's REMOVED BY THEIR HOSTING PROVIDERS for libeling me, email harassing me, stalking me site-to-site over the web, for YEARS... only to have me uttterly FLOOR THEM over @ Windows IT Pro during "The Memory Optimization Hoax" article where Jay Little, who came there @ Jeremy Reimer's request, claimed he was an "exchange expert" - ONLY TO HAVE ME TOTALLY DESTROY HIM on the fact that Microsoft's own documentation PROVED that memory optimizer techniques & programs can UNHALT stalled Exchange servers - speeding them up when frozen).

    They altered posts of mine there as well... they're shit, plain & simple.

    IF I AM LYING HERE, then WHY did CrystalTech REMOVE Jay Little's website?

    &

    IF I am lying here, then WHY did Shaw of Canada put Jeremy Reimer on a TRACKING TICKET to monitor his email harassing me AND kick his website off their servers as well??

    Hmmm?

    APK

    P.S.=> They, like you? Aren't FIT TO LICK MY BOOTS, you libeling little scumbag:

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    ... apk

    1. Re:They're a pack of pricks like YOU Zontar by Zontar+The+Mindless · · Score: 1

      Given your recent track record with me and other Slashdotters--and the fact that Jeremy's and Jay's websites appear to be alive and well--I am going to assume that you're at least mischaracterising and most likely just outright lying.

      --
      Il n'y a pas de Planet B.
  166. Quit avoiding THIS Zontar... apk by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    (YOU CAN'T, CAN YOU?)

    APK

    P.S.=> Obviously NOT as you avoid that like the plague, you done zero BIGMOUTH libeling little troll... apk

    1. Re:Quit avoiding THIS Zontar... apk by Zontar+The+Mindless · · Score: 1

      I'll repeat what I've already said elsewhere:

      1. I've yet to find a single case where one of your host files trolls was even remotely on-topic.

      2. Your "host files engine" is a useless, CPU-sucking piece of crap, and I am very far from being the first one to say this. (Furthermore, you actually boast about its horrid performance as if it were something to be desired.) In addition, it overrides the Task Scheduler for no good reason whatsoever. That in my opinion qualifies it as something I would never in a million years permit anywhere near any machine that I use or administer; IOW it is for all intents and purposes malware and no amount of your ranting and raving and trolling and crapflooding is ever going to change this fact.

      --
      Il n'y a pas de Planet B.
  167. Cat got your tongue, scumbag? by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    (YOU CAN'T, CAN YOU?)

    APK

    P.S.=> Obviously NOT as you avoid that like the plague, you done zero BIGMOUTH libeling little troll... apk

  168. Your "job" is "writing" LMAO... by Anonymous Coward · · Score: 0

    Which I don't believe considering you spend so much time here it is unreal, first of all. Secondly?

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    (YOU CAN'T, CAN YOU?)

    Any IDIOT can 'write words' about programs - me? I actually WRITE THEM, you unskilled bigmouthed whose mouth wrote checks he can't backup LITTLE libeler (like you).

    APK

    P.S.=> Obviously NOT as you avoid that like the plague, you done zero BIGMOUTH libeling little troll... apk

    1. Re:Your "job" is "writing" LMAO... by Zontar+The+Mindless · · Score: 1

      I apparently didn't have time to troll someone TWO HUNDRED TIMES in a single day, whereas you OBVIOUSLY had time to do so, because you DID in fact do just that.

      You must be weak in the head if you think that is not patently obvious to anyone observing these proceedings.

      --
      Il n'y a pas de Planet B.
  169. Backup thils libel of yours Zontar by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    (YOU CAN'T, CAN YOU?)

    APK

    P.S.=> Obviously NOT as you avoid that like the plague, you done zero BIGMOUTH libeling little troll... apk

  170. Answer this scumbag by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    (YOU CAN'T, CAN YOU?)

    Changing the parameters now eh TELLLING MORE LIES!

    What was said was that I killed the process scheduler here:

    http://slashdot.org/comments.p...

    SO HOW AM I DOING THAT BY SETTING MY APP INTO HIGHER PROCESS PRIORITIES hmmm?

    You're SUCH A BULLSHITTING twisting of words libelous little troll... you're pitiful.

    APK

    P.S.=> Obviously NOT as you avoid that like the plague, you done zero BIGMOUTH libeling little troll... apk

  171. Backup your libel Zontar by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    (YOU CAN'T, CAN YOU?)

    APK

    P.S.=> Obviously NOT as you avoid that like the plague, you done zero BIGMOUTH libeling little troll... apk

    1. Re:Backup your libel Zontar by Zontar+The+Mindless · · Score: 1

      Have you found the book review yet?

      --
      Il n'y a pas de Planet B.
    2. Re:Backup your libel Zontar by Anonymous Coward · · Score: 0

      Have you ever faced each point apk put up about you for your libeling him troll?

    3. Re:Backup your libel Zontar by Anonymous Coward · · Score: 0

      You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

  172. Backup your libel Zontar by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    APK

    P.S.=> "Run, Forrest - RUN!!! you'll avoid THAT like the plague (per my subject line above) - why's THAT, Zontar, you libelous freak? apk

  173. Backup your libel Zontar by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    APK

    P.S.=> "Run, Forrest - RUN!!! you'll avoid THAT like the plague (per my subject line above) - why's THAT, Zontar, you libelous freak? apk

  174. Zontar can't back up your libel? by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    Work? YOU call what YOU CLAIM to do, work?? LMAO... a child can write words (even about programs)... can you write decent programs though (like myself)??

    LOL - HELL NO!

    APK

    P.S.=> "Run, Forrest - RUN!!! you'll avoid THAT like the plague (per my subject line above) - why's THAT, Zontar, you libelous freak? apk

  175. Zontar: "Cat got your tongue"? by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    APK

    P.S.=> "Run, Forrest - RUN!!! you'll avoid THAT like the plague (per my subject line above) - why's THAT, Zontar, you libelous freak? apk

  176. It's one data point... by TechNeilogy · · Score: 1

    ...get back to me in 100 years.

    --
    "The wisdom of the Patriarchs was that they *knew* they were fools." --Master Foo
  177. "There is nothing you can do..." by Anonymous Coward · · Score: 0

    "... To Stop it. The process has already begun. I receive no pleasure in this. It is simply the only logical solution... - Ultron 6 FROM -> http://www.youtube.com/watch?v...

    THUS:

    "Shutdown code, rejected: My programming ( http://start64.com/index.php?o... ) has advanced beyond YOUR commands: Beyond YOUR weakness" - Ultron 6 FROM -> http://www.youtube.com/watch?v...

    * Not a DAMN THING you can do about it - as you trolls most CERTAINLY can't disprove my points on hosts files giving users of them added speed, security, reliabliity, & anonymity online - period.

    (You know it, I KNOW IT - heck, anyone reading with 1/2 a brain on /. the past 2-3 yrs. now does as well, seeing you trolls harass me to no end - only to end up with EGG ON YOUR FACES being unable to disprove 17 points on the benefits noted above @ the download link to my program above)

    APK

    P.S.=> It quite simply CAN'T be done - why you would do that, used to boggle my mind. It's a good program, that does the job & offers EXACTLY the benefits I extoll here & enumerate in its download link. HOWEVER - It doesn't anymore.

    You're either malware makers/botnet masters (since I block them out refreshed daily from 12 reputable & reliable sources in the security community), advertisers (obviously, I block their ads which steal your speed you PAID for & infect you too with malicious scripts quite often + track you), inferior competitors (Ghostery/AdBlock/RequestPolicy), or webmasters (who are pissed off I block their ads - well, those have been getting exploited, & I held off on letting my app out (not anymore after that)) & it isn't "Souled-Out" INFERIOR either (doing far less & not as well) like SOME browser addons (Adblock & Ghostery) & it also shores up security faults in DNS & speeds up resolution of your fav. sites you hardcode in it (faster than remote DNS lookups + secures you vs. DNS request logs + DNSBL) too - multiple bonus!...

    .. apk

  178. Competency and Mind Clouding by Ronin+Developer · · Score: 1

    The issues, whether it be closed / proprietary or open source is two fold:

    1) Competency of the person writing the code or making the design changes.

    2) Competency of the person who is reviewing the work to understand potential issues surrounding the design and, as applicable, the implemented code.

    A developer SHOULD never be a final reviewer of their own work. They can double check their work, clean it up, verify it meets coding standards.. But, ultimately, it comes down down to the one or more competent reviewers to study the work.

    When one writes a paper or a long-winded post and try to review our work immediately after it is written, the brain will, by nature, fill in the gaps. If you have to critically review your own work, walk away for a day or two and then come back and tackle the assignment. You will be amazed at the errors you missed before.

    FOSS is not any more safer than proprietary code if nobody who understands has the capability to understand the code and issues actually looks at it critically. A few years ago, the OpenSSL team achieved FIPS 140-2 compliance which was a major undertaking and achievement. I haven't yet checked, but did the version affected by Heartbleed pass FIPS 140-2 certification as a cryptographic token? Or, did they never resubmit the code for recertification? I would suspect it was never resubmitted as the cost for certification is too high. Had it been done, this MIGHT have been exposed long before now.

    What WAS done correct was the rapid response once the problem was identified. This is something that corporations may drag their heels on as there a legal and financial repercussions when a vulnerability is found - even worse with an live exploit in the wild. They have to perform a risk analysis (on all levels) and determine if a fix is to happen at all. At the same time, corporations that rely on any system without a service level agreement that covers such issues take a major risk. This is where reliance on FOSS can bite you and why many corporations still maintain critical systems on proprietary operating systems and commercial software.

  179. Everyone ready? "See Zontar RUN" by Anonymous Coward · · Score: 0

    "I don't HAVE to say that your Hosts File Engine is crap." - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @02:45AM (#46764647)

    You're more than welcome to disprove the 17 enumerated points here I list that give users more speed, security, reliablity, & even anonymity then http://start64.com/index.php/6... and show us YOU CAN WRITE A BETTER ONE, libeler (see my ps below, & backup your libel there too loser).

    ---

    "Your app doesn't do anything that any text editor with basic regular expression support can't do better already, and do so WITHOUT pegging a 4-core CPU." - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @02:45AM (#46764647)

    For starters:

    Didn't know those could do a REVERSE DNS lookup and speed up your favorite websites (by resolving using the 1st lookup too, hosts, locally - which is FAR faster than calling out to a remote DNS since hosts is cached in RAM).

    My program does... do they?
    (YOU FAIL again, libeler)

    "And there is NO WAY IN HELL that I'm EVER going to let such an abomination override the OS task scheduler on any system I administer. That's just insane." - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @02:45AM (#46764647)

    LMAO - CHANGING WHAT WAS SAID HERE ERRRONEOUSLY NOW Zontar?

    http://slashdot.org/comments.p...

    SO HOW AM I DOING THAT BY SETTING MY APP INTO HIGHER PROCESS PRIORITIES hmmm?

    APK

    P.S.=>

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    ... apk

    1. Re:Everyone ready? "See Zontar RUN" by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 mod ensures all /. sees your post + Zontar running from it.

  180. Bugs exist in code. by Anonymous Coward · · Score: 0

    >As Eric Raymond famously said, 'given enough eyeballs, all bugs are shallow.'

    He doesn't say they don't exist. Look at how fast it was patched though. Microsoft would have taken months.

  181. This could happen to anyone by Anonymous Coward · · Score: 0

    The simple fact is that Heartbleed was caused by a mistake that any programmer, paid or unpaid, free or proprietary, could make. The entirety of the code commit was freely available for anyone to look at at any time, increasing its audience beyond that of closed-source code. Just because no one managed to catch it prior doesn't mean that open source is not safer. In fact, if it had been closed source, the exploit could very likely have remained unnoticed for much longer.

  182. Don't change the subject Zontar by Anonymous Coward · · Score: 0

    WHY were their websites removed by hosting providers @ CrystalTech & Shaw?

    ANSWER THAT.

    Is it perhaps since ARSTECHNICA = libeling trolls just like YOU? Figures you'd use your FELLOW LIBELERS to "back you up" but it's ineffectual

    ---

    Changing the parameters now eh TELLLING MORE LIES!

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    SO HOW AM I DOING THAT BY SETTING MY APP INTO HIGHER PROCESS PRIORITIES hmmm?

    You're evading where you FUCKED UP again, & telling LIES about it now? LMAO... you fail.

    APK

    P.S.=>

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    You said my "APK Hosts File Engine" is a virus/malware http://slashdot.org/comments.p... but it's EASILY PROVABLE it's not, right there in that link too.

    Now PROVE YOUR FALSE ACCUSATION above: Show me a quote OR POST of me posting off topic on hosts where they did NOT apply... go for it!

    You'll "Run, Forrest: RUN!!! as usual from THAT... why is THAT Zontar? We KNOW why (libeler)... apk

    1. Re:Don't change the subject Zontar by Zontar+The+Mindless · · Score: 1

      I've already made it crystal clear that I am utterly certain that you are engaging in gross mischaracterisation, as this is one of your trademarks.

      Like I said before: If APK tells us that the sky is blue, I'm going to assume that this is a lie until I look out the window and see it for myself.

      --
      Il n'y a pas de Planet B.
    2. Re:Don't change the subject Zontar by Zontar+The+Mindless · · Score: 1

      IOW you need to offer proof that this is what happened.

      ProTip: Linking to one of your own posts does not constitute proof.

      And like I've said before, as far as I can tell, every single one of your host files spamvertisements has been off-topic.

      Since they are nothing but spamvertisements for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system, your posts are by definition useless and off-topic. Q.E.D.

      --
      Il n'y a pas de Planet B.
  183. Show us a post as proof Zontar... apk by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Show us a post as proof Zontar... apk by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 mod ensures all of /. will see that post of yours + Zontar running from it.

  184. You appear to be "running", Forrest (lol) by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:You appear to be "running", Forrest (lol) by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 moderation ensures all of /. will see that post of yours + Zontar running from it.

    2. Re:You appear to be "running", Forrest (lol) by Zontar+The+Mindless · · Score: 1

      Your usermode app *subverts* normal process scheduling. You *bragged* about this until it was pointed out that this is a really, really bad thing to do.

      All I can see is that those two individuals' websites appear to be alive and thriving.

      And how you can try to portray getting kicked off Ars at least 4 times as some sort of victory is pretty silly.

      But we've come to expect mischaracterisation from you much as we'd expect cowflop from the wrong end of a cow.

      --
      Il n'y a pas de Planet B.
    3. Re:You appear to be "running", Forrest (lol) by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 moderation ensures all of /. will see all those posts of yours downmodded to -1.

      TFTFY, dumbass.

  185. "Run, Forrest: RUN!!!", lmao... apk by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:"Run, Forrest: RUN!!!", lmao... apk by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 mod ensures all /. will see that post of yours + Zontar running from it.

  186. Zontar - BACKUP YOUR bullshit... apk by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Zontar - BACKUP YOUR bullshit... apk by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 moderation ensures all of /. will see this post of yours + Zontar running from it.

  187. Zontar (ac now?) - backup your bs by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Zontar (ac now?) - backup your bs by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 mod ensures all /. sees that post of yours + Zontar running from it.

  188. LMAO - "See Zontar RUN" (like Forrest) by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apkview=article

    1. Re:LMAO - "See Zontar RUN" (like Forrest) by Anonymous Coward · · Score: 0

      Good job apk. Zontar's +5 moderation ensures all /. will see this post of yours + Zontar running from it.

  189. No Zontar YOU do need to provide proof by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:No Zontar YOU do need to provide proof by Anonymous Coward · · Score: 0

      Great job apk. Zontar's running. All /. can see it under his +5 moderated post (done by his sockpuppet TrollingForHostsFiles no doubt as to that upmod, big mistake that after this post of yours on Zontar's part, using sockpuppets too)

  190. Open Governance by lhunath · · Score: 1

    The same argument can be applied to government. Just because all laws are visible to the public doesn't mean we don't ever put and keep bad laws in effect. The solution to bad laws is not hiding them, it's more publicity. Similarly, more review on each commit would help the OpenSSL project.

    --
    ``OK, so ten out of ten for style, but minus several million for good thinking, yeah?''
  191. Ready everyone? "See Zontar RUN!!!" by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Ready everyone? "See Zontar RUN!!!" by Anonymous Coward · · Score: 0

      Good Job apk. Zontar's +5 upmod ensures all /. sees him run from your post.

  192. It does so to run FASTER stupid by Anonymous Coward · · Score: 0

    Same reasons I did well with UltraDefrag64 suggesting it to them & they put me in its credits no less (good program) - soon I'll be adding a 100 part 'breakup' of large intake data to make it even FASTER (along with doing what PeerBlock does, albeit MINUS adding "more" parts in layered drivers, by simply populating an existing tool that works, like hosts, in the Windows firewall, with known bad IP addresses & any the users wants to add (like I did with the 100's of things connecting to YOU here on /. - none of them slow me down, track me, or serve scripts to me either unlike you, dumbass... see subject-line above, lol!).

    NOW:

    Quit running away from producing the REST what's asked of you -> http://slashdot.org/comments.p... since you've FAILED this part badly - changing words you used now stupid? WEAK & STUPID... just like you.

    APK

    P.S.=> Oh, so NOW it's "subverts", eh? No stupid, it's using the process scheduler subsystem to do so dumbass:

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    ... apk

    1. Re:It does so to run FASTER stupid by Anonymous Coward · · Score: 0

      Perfect. Nail in Zontar the libeler's coffin. He won't face the rest of your points apk and he's running. This is almost as good as when you splattered arstechnica at Windows it pro mag forums.

    2. Re:It does so to run FASTER stupid by Anonymous Coward · · Score: 0

      Again: How would the process scheduler be turned off by doing that?

      It wouldn't. In basic English, sticking a qualified like "effectively" in front of a statement means "This doesn't actually do this, but the effect is the same".

      You can learn more about this by googling for remedial English lessons in your neighborhood. Who knows, if you go on one of those courses, they may give you a diploma!

  193. Re:Proprietary or open seems irrelevant to discove by perpenso · · Score: 1

    Why are you so adamant that it was not "eyeballs". So they fizzed their own infrastructure and found the issue. The article you posted is scant on the details if the tool and a google search did not turn up any salient details on the tool. From the description it appears to be black box testing SSL/TLS for obvious overruns.

    And such testing would find such a bug equally well in proprietary or open source code. It seems fairly clear that the bug was not discovered by someone reading the source code, despite the code being available for two years and the code being absolutely critical to networking.

    The value of many eyeballs is often exaggerated. Few users are developers. Few developers are qualified readers.

  194. Access to lib source does not require FOSS ... by perpenso · · Score: 1

    At my company we use open source software libraries for our commercial products. When we find anomalies, we are actually able to figure out if bugs are in our own software or in the open source libraries we use. In fact, we actually run static analysis tools on every piece of open source software that we use because we care about the security of our own applications. We don't use openSSL, but if we did, we may have actually found this bug. That wouldn't be possible if the source was closed.

    That is not true. At past jobs where we used proprietary libraries in our commercial products, I always advocated for buying the more expensive source licenses rather than the less expensive binary only licenses. We even chose vendor A over vendor B due to A have a source option and B not having one. Fortunately all the libraries we used had source options, obviously YMMV. Management was always reluctant until we found and resolved problems in these proprietary libraries just as you describe doing in open source. Management quickly became believers in buying the source licenses so that our fate was not in a 3rd party's hands.

    1. Re:Access to lib source does not require FOSS ... by TsuruchiBrian · · Score: 1

      OK fine. It would not be possible if you did not have access to the source code. It is true that you can buy access to the source from some closed source software. But the fact that you are choosing software based on whether you are able to access the source code, I would argue is a point in favor of open source software rather than closed source proprietary software (the vast majority of which you can not buy source code access).

    2. Re:Access to lib source does not require FOSS ... by perpenso · · Score: 1

      OK fine. It would not be possible if you did not have access to the source code. It is true that you can buy access to the source from some closed source software. But the fact that you are choosing software based on whether you are able to access the source code, I would argue is a point in favor of open source software rather than closed source proprietary software (the vast majority of which you can not buy source code access).

      I never said I was against FOSS. I'm merely pointing out that access to source code is hardly unique to FOSS.

      As far as how common access to source is in proprietary software, I think it is far more common than most FOSS advocates are aware of. For some of what we had used in the past there was no public offering of a source license. Yet when we specifically asked about it a deal was made. Many things that appear set are in fact negotiable. FWIW, we were a small company with no particular leverage.

  195. Re:Proprietary or open seems irrelevant to discove by perpenso · · Score: 1

    Proprietary or open seems irrelevant to this discovery.

    You can't make such conclusions from one bug.

    Good thing I was commenting on only this one bug. That said, one can absolutely make the statement that fuzzing and other penetration testing works equally well on proprietary and FOSS code. The binary being tested doesn't care about the nature of it license.

    Bugs will happen, and bugs will go unnoticed. The question is about whether the open source nature of a piece of software decreases the frequency of those events.

    No one is arguing whether bugs will occur and go unnoticed. What is being argued is that the value of the "many eyeballs" concept is often exaggerated. Few users are developers. Few developers are qualified readers.

  196. Makes FOSS Seem Safer by Anonymous Coward · · Score: 0

    I'm sure the NSA wishes we were using more proprietary tools, however.

  197. Re:Zontar: "Rinse, Lather, & Repeat" (lol) by Zontar+The+Mindless · · Score: 1

    Well, since you asked:

    Currently that's 5 Insightful mods, 1 Overrated, and 1 Troll.

    I start at 1 when logged in, and I get an extra +1 for having excellent Karma.

    What's "Karma", you ask? That's something you don't really need to worry about, since you are too big a coward to create an account and log in to it before posting, and even then, you need to post stuff that people think is useful, informative, insightful, which you don't seem capable of doing, so my advice is not to bother.

    --
    Il n'y a pas de Planet B.
  198. Re:Zontar, lol, COME ON...apk by Zontar+The+Mindless · · Score: 1

    You started your own janitorial service? Congrats.

    --
    Il n'y a pas de Planet B.
  199. Quit running from producing what's asked of you by Anonymous Coward · · Score: 0

    Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Quit running from producing what's asked of you by Anonymous Coward · · Score: 0

      Keep it up apk. You've got that libeler Zontar on the ropes running.

  200. Quit running from producing what's asked for by Anonymous Coward · · Score: 0

    You're a TRUE coward (& libeler): Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

  201. Ready everyone? "See Zontar RUN"... apk by Anonymous Coward · · Score: 0

    Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them?

    NO - now as anyone can see? You're REDUCED to illogical ad hominem attacks instead... - like the lousy useless unskilled TROLL I've proven you truly are... lol!

    ... apk

    1. Re:Ready everyone? "See Zontar RUN"... apk by Zontar+The+Mindless · · Score: 1

      I repeat: All of Slashdot is still waiting for you to show even one time you have ever posted your copypasta spamvert that it's been ON topic.

      You post nothing but spam, trolls, attacks, mischaracterisations, half-truths, and plain old lies.

      When you're called out on it, you resort to crapflooding.

      --
      Il n'y a pas de Planet B.
    2. Re:Ready everyone? "See Zontar RUN"... apk by Anonymous Coward · · Score: 0

      You've been asked to prove your quoted words. Why are you avoiding it? Anyone knows why. You're a libeling troll.

    3. Re:Ready everyone? "See Zontar RUN"... apk by Anonymous Coward · · Score: 0

      You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

  202. Re:Zontar, lol, COME ON...apk by Anonymous Coward · · Score: 0

    A shithole like DemonWare perhaps?

  203. Zontar resorts to ac trolling now? LMAO (run) by Anonymous Coward · · Score: 0

    Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

  204. Thank You, APK! by Zontar+The+Mindless · · Score: 1

    Apparently you've figured out that I don't want or need to post AC in response to your trolls, APK.

    I've been having a field day finding your slimy little trails all over the Internet and exposing you for the lifelong spammer, bully, troll, crapflooder, and liar that you are.

    Why should I not want to receive credit for unearthing all these wonderful facts about yourself that you've been leaving lying about for the last decade or more?

    Besides, it's been giving me something to take my mind off cigarettes--I decided to quit on Monday after being a smoker for 30+ years.

    This is working out really well for me, too--every time a I get a craving for a smoke, I just hit the Google again and find something new to smoke you with, instead. :D

    Or maybe next time I'll switch to Bing and see what they've got on you, as well.

    --
    Il n'y a pas de Planet B.
    1. Re:Thank You, APK! by Anonymous Coward · · Score: 0

      you create sockpuppets http://slashdot.org/comments.p... and you do ac to troll and libel apk

    2. Re:Thank You, APK! by Zontar+The+Mindless · · Score: 1

      APK, you know damn well that TrollingForHostsFiles was created in response to your appalling behaviour.

      You DO realise, don't you, that my posting history that you keep going over backwards and forwards posting troll responses to just makes it easy for anyone to see how you do things like troll a bunch of my posts a week or more after I made them, then you claim that your trolls came two weeks before my posts did!

      Do you actually think people can't read the timestamps on your posts and mine, and easily see that you started this?

      --
      Il n'y a pas de Planet B.
    3. Re:Thank You, APK! by Anonymous Coward · · Score: 0

      I read you had issues. You're proving it. Like what you said makes sockpuppeting ok to do? Clue, it's not.

    4. Re:Thank You, APK! by Anonymous Coward · · Score: 0

      You created a sockpuppet to troll apk after your appalling libel of him since he's confronting you and you run.

    5. Re:Thank You, APK! by Anonymous Coward · · Score: 0

      You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

    6. Re:Thank You, APK! by Zontar+The+Mindless · · Score: 1

      I created a throwaway account purely to mock you, APK, because, for some *weeks* now, you've been surfing my posting history and crapflooding every discussion I post in.

      It has been very obvious from the start that this was exactly what I was doing, and I've made no attempt whatsoever to disguise it. Anyone who cares to do so can check the record for himself and see that I'm telling the truth about this.

      Whereas you keep going round making the same 3 or 4 trolls in response to each of my posts, trying to pretend that these trolls are posted by different people. However, anyone can see that they're all posted by ACs, and that they all re-use your words and links. Thus, you're fooling nobody... except perhaps yourself.

      --
      Il n'y a pas de Planet B.
  205. Zontar *tries* to change the subject? LMAO! by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Zontar *tries* to change the subject? LMAO! by Anonymous Coward · · Score: 0

      Keep it up apk. Zontar the libeler's on the ropes running.

    2. Re:Zontar *tries* to change the subject? LMAO! by Zontar+The+Mindless · · Score: 1

      So you've never been outside the US.

      Have you ever been outside New York State?

      Have you ever even been outside the Syracuse city limits?

      --
      Il n'y a pas de Planet B.
    3. Re:Zontar *tries* to change the subject? LMAO! by Anonymous Coward · · Score: 0

      Have you ever not run like a scared rabbit from answering to what's shown about you by apk?

    4. Re:Zontar *tries* to change the subject? LMAO! by Anonymous Coward · · Score: 0

      You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

  206. Re:Open source was never safer by BasilBrush · · Score: 1

    Safer != Perfect

    But it's not safer. It's less safe.

    It also does not help when you have large commercial institutions RELYING on the source code in a security critical role under constant attack by well-funded adversaries, AND the developers of said open source code are so pitifully underfunded, AND the commercial proprietors that cause said open source library to become a high-value target are only willing to invest in features, and not improvements that would lead to better quality and lesser likelihood of serious bugs.

    And so the excuse making comes.

  207. Get your facts right by Anonymous Coward · · Score: 0

    No, the "for many eyes all bugs are shallow" did not really fail.

    The OpenSSL with TLS heartbeat shipped in November 2013 in most of the major distributions. The bug was found and reported on April 3rd 2014 by Codenomicon, and by a sheer stroke of completely innocent happenstance and magic Google security found out about it and reported it too. The bug was reported and fixed extremely fast, in April 2014.

    No closed source software can pull anything like this off, they usually take a week or two to sync up and to man the project team, sit in meetings, organize an acceptance within the organization, sit in meetings, start investigations, prepare damage controls just in case, calculate fix/no-fix, sit in meetings, implement something, sit in meetings, review the changes, tick the boxes, redo the documentation layouts for new corporate color scheme, sit in meetings, and so forth.

    Yes, the commit was made years ago, but basically very, very few were using it since it wasn't packaged by distributions. There is not a million eyeballs staring at a dev branch of some open source project. The major release branches get users and thus eyeballs.

  208. Re:Open source was never safer by BasilBrush · · Score: 1

    No question the heartbleed thing is a huge and embarassing problem.

    The biggest of the internet era. Only outdone by the Y2K category of bugs.

    And the origins of both are optimisations which are no longer necessary. For Y2K, back in the day saving 2 bytes repeatedly mattered. And for C, back in the day, saving a bounds check mattered. (And on top of that the Open SSL term believed creating their own malloc mattered.) Nowadays none of these optimisations are worth it. They should all be long gone.

    It's everybody's failure that C hasn't been replaced as a systems programming language. It's ought to be a footnote in history by now.

  209. Re:Zontar "eat your words" libelous troll by Anonymous Coward · · Score: 0

    Hahahaha Zontar downmods (sockpuppets) your post to try hide it. Good luck on a +5 post of his he got publicly fried in and all of Zontar's sockpuppets he used to mod up his own posts (and yours down that expose him) like TrollingForHostsFiles http://slashdot.org/comments.p... can't help him now.

  210. You DO have time to RUN from this though by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:You DO have time to RUN from this though by Anonymous Coward · · Score: 0

      Keep it up apk. You've got Zontar the libeler on the ropes. He's almost knocked out trying to change the subject evading proving his words.

  211. Zontar's = "Run, Forrest: RUN!!!" (lmao) by Anonymous Coward · · Score: 0

    Quit running away from producing what's asked of you. Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    That's all.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    You say my program's useless?

    Ok:

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    My program's in usermode. ProcessScheduler is a kernelmode subsystem.

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO, no less!

    (Arstechnica - Where they edit & alter others' posts that knock them out as I did repeatedly showing they are like YOU - mere talkers or writers, no actual programs to their credit, lol)...

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Zontar's = "Run, Forrest: RUN!!!" (lmao) by Anonymous Coward · · Score: 0

      Yeah, well, Zontar's already got about 15 unanswered posts today. Why aren't you ANNHILIHATING HIM. Cat got your tongue? Don't tell us the great APK is ==>> RUNNING AWAY!! <<==

  212. Another troll by ac post lie, Zontar? by Anonymous Coward · · Score: 0

    "Nobody clicks on THE links" - by Anonymous Coward on Tuesday April 15, 2014 @06:52PM (#46762013)

    Now WHAT was that you said Zontar? You clicked on it Zontar.

    APK

    P.S.=> Keep running from this (it's YOUR funeral) -> http://slashdot.org/comments.p...

    1. Re:Another troll by ac post lie, Zontar? by Anonymous Coward · · Score: 0

      I did READ this comment. I am not Zontar - CAN'Tyou tell the style IS completely different? - and I didn't read any of the grandparent posts. And I can assure you i DID not click on any links.

      Seek professional help. I'm confident you KNOW you need it.

      You can refer to me as the "seek help troll" if it helps cement this advice in your brain. You're welcome.

  213. Re:Open source was never safer by Anonymous Coward · · Score: 0

    "One word for you: Microsoft. Maybe two: Adobe."

    I find it interesting that in defending closed source you cited the two worst offenders for security breaches in the tech world. It can be safely assumed that any internet connected product running Microsoft and Adobe products is infected by multiple malware and spyware applications even without the involvement of state run organizations.

  214. Re:Open source was never safer by erroneus · · Score: 1

    One problem I see that is huge is in where it affects Android. It is an unfortunate reality that phone makers do not want to update or patch their phones as they would rather sell people new phones and carriers would rather extend contracts. So yes, perhaps I did understate it a bit.

    There needs to be a push for phone makers to update their firmware NOW.

  215. Zontar = "Run, Forrest: RUN!!!", lmao... apk by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity if my program's useless http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

    1. Re:Zontar = "Run, Forrest: RUN!!!", lmao... apk by Zontar+The+Mindless · · Score: 1

      Posting a link to yet another copy of a falsehood does not make the falsehood true.

      --
      Il n'y a pas de Planet B.
    2. Re:Zontar = "Run, Forrest: RUN!!!", lmao... apk by Anonymous Coward · · Score: 0

      If they're so false then why are you running away from them here http://slashdot.org/comments.p...

    3. Re:Zontar = "Run, Forrest: RUN!!!", lmao... apk by Anonymous Coward · · Score: 0

      Zontar you've just admitted your own quoted words in apk's post are libelous lies you uttered then?

    4. Re:Zontar = "Run, Forrest: RUN!!!", lmao... apk by Anonymous Coward · · Score: 0

      You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

    5. Re:Zontar = "Run, Forrest: RUN!!!", lmao... apk by Zontar+The+Mindless · · Score: 1

      Dude, are you like 12 years old or something?

      --
      Il n'y a pas de Planet B.
    6. Re:Zontar = "Run, Forrest: RUN!!!", lmao... apk by Zontar+The+Mindless · · Score: 1

      You just keep linking to your own posts, as far as I can see.

      You seem to have trouble understanding that linking to a copy of a falsehood does not make the falsehood true.

      --
      Il n'y a pas de Planet B.
  216. Re:Proprietary or open seems irrelevant to discove by Anonymous Coward · · Score: 0

    Um wasn't this bug non-existent in the versions released after this two year old version of openSSL? My 14.04 install didn't get patched, didn't have to, it never had it affected version. Updates people, do your dam updates!

  217. What, a serious bug??? by bbsalem · · Score: 1

    On, NO, they found a serious bug in a FOSS package, Oh NO, the proprietary fanboys are saying that the Sky is Falling! Meanwhile, a fix comes out on the day that the advisory is issued and the patch to the library is on several repositories that day. On April 7, the day of the CERT, Debian had a patch to the openssl livrary.

  218. Zontar - no more ac b.s.: Face the music... apk by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us all a post where I put up material on hosts where it doesn't apply & is OFF TOPIC.

    You can't, obviously, can you? Nope... lol! That makes YOU a lying bullshitter.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    You also said MY program is a virus?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I have destroyed, like I am destroying YOU loser (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler to make his process run faster." - FROM -> http://slashdot.org/comments.p...

    Again: How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Can't get out of your crap now, can you? Nope... same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    Funny:

    You can't seem to explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I am "so bad", why did THAT happen to them? apk

  219. Re:Panglossian Nonsense ---What are you on? by ikhider · · Score: 1

    Have you heard of an old cliche that goes "learn from your mistakes". By your logic, no errors can ever be made and learned from.

    --
    "SO we bide our time, waiting for a purer kick to bloom and the future is still bleak, uncertain and beautiful" -GSYBE
  220. Re:Open source was never safer by Anonymous Coward · · Score: 0

    I just wiped my linux box and installed windows 8.
    Cause, I figured, how much worse could it be?
    Thank God, I won't be wasting my time compiling stuff from "trusted sources anymore.
    Seriously, wtf is that all about anyway?
    Can you imagine how foolish us guys feel after taking this ssl tarball from hell and forcing it in to our system?
    Problem is there are to many freeloaders who will pick stuff right out of your trash as long as it's free.
    I have a much higher sense of self worth since i got rid of this crap.
    True freedom is buying whatever you can afford instead of listening to Stallman for 30 years.
    Even the French prefer windows over Mandarin Linux.
    Mandarin Linux - what's up with that?

  221. Re:Proprietary or open seems irrelevant to discove by Anonymous Coward · · Score: 0

    Um wasn't this bug non-existent in the versions released after this two year old version of openSSL? My 14.04 install didn't get patched, didn't have to, it never had it affected version. Updates people, do your dam updates!

    14.04 pre-releases were vulnerable. Perhaps you are confused because the release version of 14.04 LTS, built days after the fix and to be released tomorrow, is clean.

  222. Re:How would proprietary software have handled thi by Anonymous Coward · · Score: 0

    In the age of contracting, outsourcing, offshoring, etc. most proprietary software is actually pretty exposed..

  223. Re:Open source was never safer by Anonymous Coward · · Score: 0

    Saying Microsoft has better security record is like saying your shit-sandwich has nearly the least shit of any shit-sandwich vendor, but ignore that crazy guy selling sandwiches after washing his hands.

    So, how many consumer desktop/laptop/tablets/phones run a *nix distro that isn't from Google or Apple?

    Have they hit 1% yet? No? There's a reason for that and it's not 'because they're too awesome'.

  224. Hello Zontar sockpuppet - Zontar does this by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk/b

    1. Re:Hello Zontar sockpuppet - Zontar does this by OneAhead · · Score: 1

      Hello Zontar sockpuppet - Zontar does this

      Paranoid delusions - check.

      Show us a post where I put up material on hosts where it doesn't apply.

      All of them. Living in an alternative reality - check.

      I would advice you try to take your meds on time and never skip them. It's really important.

  225. Zontar, backup your libel here then by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  226. Re:Panglossian Nonsense ---What are you on? by Capt.Albatross · · Score: 1

    Have you heard of an old cliche that goes "learn from your mistakes". By your logic, no errors can ever be made and learned from.

    What we have here is a failure to learn from previous mistakes - this bug violates a number of basic principles in the development of secure software, and most of those principles were derived from hard experience.

    I will agree that there is one thing to be learned here: The phrase "with enough eyes, all bugs are shallow" is simplistic wishful thinking, and potentially dangerous if mistaken for a realistic verification policy.

  227. Comment not read by Anonymous Coward · · Score: 0

    I didn't READ the comment. Seek proFESSional help.

    1. Re:Comment not read by Zontar+The+Mindless · · Score: 1

      Apparently in APK's world, all ACs are Zontar and all logged-in Slashdotters are also Zontar.

      Whaddaya think, AC buddy? Should I feel honoured?

      --
      Il n'y a pas de Planet B.
    2. Re:Comment not read by Anonymous Coward · · Score: 0

      Zontar you and you posting ac also said click and read. You fail.

    3. Re:Comment not read by Anonymous Coward · · Score: 0

      You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

  228. Hi everyone! by Anonymous Coward · · Score: 0

    I just wanted to chip in and remind you that the real world do have people who don't engange in opionionated debates and can deduce logic from statements. Cheers! Don't be depressed when people seem stupid, it's just the stupid crowd that talk a lot louder. Hang in there! :)

  229. Replying to myself again by Anonymous Coward · · Score: 0

    I am planning to reveal my slashdot account to him in due course (that's right APK - you're going to get a new, named target soon). For now, I follow the show from a distance and have found a number of your posts to be very entertaining, so thanks for that :)

    -- The Seek Help Troll - advising APK on mental health since 2007

    1. Re:Replying to myself again by Zontar+The+Mindless · · Score: 1

      One plan I was considering for TrollingForHostsFiles was to have him try to convert APK to Buddhism, but I'm still a bit too jittery from nicotine withdrawal to come up with any suitable rhymes.

      He's awfully quiet today--I hope they've not already managed to block him.

      --
      Il n'y a pas de Planet B.
  230. Zontar = "Run, Forrest: RUN!!!" by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

    1. Re:Zontar = "Run, Forrest: RUN!!!" by Zontar+The+Mindless · · Score: 1

      Show us a post where I put up material on hosts where it doesn't apply.

      You can't, can you? Nope - That makes YOU a liar.

      ---

      I have already explained why your crapflooding and spamvertisements are by definition off-topic. It's up to you to show where a single one of them was on-topic and you are never going to do this because it is simply not possible.

      "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

      Don't misattribute that to me, as I wasn't the one who said it. (It's true that I happen to agree with the statement, but that is not the same thing as having said it.) In any case, your objection has already been answered numerous times. The fact that you continue to ignore these responses does not mean they weren't made or that they weren't valid.

      You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

      IF I'm "so bad", why'd THAT happen to 'em? apk

      We are still waiting for some evidence (other than your say-so) that this ever even happened. Until you offer such evidence, nobody is going to believe that it ever did happen anywhere outside your own fevered imagination.

      As for me changing the subject, let's review that bit, shall we?

      APK: "I live on my own since the 80's & have my own spot however, occasionally while travelling worldwide for work I lived TONS of spots in the world (or for play too of course) or between jobs..."
      Zontar: "Name some of the 'spots' where you've lived outside the US, and tell us a little about them."
      APK: [Posts a response with the subject line "Zontar *tries* to change the subject? LMAO!" in which he does not answer Zontar's question.]

      The only conclusion that a reasonable person can make after seeing this is that APK lied about having travelled and lived outside the US.

      --
      Il n'y a pas de Planet B.
    2. Re:Zontar = "Run, Forrest: RUN!!!" by Anonymous Coward · · Score: 0

      You haven't shown us a post of apk's that doesn't apply where it's posted. Reimer and Little are known trolls. This isn't about them. It's about you. Everyone knows about them for decades now online. You agreed with those saying apk turned off the process scheduler (so you're in error alongside them). No changing from that subject is necessary.

  231. Zontar = "Run, Forrest: RUN!!!"... apk by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  232. Quit running Zontar... apk by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk since YOu say my program's "crapware"

  233. Zontar = "Run, Forrest: RUN!!!" by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  234. Zontar = "Run, Forrest: RUN!!!" by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  235. Zontar gets called out & runs (lol)... apk by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  236. Zontar = "Run, Forrest: RUN!!!" by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  237. Zontar the sockpuppeteer runs (face the music) by Anonymous Coward · · Score: 0

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    I disproved that too here WITH PROOF FROM A RELIABLE & REPUTABLE SOURCE IN THE SECURITY COMMUNITY who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    http://slashdot.org/comments.p...

    (Which I always produce from reputable sources, NOT fellow "trolls" whom I destroyed, like I am destroying YOU (see ps below)):

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  238. I read you had mental issues by Anonymous Coward · · Score: 0

    You prove it again, second time. You think it's cool to troll with sockpuppets? Clue, it's not.

  239. Re:Zontar, lol, COME ON...apk by Anonymous Coward · · Score: 0

    You've been called out. I'm waiting for you to explain your quoted libel here http://slashdot.org/comments.p...

  240. Zontar the MIndless must eat his words by Anonymous Coward · · Score: 0

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    Ok: CONTRARY PROOF from a REPUTABLE security community source http://slashdot.org/comments.p... who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  241. Your own words quoted = falsehoods? by Anonymous Coward · · Score: 0

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    Ok: CONTRARY PROOF from a REPUTABLE security community source http://slashdot.org/comments.p... who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    You said by turning up cpu priorities in my program I am turning off the processscheduler?

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  242. Zontar the Mindless' quoted falsehoods by Anonymous Coward · · Score: 0

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    Ok: CONTRARY PROOF from a REPUTABLE security community source http://slashdot.org/comments.p... who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    ---

    "He's effectively turning off the Windows process scheduler" - FROM -> http://slashdot.org/comments.p...

    Question:

    How would the process scheduler be turned off by doing that?

    APK

    P.S.=> Same with using arstechnica as your backers - BIG mistake!

    I annihilated arstechnica, & outside their private playpen where THEY STALKED ME TO @ Windows IT Pro forums http://slashdot.org/comments.p... , no less!

    You can't explain WHY Jeremy Reimer and Jay Little's websites were removed by CrystalTech &/or Shaw CA hosting providers

    IF I'm "so bad", why'd THAT happen to 'em? apk

  243. Zontar: EAT YOUR WORDS (on arseholetechnica) by Anonymous Coward · · Score: 0

    Proof's in Jay Little's OWN WORDS below, quoted, that he never denied & in fact, AFFIRMED!

    PERTINENT QUOTES/EXCERPTS:

    ---

    Jay Little being kicked from CrystalTech.com:

    "I asked Jay Little to run this by Dr. Russinovich in fact, lol, & he never tried it again. He OUTRIGHT RAN, & especially after CrystalTech.com removed his website for libel & death threats directed my way! ******* "IM NOT REMOVING THE CONTENT. I HAVE HOWEVER BEGUN HOSTING MY WEBSITE ELSEWHERE." - jaylittle - March 31, 2005 & "This battle with APK has taken it's toll I am afraid." - 4/2/2005 7:47:38 AM jaylittle @ www.jaylittle.com ******* So did petitiononline.com as well for the same childish 'geek angst' that FATBOY Jay Little (no dick type, you know, an obese monstrosity) tried: Jay, learn a bit out IRQL_LESS_THAN_OR_EQUAL_TO, buffer overruns/underruns" FROM-> http://windowsitpro.com/system...

    AND

    Jeremy Reimer being places on a tracking ticket by his ISP, Shaw of Canada:

    "Thank you for your report. Please advise the sender to cease & desist this unwanted communication w/ you & keep this record. If further messages are received after that, we can investigate this further & we will act accordingly. & Hello Mr. Kowalski, we have added this evidence to Jeremy's tracking ticket... Regards, Acceptable Use Policy Management Team Shaw High-Speed Internet Service Shaw Cablesystems G.P. 2400 - 32nd Avenue N.E. Calgary, Alberta, T2E 9A7" FROM-> http://windowsitpro.com/system...

    ---

    For starters!

    (Which, as anyone can see, Neither Jay Little OR Jeremy Reimer DENY that happened to them - being kicked from their hosting providers for stalking, email harassing, & libeling me on their websites (and other places online)).

    * Want emails from CystalTech, ENom, Shaw too? Just ask & "ye shall receive"... now, "eat your words" yet again, you libelous little scumbag!

    APK

    P.S.=> You FAIL, yet again Zontar the Mindless (libeling troll that you are)... apk

  244. Re:Security is hard. Encryption is even harder. by kriston · · Score: 1

    Or you could start using Mozilla NSS (mod_nss). Not only independently written, it also aggressively protects private keys unlike any version of OpenSSL/SSLeay does.

    --

    Kriston

  245. Zontar the Mindless can't backup his libel by Anonymous Coward · · Score: 0

    "Your hosts file app is SPYWARE, dude." - by Zontar The Mindless (9002) on Wednesday April 09, 2014 @02:43AM (#46702387) FROM -> http://slashdot.org/comments.p...

    You said MY program's a spyware?

    Ok: CONTRARY PROOF from a REPUTABLE security community source http://slashdot.org/comments.p... who hosts my app (malwarebytes hpHosts) which you are FREE TO VERIFY by email if you like as MY proof!

    Now: Is YOUR SOURCE Computer Associates REPUTABLE? See here http://www.bing.com/search?q=c...

    ---

    "for a crapware host files app that nobody in his right mind wants to allow anywhere close to his system" - by Zontar The Mindless (9002) on Wednesday April 16, 2014 @12:24PM (#46769393) FROM -> http://slashdot.org/comments.p...

    You say my program's crapware?

    Disprove 17 points here showing hosts give uses more speed, security, reliability, & anonymity then since YOu say my program's "crapware" http://start64.com/index.php?o...

    ---

    "You barge into discussions with your off-topic hosts file nonsense" - by Zontar The Mindless (9002) on Friday April 11, 2014 @09:51PM (#46731153) FROM -> http://slashdot.org/comments.p...

    Show us a post where I put up material on hosts where it doesn't apply.

    You can't, can you? Nope - That makes YOU a liar.

    APK

    P.S.=> You FAIL, sockpuppeteer troll...

    ... apk