<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TLS on</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/tags/tls/</link><description>Recent content in TLS on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Sat, 15 Nov 2025 08:49:31 +0000</lastBuildDate><atom:link href="https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>Chainguard FIPS TLS Connectivity Requirements</title><link>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/fips/tls-requirements/</link><pubDate>Sat, 15 Nov 2025 08:49:31 +0000</pubDate><guid>https://deploy-preview-3175--ornate-narwhal-088216.netlify.app/chainguard/fips/tls-requirements/</guid><description>This document provides an overview of FIPS TLS connectivity requirements for using Chainguard FIPS products. These FIPS products have higher minimum TLS requirements, which complicates connecting them to insecure EOL non-FIPS systems, as well as FIPS systems with lapsed (historical) certification.
Chainguard strives to ensure the broadest connectivity possible for its FIPS products. However, many obsolete systems are still widely used and may not be able to connect with Chainguard FIPS products.</description></item></channel></rss>