e?
>
> David
>
> -Original Message-
> From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> Sent: Monday, November 03, 2014 11:22 AM
> To: users@cxf.apache.org
> Subject: Re: Mitigations for POODLE vulnerability
>
> I'm not sure if there is a way to exclude it us
t in the CXF client at the next release?
>
> David
>
> -Original Message-
> From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> Sent: Monday, November 03, 2014 11:22 AM
> To: users@cxf.apache.org
> Subject: Re: Mitigations for POODLE vulnerability
>
> I
at the next release?
>
> David
>
> -Original Message-
> From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> Sent: Monday, November 03, 2014 11:22 AM
> To: users@cxf.apache.org
> Subject: Re: Mitigations for POODLE vulnerability
>
> I'm not sure if the
Will it also be disabled by default in the CXF client at the next release?
David
-Original Message-
From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
Sent: Monday, November 03, 2014 11:22 AM
To: users@cxf.apache.org
Subject: Re: Mitigations for POODLE vulnerability
I'm not su
context:
http://cxf.547215.n5.nabble.com/Mitigations-for-POODLE-vulnerability-tp5750618p5750620.html
Sent from the cxf-user mailing list archive at Nabble.com.
required="false" />
> ${https.certAlias}
>
> minThreads="${webservice.minThreads}"
> maxThreads="${webservice.maxThreads}" />
>
>
>
> Is there a way to m
.*_DH_anon_.*
${https.certAlias}
Is there a way to modify the configuration above to exclude all use of
SSLv3?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Mitigations-for-POODLE-vulnerability-tp5750618.html
Se
