On Thu, 15 Apr 2021 10:27:25 GMT, Sibabrata Sahoo wrote:
>> Valerie Peng has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Fixed an tagLen issue, no key+iv reuse check for decryption, and add
>> regression test for ChaCha20 SKF.
>
>
On Thu, 15 Apr 2021 14:25:13 GMT, Jamil Nimeh wrote:
>> Valerie Peng has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Fixed an tagLen issue, no key+iv reuse check for decryption, and add
>> regression test for ChaCha20 SKF.
>
>
> Could someone (perhaps Jamil?) please help review this change? This enhances
> SunPKCS11 provider with ChaCha20-Poly1305 cipher and ChaCha20 key generation
> support. Majority of the regression tests are adapted from the existing ones
> for SunJCE provider's ChaCha20-Poly1305 cipher impl.
On Thu, 22 Apr 2021 17:38:43 GMT, Naoto Sato wrote:
>> Please review the changes for the subject issue. This has been suggested in
>> a recent discussion thread for the JEP 400
>> [[1](https://mail.openjdk.java.net/pipermail/core-libs-dev/2021-March/075214.html)].
>> A CSR has also been
On Wed, 13 Jan 2021 21:32:07 GMT, Weijun Wang wrote:
> Clean up temporary byte array, char array, and keyspec around keys and
> passwords.
>
> No new regression test.
This pull request has now been integrated.
Changeset: f834557a
Author:Weijun Wang
URL:
> Clean up temporary byte array, char array, and keyspec around keys and
> passwords.
>
> No new regression test.
Weijun Wang has updated the pull request with a new target base due to a merge
or a rebase. The pull request now contains 12 commits:
- Merge branch 'master' into 8258915
-
On 22 Apr 2021, at 18:27, Reinier Zwitserloot
mailto:rein...@zwitserloot.com>> wrote:
For example, I may want to restrict access to the 'logs' directory. I can't
restrict it at the OS level (because the JVM does need to write the log files,
of course), at best I can restrict it at the module
> Please review the changes for the subject issue. This has been suggested in
> a recent discussion thread for the JEP 400
> [[1](https://mail.openjdk.java.net/pipermail/core-libs-dev/2021-March/075214.html)].
> A CSR has also been drafted, and comments are welcome
>
On Thu, 22 Apr 2021 16:29:35 GMT, Roger Riggs wrote:
>> Then `charset()` in the shared secret would return `null`. Would that
>> suffice your case?
>
> I read lines 575-587 as initializing CHARSET regardless of whether the
> Console was created.
OK, revived the charset() method.
> Alan Bateman wrote:
> security features for XML processing can be controlled programmatically,
it doesn't require a security manager to do that.
Yes, it would be nice, and it is feasible, for XML parser libraries to gain
API calls to tell them to never hit the disk or the network to resolve
On Thu, 22 Apr 2021 16:11:16 GMT, Naoto Sato wrote:
>> Not always, for example, if stderr was redirected to a terminal but not
>> stdin and stdout.
>> The istty check is only true if both stdin and stdout are ttys.
>
> Then `charset()` in the shared secret would return `null`. Would that
On Thu, 22 Apr 2021 16:03:12 GMT, Roger Riggs wrote:
>> Would the singleton `Console.cons` be instantiated in your use case? It is
>> created only when isatty() (or Windows' equivalent) in the native code
>> returns true.
>
> Not always, for example, if stderr was redirected to a terminal but
On Thu, 22 Apr 2021 15:42:02 GMT, Naoto Sato wrote:
>> src/java.base/share/classes/java/io/Console.java line 597:
>>
>>> 595: return null;
>>> 596: }
>>> 597: });
>>
>> Please keep the charset() method and return CHARSET.
>>
>> I'm looking at a use case
On Thu, 22 Apr 2021 15:18:11 GMT, Roger Riggs wrote:
>> Naoto Sato has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains 13 additional
>> commits
On Thu, 22 Apr 2021 11:41:40 GMT, Fernando Guallini
wrote:
> Test DHKeyExchange/LegacyDHEKeyExchange.java has been seen to fail
> intermittently. There is a thread synchronisation issue that is fixed by:
>
> - Using SSLSocketTemplate that handles client/server socket configuration and
>
On Tue, 20 Apr 2021 22:35:00 GMT, Naoto Sato wrote:
>> Please review the changes for the subject issue. This has been suggested in
>> a recent discussion thread for the JEP 400
>> [[1](https://mail.openjdk.java.net/pipermail/core-libs-dev/2021-March/075214.html)].
>> A CSR has also been
Test DHKeyExchange/LegacyDHEKeyExchange.java has been seen to fail
intermittently. There is a thread synchronisation issue that is fixed by:
- Using SSLSocketTemplate that handles client/server socket configuration and
synchronisation before connection
- Making use of a CountDownLatch and
17 matches
Mail list logo
