{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiacijt255yd7rhb6wxpyyhk22k6iffdiilanz7cfluikmpjatreey",
    "uri": "at://did:plc:uxkrhzvf6obbsoh5nf2gkpj5/app.bsky.feed.post/3mp63o24727d2"
  },
  "path": "/fips-with-statically-linked-wolfssl/?utm_source=rss&utm_medium=rss&utm_campaign=fips-with-statically-linked-wolfssl",
  "publishedAt": "2026-06-25T15:00:22.000Z",
  "site": "https://www.wolfssl.com",
  "tags": [
    "wolfCrypt FIPS",
    "Uncategorized"
  ],
  "textContent": "Many FIPS deployments of wolfSSL’s FIPS 140-3 validated wolfCrypt module use dynamic linking to load the shared object / DLL. However, sometimes it is necessary for some types of projects to statically link the libwolfssl.a static archive directly into an executable or firmware image. This post explains why static linking takes a little extra care, […]",
  "title": "FIPS with Statically-Linked wolfSSL"
}