Adam
Petcher
Sent: Wednesday, December 6, 2017 8:38:35 PM
To: security-dev@openjdk.java.net
Subject: Re: Support for ECParameters with explicit (not named) parameter spec
On 12/6/2017 11:39 AM, Max Fichtelmann wrote:
We use a HSM to generate ECDSA Keys and are required to use the curve
On 12/6/2017 11:39 AM, Max Fichtelmann wrote:
We use a HSM to generate ECDSA Keys and are required to use the curve
brainpoolP256r1.
Although the HSM does not specifically support brainpool, it is
possible to generate these keys by providing the specific Curve
Parameters. These curve paramet
Betreff:Re: Support for ECParameters with explicit (not named)
parameter spec
On 12/6/2017 4:24 AM, Max Fichtelmann wrote:
> Hello,
>
> currently sun.security.util.ECParameters.engineInit(byte[]) is limited
> to parse named curves. A commented block outlining parsing
On 12/6/2017 4:24 AM, Max Fichtelmann wrote:
Hello,
currently sun.security.util.ECParameters.engineInit(byte[]) is limited
to parse named curves. A commented block outlining parsing of explicit
parameters is included below throwing "only named ECParameters
supported". That comment block seems
On 12/6/2017 7:24 AM, Max Fichtelmann wrote:
Hello,
currently sun.security.util.ECParameters.engineInit(byte[]) is limited
to parse named curves. A commented block outlining parsing of explicit
parameters is included below throwing "only named ECParameters
supported". That comment block seem
Hello,
currently sun.security.util.ECParameters.engineInit(byte[]) is limited to
parse named curves. A commented block outlining parsing of explicit
parameters is included below throwing "only named ECParameters supported".
That comment block seems to be unchanged from at least jdk6 up until
j
