{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicph4etyobodh2ve3fw27al2tnpmofte3a5k5yc5j2nwjftfebyki",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhezjhjsqnq2"
  },
  "path": "/t/botan-bindings-devlog/6855?page=10#post_198",
  "publishedAt": "2026-03-19T02:42:59.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I have planned for a SecureMemory class that Botan will provide an implementation of that uses `botan_scrub_mem` to ensure that memory erasure is not accidentally elided by the compiler. After that, the most important thing will be masking interruptions and squeezing the laziness out to make sure that the IO actions actually fire. Then using it should be no more difficult than supplying a `SecureByteStringAllocator` instead of a `ByteStringAllocator` (or putting the appropriate `SecureAllocator` constraint on the function if you want to force it)",
  "title": "Botan bindings devlog"
}