3 ms·
There are situations where you want to be able to say you're using a FIPS certified crypto library, but that you're not going to get the whole thing certified.
by Nursie 8y ago
There are situations where you want to be able to say you're using a FIPS certified crypto library, but that you're not going to get the whole thing certified.
I went through that with an IBM product I was working on years ago. It involved taking out any crypto implementations already in the code (I believe we had a reference DES implementation doing something with passwords) and switching to FIPS certified TLS libs. At the end we got to say we were FIPS compliant (NOT certified), which was important for some government contract or other.
- windexh8er 8y agoAlso interesting is that the PCI SSC is now recommending FIPS 140-2. While not likely relevant to the decision in Alpine, it may be relevant downstream with regard to choosing Alpine to develop on. PCI Standards Security Council - Secure Software Standards v1.0 (Jan 2019) https://www.pcisecuritystandards.org/document_library?category=sware_sec#results https://www.pcisecuritystandards.org/document_library?catego...
- Nursie 8y agoOh interesting. That said I've only ever taken devices through PCI-PTS, not worked on PCI compliant software so I have no idea how much of a departure this is from common practice. The one thing that would concern me about widespread adoption of FIPS-certified tech is that (IIRC) FIPS 140-2 essentially forbids PFS modes (DH/DHE) on TLS, presumably for traffic audit purposes in secure government environments.