https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #13 from Konstantin Kolinko knst.koli...@gmail.com ---
Fixed in Tomcat 6 by r1639415. The fix will be in 6.0.43 onwards.
--
You are receiving this mail because:
You are the assignee for the bug.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #10 from Konstantin Kolinko knst.koli...@gmail.com ---
3. Is it possible to try several names in turn in
SSLContext.getInstance(TLS); such as TLS, TLSv1.1 and TLSv1.2?
Other ideas:
A) Use JSSESocketFactory.defaultProtocol
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #11 from Mark Thomas ma...@apache.org ---
(In reply to Konstantin Kolinko from comment #10)
3. Is it possible to try several names in turn in
SSLContext.getInstance(TLS); such as TLS, TLSv1.1 and TLSv1.2?
Workable but ugly
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #12 from Mark Thomas ma...@apache.org ---
Improved init code applied to 8.0.x for 8.0.15 onwards and to 7.0.x for 7.0.57
onwards.
The original issue has not been addressed in 6.0.x so the improved init code
hasn't been applied
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
Hariharan, R cloakcaval...@gmail.com changed:
What|Removed |Added
CC|
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #7 from Mark Thomas ma...@apache.org ---
Is there a way to get the sslProtocol attribute specified for the connector
in the server.xml? That has the value that should be used to create the
SSLContext.
That is what is used.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
Mark Thomas ma...@apache.org changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #9 from Konstantin Kolinko knst.koli...@gmail.com ---
1. If IllegalArgumentException is thrown from static{} block of a class, is it
fatal for the class or not?
If it were fatal, the static{} block should have try/catch for
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #6 from Hariharan, R cloakcaval...@gmail.com ---
@Mark Thomas: I am able to see the bug fix in 7.0.56.
@Karl Freburger: Can you mail a 64-bit IBM JRE for Windows to
cloakcaval...@gmail.com?
--
You are receiving this mail
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #4 from Richard Watts rwa...@us.ibm.com ---
looking at 7.0.56... it does not look like this made it into that release. Can
someone comment?
--
You are receiving this mail because:
You are the assignee for the bug.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
Karl Freburger karl.frebur...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
Mark Thomas ma...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #2 from Karl Freburger karl.frebur...@gmail.com ---
If the IBM JVM is configured for strict SP800-131a mode, the only acceptable
value (currently) for the protocol would be TLSv1.2. If strict SP800-131a
mode is NOT on, many
https://issues.apache.org/bugzilla/show_bug.cgi?id=56780
--- Comment #1 from Mark Thomas ma...@apache.org ---
What value(s) will the IBM JRE accept there?
As an aside, if you can provide a IBM JRE for Windows to test with (preferably
64-bit) to ma...@apache.org that would be great.
--
You are
14 matches
Mail list logo
