Affects Version/s: None
Fix Version/s: 2.0.0-M5
Currently, EncryptionType are stored in a Set, and we compare the expected ETypes passed by the client with the configured ETypes we support in the server. They are both stored in a Set, which is not ordered.
The problem is that there is nothing like a EType negotiation between the client and the server, so the encrypted data will be encrypted using the strongest Etype found in the list of Etypes, where the leftmost EType is the strongest, and the rightmost is the weaker.
Using a set is then a guarantee that we will face issues at some point. We must use a List instead.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||Emmanuel Lecharny [ elecharny ]|
|Fix Version/s||2.0.0-M5 [ 12319541 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1d 5h 40m||1||Emmanuel Lecharny||27/Jan/12 00:44|