Secret stream state initialization; Continue interrupted upload of encrypted stream; about libsodium_dart_bindings HOT 3 CLOSED

I do appreciate your quick response on that. Even though the use case as described is valid and worth having in mind in the future, we've actually concluded that secretstream isn't for us, so if by any chance I've created some feeling of urgency it's definitely no longer important to me at least.

In the meantime I've received brilliant summary response regarding the streaming ciphers: https://crypto.stackexchange.com/a/106992/70896 which made us pursue other streaming protocol, because of lack of seeking in secretsteam:

it doesn't support random-access decryption because of the nonce XOR

from libsodium_dart_bindings.

This is indeed a use case I have not thought of, but definitely something useful to look in to. The dart stream API makes it somewhat hard to do that. Initializing from a previously saved state is easy, but getting that state is hard.

The main problem is that dart streams, as well as all IO (including HTTP) is asynchronous and thus we cannot wait for individual chunks to be sent before "advancing" the state. I will however think about this a little more and see how it might be integrated into the existing APIs.

Also, while not ideal, you could directly use the C-Bindings, they are exported from the library and allow you direct access to the C API. However, then you have to take care of pointer-management etc. yourself as well, so I'd only recommend that as a last resort.

from libsodium_dart_bindings.

Okay. I think I will still leave this issue open, as it might be relevant for others as well.

from libsodium_dart_bindings.