Closed kirelagin closed 4 years ago
See Crypto.Mac.Lazy
, Crypto.Mac.Stream
, and crypto-sodium-streamly
.
Let’s restrict the scope of this issue to the NaCl-compatible (unauthenticated) streaming API. https://libsodium.gitbook.io/doc/advanced/stream_ciphers/xsalsa20
So, within the scope of this issues are only two simple functions: Crypto.Stream.create
and Crypto.Stream.xor
. The latter should come with a WARNING in haddock that it is inscure because there is no authentication, and thus should not be used, unless the developer knows exactly what they are doing and will have some other form of authentication of the data.
Actually, let’s make sure we do not expose this dangerous API from crypto-sodium
and only expose it from NaCl
.
Implemented in 35835f9f69116bdfe064725d24ea15f055c12176.
https://nacl.cr.yp.to/stream.html
ByteString
?ListT
?