t?
> Martin
> ______
> Please do not alter or disrupt this transmission..Thank You
>
>
>
>
>> Date: Thu, 22 Aug 2013 14:53:55 +0100
>> Subject: Re: Tomcat 7 / Java 7 with TLS 1.2 algorithms
>> From: aterrest...@gmail.com
>> To: us
mcat 7 / Java 7 with TLS 1.2 algorithms
> From: aterrest...@gmail.com
> To: users@tomcat.apache.org
>
> According to RFC 5246 Appendix C (TLS 1.2), there is no SHA384. See :
> http://www.ietf.org/rfc/rfc5246.txt
>
> The JSSE Reference Guide also doesn't talk about th
According to RFC 5246 Appendix C (TLS 1.2), there is no SHA384. See :
http://www.ietf.org/rfc/rfc5246.txt
The JSSE Reference Guide also doesn't talk about this SHA384 as an
implementation requirement. See :
http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#impl
Thi
I've already done that, though as far as I can see that doesn't effect
the digest algorithms (only the encryption options).
- Dennis
On 08/23/2013 12:24 AM, Aurélien Terrestris wrote:
Hello
I suppose you need to run your JVM with the unrestricted policy files (on b=
oth client and server si
what's supposed to happen:
The specified cipher in SSLCipherSuiteSSLCipherSuite is supposed to be enabled
when specified within
SSLCipherSuiteSSLCipherSuite=SHA256/384
to allow the Server to arbitrate the ordering of ciphers(instead of the client)
SSLHonorCipherOrder=true
http://tomcat.a
Hello
I suppose you need to run your JVM with the unrestricted policy files (on b=
oth client and server sides). You have to download them from Oracle website=
for your java version, and replace the old.
These files are :
local_policy.jar
US_export_policy.jar
Regards
2013/8/22 :
> Tomcat 7.0.
