Just checking - does this look like a genuine issue? Anything else I can
provide to help reproduce this?
-Jaikiran
On 18/09/18 7:06 PM, Jaikiran Pai wrote:
> I have been testing some projects that I know of, with Java 11 RC.
> There's one specific test that has been failing for me, for a while n
Hi Jaikiran,
Does it happen if using JDK crypto provider?
Thanks,
Xuelei
On 9/20/2018 6:16 AM, Jaikiran Pai wrote:
Just checking - does this look like a genuine issue? Anything else I can
provide to help reproduce this?
-Jaikiran
On 18/09/18 7:06 PM, Jaikiran Pai wrote:
I have been testing
Hello Xuelei,
It doesn't happen if both the server side and client side use the JDK
crypto provider. However if any one side uses a different crypto
provider (bouncycastle in this case) then it throws this exception.
-Jaikiran
On 20/09/18 8:37 PM, Xuelei Fan wrote:
> Hi Jaikiran,
>
> Does it ha
Thanks for the quick reply, Jaikiran!
Per your diff code, it sounds like a crypto provider implementation
bugs. JDK is using a lazy initialization so that the right provider get
used. Third party's provider may not do this way. Would you please
help to verify if the parameters get used in
Sure, I'll run some tests tomorrow and get more details on whether/how
bouncycastle uses these parameters if they are set after the init
verify/sign calls.
-Jaikiran
On 20/09/18 9:05 PM, Xuelei Fan wrote:
> Thanks for the quick reply, Jaikiran!
>
> Per your diff code, it sounds like a crypto pro
Just to followup on your (Norman's) earlier question:
On 9/19/2018, Norman wrote:
>> Is this just the
>> initial version set or do you not plan to fix it in Java11 ?
and
On 9/19/2018 9:34 AM, Xuelei Fan wrote:
> It is just a initial version set.
Getting this fix into JDK 12 was easy as 12 is i
Got it... just keep in mind that this bug make it kind of unusable on the
client-side so I think it should be a high priority to fix it rather sooner
then later. Especially as the fix is really a one line change
Norman
> Am 20.09.2018 um 11:30 schrieb Bradford Wetmore :
>
> Just to followup on
Hi,
Please review this simple fix for SunJSSE debug log:
http://cr.openjdk.java.net/~xuelei/8210974/webrev.00/
The debug log for ClientHello message does not appear in JDK 12.
Trivial update, no new regression test.
Thanks,
Xuelei
Looks good.
On 9/20/2018 1:02 PM, Xuelei Fan wrote:
Hi,
Please review this simple fix for SunJSSE debug log:
http://cr.openjdk.java.net/~xuelei/8210974/webrev.00/
The debug log for ClientHello message does not appear in JDK 12.
Trivial update, no new regression test.
Thanks,
Xuelei
Ditto.
Brad
On 9/20/2018 1:03 PM, Jamil Nimeh wrote:
Looks good.
On 9/20/2018 1:02 PM, Xuelei Fan wrote:
Hi,
Please review this simple fix for SunJSSE debug log:
http://cr.openjdk.java.net/~xuelei/8210974/webrev.00/
The debug log for ClientHello message does not appear in JDK 12.
Trivia
Hello all,
This review is for a backport of 3 TLS interoperability issues that have
come up over the past week or so. These are already in jdk/jdk. They
cover the following issues:
* An NPE thrown during processing of the supported groups extension
with curves not enabled by default
*
11 matches
Mail list logo
