4 ms·
> It is really difficult to refactor such things at the public API layer once they are widely adopted by 3rd party projects. But how did it ever get so widely
by mcv 13y ago
> It is really difficult to refactor such things at the public API layer once they are widely adopted by 3rd party projects.
But how did it ever get so widely adopted, if it's so hard to use?
And even if it is widely adopted, that still shouldn't stop anyone from forking it and fixing all the problems.
- tinco 13y agoSo why didn't you?
- mcv 13y agoIt's not something I work on. But clearly a lot of other people do. And I have some trouble believing that all those people building stuff on top of OpenSSL don't care about security. Look, if this was about something fairly inconsequential, like a library for a game or a blog or something, sure, use some badly maintained, badly documented, inconsistent library. But when you care enough about security to use SSL, surely you care enough to use something that's put together in such a way that you can be sure it does what you think it does? Bad documentation and inconsistent error handling in a security package sound like an unbelievably dangerous idea. And if it's really an unmaintainable mess, like everybody says, then how can bugs possibly be fixed? How easy would it be for the NSA to insert some crucial vulnerability into the code base? Security, moreso than anything else in computer science, needs to be clear, transparent, understandable, well documented and well maintained. If it's not, mistakes will be made and security will be compromised.
- tinco 13y agoWhy do you not include yourself in the list of people that work on it? Who are these other people that should be working on it? There's only 2 people on the OpenSSL team apparently.
- andyjohnson0 13y ago"But how did it ever get so widely adopted, if it's so hard to use?" Usefulness and lack of alternatives?