This is an automated email from the ASF dual-hosted git repository. coheigea pushed a commit to branch camel-2.23.x in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1dcd6cbecafe1732a978210d70f733b7897ebd33 Author: Colm O hEigeartaigh <[email protected]> AuthorDate: Wed Jan 9 12:50:42 2019 +0000 Fixing javadoc links --- .../apache/camel/component/crypto/cms/crypt/RecipientInfo.java | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/components/camel-crypto-cms/src/main/java/org/apache/camel/component/crypto/cms/crypt/RecipientInfo.java b/components/camel-crypto-cms/src/main/java/org/apache/camel/component/crypto/cms/crypt/RecipientInfo.java index 06110a4..5fc4fb5 100644 --- a/components/camel-crypto-cms/src/main/java/org/apache/camel/component/crypto/cms/crypt/RecipientInfo.java +++ b/components/camel-crypto-cms/src/main/java/org/apache/camel/component/crypto/cms/crypt/RecipientInfo.java @@ -39,9 +39,11 @@ package org.apache.camel.component.crypto.cms.crypt; * <li>password based encryption: the content-encryption key is encrypted with * key-encryption key derived from a password. The RecipientInfo is using a key * derivation algorithm like PBKDF2 as specified by <a href = - * http://www.ietf.org/rfc/rfc2898.txt"; target="_blank">RFC 2898</a> (PKCS#5) - * and a key encryption algorithm like PWRI-KEK as specified by <a href = - * http://www.ietf.org/rfc/rfc3211.txt"; target="_blank">RFC 3211</a>. + * "http://www.ietf.org/rfc/rfc2898.txt"; target="_blank" + * rel="noopener noreferrer">RFC 2898</a> (PKCS#5) and a key encryption + * algorithm like PWRI-KEK as specified by <a href = + * "http://www.ietf.org/rfc/rfc3211.txt"; target="_blank" + * rel="noopener noreferrer">RFC 3211</a>. * <li>any other technique: based on private, user defined key management * techniques * </ul>
