Live data from Hacker News

Ask HN: Negative OpenSSL sentiments

news.ycombinator.com

11–20 of 52 posts

Re: Ask HN: Negative OpenSSL sentiments

#11
post #7

Couldn't agree more. Heuristic to use when someone is bashing someone else's code: Have you contributed (money, code, docs) to the project? If the answer is no: person lacking skin in the game - irrelevant (even harmful) armchair comment.

I don't think that's very good reasoning.

Bad software is bad software regardless of who has funded it, who has committed code to it, or who has written its documentation.

One does not have to be a contributor to that software in order to analyze it and make a judgment regarding its quality.

Re: Ask HN: Negative OpenSSL sentiments

#12
It sounds to me like the way to solve this problem is to turn OpenSSL into a benevolent for profit company with an actual business model.

Why not give the software away as is current practice but then charge top-dollar to MSFT, Google, et al. for professional consulting? This way they could actually devote real resources to the project and implement some of the obvious process reforms that OP and others are suggesting.

The OpenSSL mission could & would be executed better if it was pursued as a business rather than a hobby. Capitalism doesn't cure all ills, but it might be able to cure this one.

Thoughts? Am I missing something?

Re: Ask HN: Negative OpenSSL sentiments

#13
post #11
post #7

Couldn't agree more. Heuristic to use when someone is bashing someone else's code: Have you contributed (money, code, docs) to the project? If the answer is no: person lacking skin in the game - irrelevant (even harmful) armchair comment.

I don't think that's very good reasoning. Bad software is bad software regardless of who has funded it, who has committed code to it, or who has written its documentation. One does not have to be a contributor to that software in order to analyze it and make a judgment regarding its quality.

But if you continue to use that software then you probably need to be a little self-critical too.

Re: Ask HN: Negative OpenSSL sentiments

#14
post #4

Crypto is complicated and very hard to do well. Hell, any complex software is hard to do well. There will always, always be bugs. While I am pissed off with so much moaning, and do agree they should be better funded, I think it is more the case of sensationalist blogging taking control of the narrative. Rather than "Booo OpenSSL" we should focus on recovering and raising awareness of the projects we all rely on every…

> Crypto is complicated and very hard to do well. Hell, any complex software is hard to do well. There will always, always be bugs.

There will always be bugs, sure, but differences in the engineering approach can result in orders-of-magnitude differences in the frequency of bugs.

For example, see "Some thoughts on security after ten years of qmail 1.0," where the qmail author explained why he thought qmail had a dramatically different security track record than sendmail: http://cr.yp.to/qmail/qmailsec-20071101.pdf

The kind of things he's talking about can't just happen on the level of "more people submitting patches" and "more financial contributions." You need a top-down approach that's designed to produce secure code.

Re: Ask HN: Negative OpenSSL sentiments

#15
post #11
post #7

Couldn't agree more. Heuristic to use when someone is bashing someone else's code: Have you contributed (money, code, docs) to the project? If the answer is no: person lacking skin in the game - irrelevant (even harmful) armchair comment.

I don't think that's very good reasoning. Bad software is bad software regardless of who has funded it, who has committed code to it, or who has written its documentation. One does not have to be a contributor to that software in order to analyze it and make a judgment regarding its quality.

[deleted]

Re: Ask HN: Negative OpenSSL sentiments

#16
post #4

Crypto is complicated and very hard to do well. Hell, any complex software is hard to do well. There will always, always be bugs. While I am pissed off with so much moaning, and do agree they should be better funded, I think it is more the case of sensationalist blogging taking control of the narrative. Rather than "Booo OpenSSL" we should focus on recovering and raising awareness of the projects we all rely on every…

Part of the reason people are annoyed it that this wasn't a complicated "crypto is hard" bug!

It was a stupid, "really? again?" type bug that is typical of low-level badly written C programs and a common cause of security vulnerabilities.

Re: Ask HN: Negative OpenSSL sentiments

#17
"Hardware donations do not come from vendors who use OpenSSH on parts of their stuff. They come from individuals. The hardware vendors who use OpenSSH on all of their products have given us a total of one laptop since we developed OpenSSH five years ago. And asking them for that laptop took a year. That was IBM." - http://www.theage.com.au/articles/2004/10/07/1097089476287.h...

Re: Ask HN: Negative OpenSSL sentiments

#18
post #11
post #7

Couldn't agree more. Heuristic to use when someone is bashing someone else's code: Have you contributed (money, code, docs) to the project? If the answer is no: person lacking skin in the game - irrelevant (even harmful) armchair comment.

I don't think that's very good reasoning. Bad software is bad software regardless of who has funded it, who has committed code to it, or who has written its documentation. One does not have to be a contributor to that software in order to analyze it and make a judgment regarding its quality.

You two are talking about different things.

Analyzing something and making a judgment is fine. But what happens after you do that? If you just file it away, fine. But if you go out and publicly bash somebody with little thought for the circumstances, it makes you look like an asshole, and it is generally, as Oskarth says, and irrelevant and possibly harmful comment.

Open source software is a gift to the world. If somebody does a lot of work to give you something and the first thing out of your mouth is, "This sucks! What's wrong with you for giving me an imperfect gift?" then it comes across as ungrateful. Because it is. Worse, it makes the gift-giver less likely to keep giving.

If you want to offer feedback to an open-source project, first ask yourself, "Am I telling them anything they don't know?" If you think you are, then offer it in a spirit of gratitude and constructive criticism. And think hard about going beyond offering opinions to offering money or labor.

Re: Ask HN: Negative OpenSSL sentiments

#19
post #7

Couldn't agree more. Heuristic to use when someone is bashing someone else's code: Have you contributed (money, code, docs) to the project? If the answer is no: person lacking skin in the game - irrelevant (even harmful) armchair comment.

Did you personally take part in the fighting in WWII? If not, how can you say that Hitler was a bad person?

(Deliberately invoking Godwin, because that's the level of logic I'm responding to :P )

Re: Ask HN: Negative OpenSSL sentiments

#20
I'm with you when you say the hate on the developers (especially voluntary devs) is completely undeserved. What really baffles me about the whole debacle is how it's possible that software so widely used and of this importance is left mostly in the few hands of people who want to contribute. I get it that crypto is hard as hell and especially SSL/TLS requires skilled workers, but what I can't understand is why in all these years nobody stepped up and tried to start a collective effort to either fork the project and start a sweeping refactoring or start a completely new project with better foundations. You may argue that it's grunt work and nobody wants to do it, but if your company relies on this sensitive software is in your interest to put money on the table and pay people to do this kind of work.
Post reply on HN