{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicg5qlx47yllkzrftdk2oop4ps5yfkblu6qj3bl45d2usw4hlf37q",
    "uri": "at://did:plc:uxkrhzvf6obbsoh5nf2gkpj5/app.bsky.feed.post/3mlckvmymz442"
  },
  "path": "/migrating-crl-workflows-from-bouncy-castle-to-wolfssl-jni/?utm_source=rss&utm_medium=rss&utm_campaign=migrating-crl-workflows-from-bouncy-castle-to-wolfssl-jni",
  "publishedAt": "2026-05-07T23:00:30.000Z",
  "site": "https://www.wolfssl.com",
  "tags": [
    "wolfSSL JSSE Provider (and JNI wrapper)",
    "Uncategorized"
  ],
  "textContent": "If your Java stack currently uses Bouncy Castle for certificate tooling, moving CRL generation to wolfSSL’s JNI is straightforward once you map the flow correctly. wolfSSL JNI/JSSE uses wolfSSL’s native C crypto/TLS library, so projects can share one crypto implementation across Java and non-Java components. In environments that require validated cryptography, wolfSSL has significant experience […]",
  "title": "Migrating CRL Workflows from Bouncy Castle to wolfSSL JNI"
}