Mercurial > hg > orthanc-object-storage
diff NEWS @ 75:ac596874d997
fix client side encryption
author | Alain Mazy <am@osimis.io> |
---|---|
date | Tue, 30 Aug 2022 14:59:58 +0200 |
parents | a25b4140e7e4 |
children | 80792bb9600e |
line wrap: on
line diff
--- a/NEWS Tue Feb 15 06:01:47 2022 +0100 +++ b/NEWS Tue Aug 30 14:59:58 2022 +0200 @@ -1,6 +1,12 @@ -Pending changes in the mainline -=============================== +2022-08-30 - v 2.0.0 +==================== +* AWS, Google & Azure: BREAKING CHANGE with client-side encryption: + Fixed reading the master key. Although the documentation stated that the master key had to be + encoded in Base64, the master key was interpreted as an Hex string. All non hex characters were + ignored and could even end up in a non-deterministic master key (see details in https://groups.google.com/g/orthanc-users/c/FKmq9EuvQkU/m/gbz_bSuwBwAJ). + The plugin v 2.0.0 won't be able to read data encrypted with v 1.3.3. You'll have to start a new Orthanc instance + and transfer all data from old to new Orthanc. * AWS: added the content MD5 in the request when writing. This adds integrity check and enables some feature on AWS side like https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html