Yes, I think so. I'm not sure if we're going to make a separate issue
for this specifically or handle it as part of a larger session
management improvement we're working on.
--Jamil
On 12/17/2018 11:13 AM, Norman Maurer wrote:
So is what I see something that should be fixed in general ?
Lik
So is what I see something that should be fixed in general ?
Like I said it does not matter if its TLSv1.3 or earlier.
Bye
Norman
> On 12. Dec 2018, at 15:42, Norman Maurer wrote:
>
> Hi Jamil,
>
> This was just noticed during a test which uses TLS1.2.
>
>> On 12. Dec 2018, at 15:35, Jamil
Hi Jamil,
This was just noticed during a test which uses TLS1.2.
> On 12. Dec 2018, at 15:35, Jamil Nimeh wrote:
>
> Hi Norman, the new handshaker does return a new SSLSession object. Part of
> JDK-8212885 fixes the lack of propagation of session values across session
> objects, though that
Hi Norman, the new handshaker does return a new SSLSession object. Part
of JDK-8212885 fixes the lack of propagation of session values across
session objects, though that fix was largely in the context of TLS 1.3.
There is a backport set for it, but it is not yet complete as far as I'm
aware.
