It used to be, but cryptonite has been unmaintained for a couple of years now and that's somewhat bad for a security-related package.
On Fri, 6 Mar 2026, Viktor Dukhovni wrote:
> Bottom line, the two variants of `mlkem` don't end up offering the same
> API (distinct type signatures, that only look the same).
Isn't this exactly what Backpack modules are for? If `mlkem` and `tls`
imported a signature for `crypton`/`cryptonite`, depending on either of
these should have `mlkem` and `tls` use the correct version of the API.
I'm not sure what to make of "somewhat experimental", though:
https://cabal.readthedocs.io/en/stable/how-to-use-backpack.html
It may already have been considered, but wouldn't making `tls` compatible
with `cryptonite` solve the issue, too?
_______________________________________________
Haskell-Cafe mailing list -- haskell-cafe@haskell.org
To (un)subscribe, modify options or view archives go to:
Only members subscribed via the mailman list are allowed to post.
--