On 8/10/2017 12:25 PM, Michael StJohns wrote:
On 8/10/2017 9:44 AM, Adam Petcher wrote:
Does anyone know of a particular use case (that we haven't discuss
already) that would require a provider to support arbitrary curves?
Any other arguments for or against this feature?
There are uses for
Changes look good to me, although I'm not an HTML expert nor an expert
in our current documentation style. I did compare the output, and can
see the effects. (Striped, scope (row vs col), style)
Brad
On 8/11/2017 5:01 PM, Jonathan Gibbons wrote:
Please review the following small fix for
Brad,
Thanks. I should have noted that the issues were detected by checking tools,
and that after the edits, no such issues were reported in this package.
FWIW, there is one remaining issue to be addressed: it is a broken link
in Provider.html.
It comes from Provider.replace(Object, Object,
Please review the following small fix for some accessibility issues in
the java.security package.
3 tables are converted to the de-facto JDK standard for row-oriented
tables, and updated
with appropriate scope=row|col attributes to identify the header cell in
each row or column.
You can see
Hi Guys,
whatever you come up with I anticipate it comes with descriptions
of how to use it as well. I would recommend putting the JEP on GitHub
(although this may not be the usual process), since this topic have
bearings on other crypto APIs in the workings.
I really hope that the end-result
Hi Martin,
Sorry for the delay.
I'd like to wait for finalization of TLS 1.3 specification, so that we
can get a stable specification of the Certificate Authorities extension.
For the current design, I did not see much benefit to add a new
CertificateAuthority API. The
