Jack Lloyd e8b4474cb9 Fix handling when attempting to decrypt with a session that isn't found ...

There were two discrepancies between the logic here and the original
logic of libsignal-protocol-java.

First, if the session record had an uninitialized active session, in
Java this would still attempt decryption with the old session states,
but Rust would stop immediately without trying the old states. [I am
not sure if this ever happens but it could possibly occur due to use
of archiveCurrentState]

Secondly, we returned the wrong error condition. We treated lack of a
sender chain as an invalid state (effectively an internal error) but
Java treats it as an invalid message, which makes sense in so far as
it is a message which we are unable to process with the information we
have available. This wrong error type led to an unexpected exception
being thrown in Android.

2021-01-07 14:17:17 -05:00

..

benches

Switch to AGPL 3.0

2020-11-02 17:53:10 -05:00

src

Fix handling when attempting to decrypt with a session that isn't found

2021-01-07 14:17:17 -05:00

tests

Remove SessionState from the Rust API

2021-01-06 12:57:41 -05:00

build.rs

Add SenderCertificate and ServerCertificate

2020-11-19 13:24:29 -05:00

Cargo.toml

SealedSessionCipher encrypt

2020-11-19 13:24:29 -05:00