From d020de4b3d9d5b13e7a8cc8906d46859d5f0766e Mon Sep 17 00:00:00 2001 From: Ryan Richard Date: Fri, 1 Nov 2024 12:54:49 -0700 Subject: [PATCH] update fips reference doc --- site/content/docs/reference/fips.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/site/content/docs/reference/fips.md b/site/content/docs/reference/fips.md index e3391b182..a10a3db2a 100644 --- a/site/content/docs/reference/fips.md +++ b/site/content/docs/reference/fips.md @@ -13,15 +13,14 @@ By default, the Pinniped supervisor and concierge use ciphers that are not supported by FIPS 140-2. If you are deploying Pinniped in an environment with FIPS compliance requirements, you will have to build the binaries yourself using the `fips_strict` build tag and Golang's -`go-boringcrypto` fork. +`GOEXPERIMENT=boringcrypto` compiler option. The Pinniped team provides an [example Dockerfile](https://github.com/vmware-tanzu/pinniped/blob/main/hack/Dockerfile_fips) demonstrating how you can build Pinniped images in a FIPS compatible way. -However, we do not provide official support for FIPS configuration, and we may not -respond to GitHub issues opened related to FIPS support. +However, we do not provide official support for FIPS configuration. We provide this for informational purposes only. -To build Pinniped use our example fips Dockerfile, you can run: +To build Pinniped use our example FIPS Dockerfile, you can run: ```bash $ git clone git@github.com:vmware-tanzu/pinniped.git $ cd pinniped