libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From to...@apache.org
Subject [libcloud] 02/03: Add changelog entry.
Date Fri, 22 Jan 2021 18:34:16 GMT
This is an automated email from the ASF dual-hosted git repository.

tomaz pushed a commit to branch ec2_regression_signature_version_fix
in repository https://gitbox.apache.org/repos/asf/libcloud.git

commit f8f2f8f6109226317d3937fd8d04ac6e91fa56a5
Author: Tomaz Muraus <tomaz@tomaz.me>
AuthorDate: Fri Jan 22 17:04:37 2021 +0100

    Add changelog entry.
---
 CHANGES.rst | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/CHANGES.rst b/CHANGES.rst
index 5e8537e..8121e53 100644
--- a/CHANGES.rst
+++ b/CHANGES.rst
@@ -1,6 +1,36 @@
 ´╗┐Changelog
 =========
 
+Changes in Apache Libcloud in development
+-----------------------------------------
+
+Compute
+~~~~~~~
+
+- [EC2] Fix a regression introduced in v3.3.0 which would break EC2 driver for
+  some regions because the driver would incorrectly try to use signature version
+  2 for all the regions whereas some newer regions require signature version 4
+  to be used.
+
+  If you are unable to upgrade, you can use the following workaround, as long
+  as you only use code which supports / works with authentication signature
+  algorithm version 4:
+
+  .. sourcecode:: python
+
+    import libcloud.common.aws
+    libcloud.common.aws.DEFAULT_SIGNATURE_VERSION = "4"
+
+    # Instantiate affected driver here...
+
+  Reported by @olegrtecno.
+  (GITHUB-1545, GITHUB-1546)
+
+- [EC2] Allow user to override which signature algorithm version is used for
+  authentication by passing ``signature_version`` keyword argument to the EC2
+  driver constructor.
+  (GITHUB-1546)
+
 Changes in Apache Libcloud 3.3.0
 --------------------------------
 


Mime
View raw message