{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibrgym4cv5om2n4brrl7fbjmzyjifje6dihinzwklaw2qebf4whkm",
    "uri": "at://did:plc:uxkrhzvf6obbsoh5nf2gkpj5/app.bsky.feed.post/3mlbimha3tke2"
  },
  "path": "/keeping-tls-1-3-aes-gcm-session-keys-out-of-ram/?utm_source=rss&utm_medium=rss&utm_campaign=keeping-tls-1-3-aes-gcm-session-keys-out-of-ram",
  "publishedAt": "2026-05-07T12:00:55.000Z",
  "site": "https://www.wolfssl.com",
  "tags": [
    "wolfSSL/ wolfCrypt",
    "Uncategorized"
  ],
  "textContent": "Secure Element Offload via Crypto Callbacks in wolfSSL Modern embedded and security-critical systems increasingly rely on Secure Elements, TPMs, and hardware cryptographic accelerators to protect private keys. In wolfSSL, asymmetric keys such as ECC private keys can already reside entirely inside hardware using Crypto Callbacks. Until now, however, TLS 1.3 AES-GCM session keys were still […]",
  "title": "Keeping TLS 1.3 AES-GCM Session Keys Out of RAM"
}