Feeds

Thanks for nothing, OpenSSL, grumbles stonewalled De Raadt

OpenBSD grump it isn't in the cool kids infosec club

Beginner's guide to SSL certificates

OpenBSD founder Theo De Raadt said OpenSSL maintainers appeared to have intentionally not informed it about dangerous vulnerabilities found in the platform and patched today.

The apparent feud stems from the April break away LibreSSL which was forked after developers found the OpenSSL code base to be unacceptably insecure in the wake of the Heartbleed vulnerability.

LibreSSL would still contain OpenSSL vulnerabilities such as the most recent DTLS invalid fragmentation bug (CVE-2014-0195) and rely on early tip offs to ensure it could build a patch for the day of public disclosure.

That bug was one of six to affect OpenSSL which permitted eavesdropping on encrypted connections and the implanting of malware on vulnerable systems.

Disclosure to LibreSSL did not happen, leading De Raadt to claim it was part of deliberate stone-walling.

"Most other operating system vendors have patches available, but that is because they were (obviously) given a heads up to prepare them over the last few days," De Raadt wrote in a mailing list post.

"Unfortunately I find myself believing reports that the OpenSSL people intentionally asked others for quarantine (of the bug), and went out of their way to ensure this information would not come to OpenBSD and LibreSSL.

"There, I've said it."

From an ethical standpoint, developers did not need to inform those dependent on vulnerable code of any bugs found ahead of public disclosure but must inform all critical players if they chose to do so and not "specifically exclude a part of the community", he said.

His statements were met with some criticism centered on the original decision to fork OpenSSL rather than working with developers to improve its security.

At the time, De Raadt took abundant critism of apparent OpenSSL security checks due to insufficient resources further by stating the platform was "not developed by a responsible team".

The LibreSSL project aimed to substaintially rewrite the OpenSSL codebase. Thousands of lines of "unneeded" code were deleted while individual source files were rewritten in kernel normal form used by BSD operating systems.

It was planned for incorporation into BSD version 5.6 scheduled for release in November. ®

Choosing a cloud hosting partner with confidence

More from The Register

next story
SMASH the Bash bug! Apple and Red Hat scramble for patch batches
'Applying multiple security updates is extremely difficult'
Apple's new iPhone 6 vulnerable to last year's TouchID fingerprint hack
But unsophisticated thieves need not attempt this trick
Hackers thrash Bash Shellshock bug: World races to cover hole
Update your gear now to avoid early attacks hitting the web
Oracle SHELLSHOCKER - data titan lists unpatchables
Database kingpin lists 32 products that can't be patched (yet) as GNU fixes second vuln
Who.is does the Harlem Shake
Blame it on LOLing XSS terroristas
Researchers tell black hats: 'YOU'RE SOOO PREDICTABLE'
Want to register that domain? We're way ahead of you.
Stunned by Shellshock Bash bug? Patch all you can – or be punished
UK data watchdog rolls up its sleeves, polishes truncheon
Ello? ello? ello?: Facebook challenger in DDoS KNOCKOUT
Gets back up again after half an hour though
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Intelligent flash storage arrays
Tegile Intelligent Storage Arrays with IntelliFlash helps IT boost storage utilization and effciency while delivering unmatched storage savings and performance.
Beginner's guide to SSL certificates
De-mystify the technology involved and give you the information you need to make the best decision when considering your online security options.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.