From 4809109ff8c647e4fa7d3dbff89c989dda613e85 Mon Sep 17 00:00:00 2001
From: Thomas Tendyck <tt@edgeless.systems>
Date: Mon, 16 Feb 2026 13:23:47 +0100
Subject: [PATCH] docs: add fips usage to build workflow

---
 docs/docs/workflows/build.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/docs/workflows/build.md b/docs/docs/workflows/build.md
index f0053de..f152949 100644
--- a/docs/docs/workflows/build.md
+++ b/docs/docs/workflows/build.md
@@ -25,3 +25,16 @@ ego run <executable>
 You can set the `OE_SIMULATION=1` environment variable if you want to simulate the enclave, e.g. for development on hardware that doesn't support enclaves.
 
 Look at the [example collection](../getting-started/examples.md) if you want to see the build process in action.
+
+## FIPS 140 cryptography
+
+EGo optionally supports FIPS 140-compliant cryptography.
+
+Build your app with the Go FIPS 140 module enabled:
+
+```bash
+GOFIPS140=latest ego-go build
+```
+
+Then sign and run as usual.
+EGo automatically uses the corresponding FIPS 140-enabled runtime.