19 ms·
LibreSSL: FIPS mode is not coming back
- api 13y agoI did some consulting once for a government lab. FIPS is idiotic. It's primarily protectionism for commercial software vendors from OSS competition, and it does not improve security. If anything it hurts-- it mandates closed-source options that cannot easily be audited, and it slows down the upgrade cycle thus preventing bugs that emerge from being quickly patched.
- niels_olson 13y ago> It's primarily protectionism This. It's also protectionism for government IA managers. And it stymies the hell out of anyone trying to do research on a budget, which often depends on open source (for both review, quality and cost reasons).
- andrewvc 13y agoThe OpenBSD people sure are abrasive, but they deserve a ton of praise for taking on a tough task that no one else was willing to do, and for fixing the damn mess. Between FIPS, the NIST and the OpenSSL foundation it's amazing that crypto even works.
- shawn-furyan 13y agoI've got to say that I like the abrasiveness. The security industry is rife with imposters and pretenders. All of the artifice and bogus claims make it very easy for people, organizations, industries... hell, governments to be misled into devoting huge amounts of resources into propping up what amounts to security theater, which is generally actively harmful. Abrasiveness and a willingness to ruffle the feathers of purveyors of bogus security is a public service.
- danielweber 13y agoThere is hardly a shortage of abrasiveness in the security industry. That said, I find zero things wrong with OpenBSD's work to make LibreSSL. If anyone doesn't like it, I'll offer them their money back.
- higherpurpose 13y ago"Fortunately" (and I don't mean to encourage it), the abrasive people in the crypto community are like that when they tend to be right - and don't want "newbies" to do stupid dangerous mistakes, so their tone comes out a little aggressive by default. But yeah, it could be improved. The community should work together on solving issues the right way.
- _delirium 13y agoFortunately or unfortunately, there are also a reasonable number of abrasive people who tend not to be right, so I'm not sure it's a good marker either way. There's a whole rock-star persona around people who make consulting careers out of trying to position themselves as security badasses, and not all of them are.
- newman314 13y agoI include amongst these, security/network guys that disable ICMP because they read it in a book somewhere. Leads to a lot of facepalming when you are actually trying to get something done.
- ghshephard 13y agoParticularly now that ICMP is actually a requirement for IPv6 networks to actually function.
- jradd 13y agoThis hits too close too home.
- 13y ago
- ballard 13y agoAbrasiveness and being opinionated are mostly orthogonal. I think this is more of a correct opinion (to reduce whale blubber) than intentionally pissing people off.
- ef47d35620c1 13y agoThat's part of the culture. It's nothing personal. Don't take it to heart if what they say offends you.
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- ephemeralgomi 13y agoI know you're trolling, but some people might not, so I thought it might be helpful to point out that they are actually discovering and fixing vulnerabilities. For example, CVE-2010-5298: http://www.tedunangst.com/flak/post/analysis-of-openssl-freelist-reuse http://www.tedunangst.com/flak/post/analysis-of-openssl-free...
- Spooky23 13y agoThis stance is counterproductive in my eyes. Lots of security standards, including state/local government and some healthcare environments require FIPS compliance. FIPS isn't perfect, but screens out low-quality crypto implementations that most organizations lack the expertise to evaluate. Dual_EC and that ilk is obviously a serious problem, but FIPS validation addresses other pertinent problems -- like my doctor's office securing my private data with a more trivially flawed/bogus encryption implementation.
- antocv 13y agoIts one thing to certify a doctor and another to certify software. There are formal proofs for software. FIPS doesnt work with software, it takes 6 months just to pass the process?? What does FIPS mean if after the 6th month another heartbleed is found? FIPS remains but the product is useless.
- danielweber 13y agoAs they said, someone else is perfectly free (it's a BSD license) to use their work to build a libfips.
- x0x0 13y agoNonsense. What would you do if you where the NSA and you've now been repeatedly caught lying, bribing (RSA dual ec), and backdooring (dual ec) security software? At this point, you have a problem: working for the nsa probably taints you in the eyes of many, and nobody (rightly) trust you. But what nation states do have is money and bribery. So you do two things: you attempt to subvert (oh, your brother got busted for dui? We know the judge and can make those charges go away or he can do a dime in state; feeling cooperative now?) developers, and you can do your best to make the code shit and as complex as possible in the hopes that if it's awful enough, somewhere in there is a security issue. Since you can afford to buy as many devs as needed, you can probably find them. I saw the phrase coined on here and unfortunately don't recall the source, but the future of backdoors is probably bugdoors. So Libressl -- rip out shit code, reduce complexity, remove unnecessary algorithms and implementations to further remove complexity -- is the necessary fix. Every option in a program increases net complexity, typically in a factorial manner, and complicates testing. What we need is simple, tested, secure code that handles the minimal use cases for web browsers and web servers. It doesn't need to support dead oses, dead compilers, or the government's wish list of complexity inducing certifications.
- forgottenpass 13y agoThe OpenBSD people sure are abrasive I've said it before, all "opinionated software" is abrasive, the scale is really how much you notice it based on if you like the faces and decisions involved. It'd be non-controversial to the HN crowd, but there are plenty of developers are happy to trash any GPL/share-alike project on the same grounds.
- ternaryoperator 13y ago>all "opinionated software" is abrasive I don't know you, so this is not directed at you. However, this is the kind of line I hear from abrasive people defending their unwillingness to temper what they say. It's perfectly possible to have opinionated software (take JUnit or TeX, for example) that simply performs its task in an opinionated way without its authors belittling competitors or being disrespectful to others whose work doesn't fulfill their view of how things should be.
- personZ 13y agobut they deserve a ton of praise for taking on a tough task that no one else was willing to do There seemed to be some serious momentum behind getting proper resources and financing in place for a real effort that the project deserves, but all of that dissolved when this team started making a lot of sound and fury about their fork of something purportedly "beyond fixing". Aside from several incidents of spite-driven commits that were simply wrong (and dangerous), it is unfortunate that so many people who worked so hard on such an important project are treated so poorly, everyone rushing to condemn the code as was.
- dwc 13y agoI tend to think the reason that support dissolved was that many people, myself included, think OpenBSD will do a better job of responsible maintenance. I have no good reason to think throwing money at OpenSSL would actually improve anything that matters. Much more likely we'd just get more of what we've been getting.
- deleted 13y ago[deleted]
- _pmf_ 13y ago"Fixing" it in a way that guarantees that the changes will not be pulled back into OpenSSL has the following problems: * the fork will lag behind when new features are introduced into OpenSSL * the fork will lag behind when new fixes for OpenSSL are implemented This creates a permanent maintenance burden for the LibreSSL maintainers; sure they have attention now, but in 3 months nobody will give a shit any more.
- rlpb 13y agoUnless the rest of the world switches to using LibreSSL by default, (eg. for security reasons). Then the situation could reverse. Given the state of the OpenSSL codebase, I think this has a greater chance of happening than most other forks.
- _cipher_ 13y ago> "Fixing" it in a way that guarantees that the changes will not be pulled back into OpenSSL has the following problems: > * the fork will lag behind when new features are introduced into OpenSSL > * the fork will lag behind when new fixes for OpenSSL are implemented > This creates a permanent maintenance burden for the LibreSSL maintainers; sure they have attention now, but in 3 months nobody will give a shit any more. So, it's gonna be apache all over again. Where they maintained their own fork, with no security patches applied. Or perhaps like OpenSSH, where a linux user is forced to `./configure && make && make install'. I'm trusting your opinion, after careful reviewing of all your commits. :) /irony off
- ebiester 13y agoFor those who don't know what FIPS mode is (like me): https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/FIPS_Mode_-_an_explanation https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NS...
- endersshadow 13y agoThank you for the primer. Can anybody comment as to why FIPS mode in OpenSSL is considered harmful?
- morrad 13y agoMy understanding is the FIPS requires that the SSL library implements a certain suite of protocols (including the Dual EC DRBG discussed in the linked mailing list post) which have known cryptographic weaknesses.
- DannyBee 13y agoWorse than that, AFAIK, the cheapest way to keep up FIPS certification is essentially to change nothing (except as FIPS requirements change, which is "not really often").
- tptacek 13y agoDoes NSS implement Dual_EC? I don't think so. NSS has a FIPS-compliant mode.
- ctz 13y agoThis is not true. FIPS requires that any 'approved' included crypto algorithm implementations are self-tested, and pass a verification program (just a big bunch of somewhat poorly conceived known answer tests). It also has a list of 'allowed' algorithms, which don't need to be tested but can be offered by a FIPS crypto module. The CSPRNG used for key generation must be of an approved construction, but there are a number of choices ranging from stupid shit nobody sane would choose (Dual EC DRBG) to ones which are trivial variations on hashes, HMAC or block ciphers in OFB or CTR mode. Sadly, it says nothing about the quality or construction of actual entropy sources. Naturally, everything not 'approved' or 'allowed' cannot be offered by a FIPS crypto module. On the plus side, this means vendors can't offer proprietary stupid-shit like LFSR stream ciphers. Unfortunately, the approved and allowed list rarely keeps up with good quality or fixed crypto (you'll not find any eSTREAM finalists, or EdDSA, or deterministic DSA, or curve25519 ECDH, for example). Also, the rules are pretty poorly enforced: you'll still find new FIPS certificates issued for boxes which do TLS < 1.2. This is a lie: MD5 is not allowed or approved, and is a fundamental (if conservatively used) part of the protocol in those versions. Source: I used to make FIPS-approved HSMs. AMA? :)
- SEJeff 13y agoThis basically means libressl can not be used by the US Govt or any contractor working with the US Govt, which is a HUGE number of companies. By proxy, it means that libressl will not make its way into Fedora or RHEL, which also limits the adoption of it a fair bit. Perhaps the solution is to fix FIPS instead of berating the people forced to use it.
- protomyth 13y agoI'm sure Red Hat has the money to pay someone to implement FIPS for their port.
- mburns 13y agoI'm sure they do, too. It isn't that simple.
- protomyth 13y agoWhat isn't simple about Red Hat paying a third-party to write some software and get it certified? Other companies are doing it for themselves, surely Red Hat can find someone qualified.
- mburns 13y agoJust "write some software and get it certified"? Sounds so simple, why doesn't everyone do it? Because it isn't just getting a body of code certified once. Someone has to maintain that specific code and either upstream or backport important changes which require a re-certification, neither of which LibreSSL is interested in helping with.
- danudey 13y agoOnce LibreSSL has reached a point of minimal disruptive change, FIPS support could be re-implemented as a series of third-party patches, which could then be certified as needed. For example, create a fipssl project which is patches to a specific version of LibreSSL; take the result (LibreSSL v1.x + fipssl v1.2 = libfipssl v1.2) and then get that certified. Companies/contractors which need FIPS certification then use libfipssl v1.2. The fipssl maintainers then just have to track LibreSSL changes until their next release, which (for a series of small, maintainable patches) shouldn't be too difficult. The grsecurity project has been doing the same thing with the Linux kernel for years.
- ChuckMcM 13y agoIts a reasonable stance, I expect someone will create libfipsssl for the reason that they can charge money for it. For a while at Sun I suggested that we meet the "OSI Network Standards" requirement by just sending a library with stubs that would close out the link, and if they ever got called email us. The humor didn't seem to reasonate with the Federal Systems people :-)
- ballard 13y agoDefinitely. It'll be expensive commercial open source w/ a subscription and delayed to pass FIPS. And LibreSSL will still be more secure.
- dfa0 13y agoIs openSSH FIPS certified? [seems like an aweful lot of people, including me, trust it regardless]
- ticktocktick 13y agoSo it will be consistent with OpenSSH, also a project of OpenBSD devs.
- ausjke 13y agoworking on a FIPS embedded network product right at the moment, gosh it's a maze to get even started, I'm still going to use the now patched openssl for this, as really, the alternatives are not many, and openssl remains to be the most deployed one in the field. checked NSS but its usage in embedded device is rare, other ssls(ploarssl, matrixssl) may work, but again openssl just wins on the popularity side, in a huge way.
- guyinblackshirt 13y agothat makes sense. probably FIPS-certified firewall vendors such as sonicwall will be the ones affected by this.
- sandGorgon 13y agoIf people really need FIPS mode, somebody will fork again and create libfipssl.com and charge a million bucks for it. And then the ones who need FIPS mode can pay to get it, but they won't pay us. The OpenBSD Foundation will gladly take donations to improve libressl, but some money is just too expensive to accept. Sitting on (or more accurately, under) a million dollars in custom contracts creates what I will charitably call a priority inversion. Donate here - http://www.openbsdfoundation.org/donations.html http://www.openbsdfoundation.org/donations.html
- ninjin 13y agoOr here - https://https.openbsd.org/cgi-bin/donations https://https.openbsd.org/cgi-bin/donations If you, like me, want to use a credit card but live somewhere where PayPal blocks donations (Japan in my case).
- atonse 13y agoJust looking at the wholesale cleanup [1] makes me shudder to think about how tough the code was to maintain in the past. Kudos to the libssl team for injecting some much-needed energy into such a critical library. If only this were available on GitHub, we could more easily browse the code and learn about patterns and anti-patterns in writing secure code. [1] http://freshbsd.org/search?project=openbsd&q=file.name:libssl http://freshbsd.org/search?project=openbsd&q=file.name:libss...
- djcapelis 13y agoIf you want it on GitHub, put it on GitHub. Put it where you'd like.
- gry 13y agoAn unofficial mirror: https://github.com/libressl/libressl https://github.com/libressl/libressl
- ballard 13y agoThis is a dupe because it's already synced to git mirrors of openbsd sources. http://anoncvs.estpak.ee/cgi-bin/cgit/openbsd-src/tree/lib/libssl http://anoncvs.estpak.ee/cgi-bin/cgit/openbsd-src/tree/lib/l... "When I grow up..." Tandem multiplication commit is hilarious.
- metafunctor 13y agoGreat call. Having personally been through the toils of FIPS certifying crypto libraries, I smiled and nodded as I read this post. FIPS is about compliance, not about security. LibreSSL is about security, full stop.
- bitwize 13y agoLol, if WorldTechTribune were still around the headlines would write themselves. "Windows contains military-grade encryption certified by the U.S. government. Linux no longer does. Don't be fooled by the communist Al-Qaeda sympathizers in open-SORES development! Windows is more secure!"
- ballard 13y agoFIPS mode is as my grandfather would say: "eyewash." Something that appears to address something by doesn't. (FIPS mode is a "clipboard audit.")
- ballard 13y agoThis is great news. FIPS mode is as my grandfather would say: "eyewash." Something that appears to address something by checking boxes on a clipboard audit but doesn't provide anything but security theater.
- uuid_to_string 13y agoOpenBSD has to be commended for executing on a simple idea that sadly few developers ever adopt: You can make software more valuable by taking things out.
- rubyfan 13y agoOpenBSD lives their mantra and are unafraid of what the internet comment boards have to say about it. They do what they feel is right and believe others are free to benefit from it or go make your own. The world needs more of this not less. What the world needs less of is people with opinions and inability or unwillingness to take action other than complain about the actions of others.
- CopperWing 13y agoOpenSSL package maintainer for SUSE says openSUSE/SLES will stay with OpenSSL (plus handpicked commits from LibreSSL repo), because of missing FIPS and other questionable commits in LibreSSL. https://plus.google.com/110587864313334050808/posts/R8fkf1A4Md3 https://plus.google.com/110587864313334050808/posts/R8fkf1A4...
- sjs382 13y ago>OpenBSD Foundation will gladly take donations to improve libressl, but some money is just too expensive to accept. claps