cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cohei...@apache.org
Subject [2/2] git commit: Fixing merge
Date Mon, 14 Jul 2014 16:17:31 GMT
Fixing merge


Project: http://git-wip-us.apache.org/repos/asf/cxf/repo
Commit: http://git-wip-us.apache.org/repos/asf/cxf/commit/a63f8352
Tree: http://git-wip-us.apache.org/repos/asf/cxf/tree/a63f8352
Diff: http://git-wip-us.apache.org/repos/asf/cxf/diff/a63f8352

Branch: refs/heads/2.6.x-fixes
Commit: a63f8352a6c660b248aec5316a6a987c428862a3
Parents: 5b9d08c
Author: Colm O hEigeartaigh <coheigea@apache.org>
Authored: Mon Jul 14 17:17:19 2014 +0100
Committer: Colm O hEigeartaigh <coheigea@apache.org>
Committed: Mon Jul 14 17:17:19 2014 +0100

----------------------------------------------------------------------
 distribution/src/main/release/release_notes.txt | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cxf/blob/a63f8352/distribution/src/main/release/release_notes.txt
----------------------------------------------------------------------
diff --git a/distribution/src/main/release/release_notes.txt b/distribution/src/main/release/release_notes.txt
index 8c97995..f669512 100644
--- a/distribution/src/main/release/release_notes.txt
+++ b/distribution/src/main/release/release_notes.txt
@@ -47,7 +47,7 @@ with the specified versions, are installed on your system:
     * Apache Maven 2.2.1 or 3.x to build the samples
 
 
-3.  Integrating CXF Into You Application
+3.  Integrating CXF Into Your Application
 
 If you use Maven to build your application, you need merely add
 appropriate dependencies. See the pom.xml files in the samples.
@@ -106,3 +106,13 @@ for caveats when upgrading from CXF 2.5.x to 2.6.x.
 
 ** Task
     * [CXF-5565] - update to opensaml 2.6.1
+
+8. Known issues
+
+If you are using AES encryption with GCM for symmetric encryption in
+XML/WS-Security, there is a problem if you are using BouncyCastle < 1.49 or
+1.50. To circumvent this either of the following steps can be taken:
+
+a) Upgrade to BouncyCastle 1.49 (or 1.51 when it gets released) OR
+b) Set the system property "org.apache.xml.security.cipher.gcm.useIvParameterSpec" to "true".
+


Mime
View raw message