Botan bindings devlog

ApothecaLabs:

The new memory management library provides allocators, and by providing the allocator as an argument, we can ie specify that we want to use a SecureByteStringAllocator that guarantees cleanup, instead of just using the default ByteStringAllocator which cleans up lazily.

Can/should we add additional constraints to the allocators used in the botan bindings to ensure that it is only used with allocators that are sufficiently secure?

I confess that I haven’t always been able to follow all the details of your reworks.

If you want another use-case for testing, I would be very interested in moving amazonka off of vincenthzverse packages. The current prerequisites in my mind are:

1. (Subjective) Ergonomic DX for the operations amazonka currently needs. IIRC, it’s mostly the hashing stuff in Amazonka.Crypto
2. (Objective) Haskell library binds to an unmodified upstream copy of botan. This seems really important.
3. (Subjective) The bindings are declared stable enough to build upon, and don’t need big research projects that require rebuilding large parts of the bindings.

It sounds like you’re getting close, and I remain interested in following your progress.