[noise] Generic fallback handling

alex at centromere.net alex at centromere.net
Sat May 28 10:05:43 PDT 2016

On 2016-05-26 01:44, Rhys Weatherley wrote:
> This API doesn't provide a complete implementation of Noise Pipes - it
> only provides a primitive to make the application's life easier.
> There are still the issues of packet types and framing for the
> application to deal with.

In your estimation, can all Noise Pipes be provided completely on the
application level, with API support just being a convenience wrapper?

> The other approach is pre-message analysis: look at the arguments and
> pre-messages for the new pattern.  Clear any key that is no longer
> required, and check that required keys are already present in the
> HandshakeState.  Each requirement is dealt with separately with a
> keep/clear decision for each.

"the new pattern" -- what if, after your analysis is complete, that
there are multiple valid patterns from which to choose?


More information about the Noise mailing list