# A new future for cryptography in Haskell

**URL:** <https://discourse.haskell.org/t/a-new-future-for-cryptography-in-haskell/3888>\
**Category:** Announcements\
**Created:** [January 9, 2022, 1:49pm UTC](https://discourse.haskell.org/t/a-new-future-for-cryptography-in-haskell/3888 "2022-01-09T13:49:28Z")\
**Posts on this page:** 1\
**Showing post:** 80

<div class="post-metadata">

**Author:** ![ApothecaLabs](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/apothecalabs/32/3215_2.png) [@ApothecaLabs](https://discourse.haskell.org/u/ApothecaLabs)\
**Post date:** [July 3, 2023, 2:37pm UTC](https://discourse.haskell.org/t/a-new-future-for-cryptography-in-haskell/3888/80 "2023-07-03T14:37:21Z")

</div>

> [@arybczak](#):
>
> So “someone” would need to fork it, rip out the `Z-IO` and `Z-Data` bits and replace them with the standard deps like `bytestring` etc. I don’t know how much work that would be. I would attempt this, but my time budget for OSS has run out ☹

I took a brief look, and on the surface it doesn’t look _too bad_ - a lot of the changes would need to occur in `Z.Botan.FFI` but aside from a few things like the `CBytes` type, most of the Z-stuff used here appears to be a lot of type-aliases and re-exports.

More concerning is the issue that it relies on an [out of date fork of botan](https://github.com/ZHaskell/botan) pulled in via git submodule using a `Custom` build-type script - it is 3 years out of date, and would need to be replaced with a maintained dependency.

I may not be the best candidate for the job, but I have written my own bindings to `libsodium` before, back before `cryptonite` existed (and `saltine` didn’t provide the APIs I needed), so if time permits, I may give it a go. No promises though 🙂

---

_[View the full topic](https://discourse.haskell.org/t/a-new-future-for-cryptography-in-haskell/3888)._