You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I need to support the use case where sender and receiver side are more or less running independently from each other. From what I gather about the Noise protocol so far, this should be possible, as both directions have their own and independent counters. However, I haven't found any methods that would help me do this.
The text was updated successfully, but these errors were encountered:
Hey @piegamesde! That is indeed something I added previously for an early WireGuard experiment using snow, and have not integrated into the API. To be honest, snow hasn't gotten the love it deserves in the last couple years, and is due for a redesign to better support the newer Rust ecosystem (async, etc).
Thanks for the information. I switched to the noise-protocol crate in the meantime as it does expose the CipherState structs.
Usually I'm not a fan of so-called "sans IO" protocol libraries, but in this case the API is so simple to use that I don't think doing explicit IO stuff would be worth the effort.
Hi, I need to support the use case where sender and receiver side are more or less running independently from each other. From what I gather about the Noise protocol so far, this should be possible, as both directions have their own and independent counters. However, I haven't found any methods that would help me do this.
The text was updated successfully, but these errors were encountered: