You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2020/06/04 12:19:38 UTC
[Bug 64497] New: jni.SSL.getSessionId returns null
https://bz.apache.org/bugzilla/show_bug.cgi?id=64497
Bug ID: 64497
Summary: jni.SSL.getSessionId returns null
Product: Tomcat Native
Version: 1.2.23
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Library
Assignee: dev@tomcat.apache.org
Reporter: remm@apache.org
Target Milestone: ---
This can be reproduced using the following Tomcat test and OpenSSL using the
build.properties:
test.entry=org.apache.catalina.valves.rewrite.TestResolverSSL
test.sslImplementation=org.apache.tomcat.util.net.openssl.OpenSSLImplementation
In the log, "[SSL_SESSION_ID] null", while many other fields work fine.
jni.SSL.getSessionId simply returns null, so no SSL session id.
With JSSE, the SSL session id is there.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 64497] jni.SSL.getSessionId returns null
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=64497
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
It was part of the big patch from netty ~5 years ago. It isn't mentioned
explicitly so I am guessing session caching was disabled by default because it
isn't needed when RFC 5077 session tickets are available.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 64497] jni.SSL.getSessionId returns null
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=64497
--- Comment #2 from Mark Thomas <ma...@apache.org> ---
Turns out setting the session cache size was exposed and setting that
automatically sets the mode correctly. The session ID is now available to the
rewrite valve.
I still want to check on why the tomcat-native default is to disable this.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 64497] jni.SSL.getSessionId returns null
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=64497
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
The root cause of this behaviour is the session caching is hard-coded to
disabled in sslcontext.c
That is a different default to OpenSSL. Some svn archaeology is called for to
figure out why this was chosen as the default.
As a minimum, we need to expose the session cache mode and session cache size
to the TLS connector. That is mostly going to be Tomcat code but I'll track it
here for now.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org