Could someone please help review this RFE?
Enhance default JDK providers except SunPKCS11 with signatures using SHA-3
family of digests. SunPKCS11 provider will
be updated separately (JDK-8242332).
This changes covers SUN, SunRsaSign, and SunEC providers. Changes are
straightforward, just add
On Mon, Sep 7, 2020 at 7:54 PM Alan Bateman wrote:
>
> On Mon, 7 Sep 2020 09:44:09 GMT, Philippe Marschall
> wrote:
>
> > Hello, newbie here
> >
> > I picked JDK-8138732 to work on because it has a "starter" label and I
> > believe I understand what to do.
> >
> > - I tried to update the
On 9/9/20 1:16 AM, Anders Rundgren wrote:
I may (surely) be wrong but changing the API to return
NamedParameterSpec should not break any existing code based on the
Oracle provider.
Whether it continues to work when someone is using a specific provider
is not relevant. This is a Java SE API,
> Hello, newbie here
>
> I picked JDK-8138732 to work on because it has a "starter" label and I
> believe I understand what to do.
>
> - I tried to update the copyright year to 2020 in every file.
> - I decided to change `@since` from 9 to 16 since it is a new annotation name
> in a new
On 19/08/2020 22:46, Alkanor Oumbratok wrote:
>
> I may be wrong on both points, and I would be really grateful if
> someone could explain why these 2 CVE have been rated this high
> whereas at first glance there isn't any really exploitable related
> scenario.
The first rule of the OpenJDK
Hi Kim,
> Kim Barrett on Sent: 08 September 2020 20:28
>> On Sep 7, 2020, at 10:56 AM, Eric Liu wrote:
>> I have tested 4 cases for those warnings:
>> a) Without my patch, without asan, gcc-8 and gcc-10 are OK.
>> b) Without my patch, with asan, gcc-8 has warned, gcc-10 is OK.
>> c) With my
