<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MD5 on</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/tags/md5/</link><description>Recent content in MD5 on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 28 Oct 2025 08:00:00 +0000</lastBuildDate><atom:link href="https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/tags/md5/index.xml" rel="self" type="application/rss+xml"/><item><title>FIPS and Non-Approved Algorithms</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/fips/non-approved-algorithms/</link><pubDate>Tue, 28 Oct 2025 08:00:00 +0000</pubDate><guid>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/fips/non-approved-algorithms/</guid><description>Overview FIPS cryptographic modules implement cryptographically strong protection of data at rest and in transit. NIST&amp;rsquo;s position on this is very clear (source):
Non-validated cryptography is viewed as providing no protection to the information or data — in effect the data would be considered unprotected plaintext. If the agency specifies that the information or data be cryptographically protected, then FIPS 140-2 or FIPS 140-3 is applicable. In essence, if cryptography is required, then it must be validated.</description></item></channel></rss>