SignedSessionDecrypter and Encrypter currently encrypt json AesKey data which
is wasteful size wise, and should use a binary format such as ProtoBuf or BSON.
They also should sign the SessionMaterial too instead of just signing the
ciphertext.
For future proofing the SessionMaterial should have the ablity to support
different symmetric key types as well.
These changes would likely require a new ciphertext version number change.
Original issue reported on code.google.com by jtu...@gmail.com on 29 Jan 2013 at 5:41
Original issue reported on code.google.com by
jtu...@gmail.com
on 29 Jan 2013 at 5:41