Re: RFR: 8357915: SecureRandom nextLong memory usage

2025-06-29 Thread Koushik Muthukrishnan Thirupattur
On Thu, 26 Jun 2025 18:16:28 GMT, Chen Liang wrote: >> SecureRandom uses straightforward implementations inherited from Random but >> in the process does double the memory allocations necessary. >> The delegation to SecureRandom.engineNextBytes does not provide `int` or >> `long` values, the ca

Re: RFR: 8357915: SecureRandom nextLong memory usage

2025-06-29 Thread Chen Liang
On Thu, 26 Jun 2025 18:00:21 GMT, Koushik Muthukrishnan Thirupattur wrote: > SecureRandom uses straightforward implementations inherited from Random but > in the process does double the memory allocations necessary. > The delegation to SecureRandom.engineNextBytes does not provide `int` or > `

Re: RFR: 8357915: SecureRandom nextLong memory usage

2025-06-29 Thread ExE Boss
On Thu, 26 Jun 2025 18:00:21 GMT, Koushik Muthukrishnan Thirupattur wrote: > SecureRandom uses straightforward implementations inherited from Random but > in the process does double the memory allocations necessary. > The delegation to SecureRandom.engineNextBytes does not provide `int` or > `

RFR: 8357915: SecureRandom nextLong memory usage

2025-06-29 Thread Koushik Muthukrishnan Thirupattur
SecureRandom uses straightforward implementations inherited from Random but in the process does double the memory allocations necessary. The delegation to SecureRandom.engineNextBytes does not provide `int` or `long` values, the caller must allocate a byte array and assemble the value itself. So

Re: RFR: 8361018: Eliminate unnecessary buffering and encoding conversion in BufferedWriter

2025-06-29 Thread ExE Boss
On Fri, 27 Jun 2025 16:48:40 GMT, Shaojin Wen wrote: > BufferedWriter -> OutputStreamWriter -> StreamEncoder > > In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has > a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer > can be removed. And w

Re: RFR: 8361018: Eliminate unnecessary buffering and encoding conversion in BufferedWriter

2025-06-29 Thread Shaojin Wen
On Fri, 27 Jun 2025 16:48:40 GMT, Shaojin Wen wrote: > BufferedWriter -> OutputStreamWriter -> StreamEncoder > > In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has > a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer > can be removed. And w

RFR: 8361018: Eliminate unnecessary buffering and encoding conversion in BufferedWriter

2025-06-29 Thread Shaojin Wen
BufferedWriter -> OutputStreamWriter -> StreamEncoder In this call chain, BufferedWriter has a char[] buffer, and StreamEncoder has a ByteBuffer. There are two layers of cache here, or the BufferedWriter layer can be removed. And when charset is UTF8, if the content of write(String) is LATIN1,

Discard or clamp ticket lifetime?

2025-06-29 Thread Bernd Eckenfels
Hello, We deal with a regression in JSSE regarding resumption tickets with high lifetime. In older versions with Java 11 the customer claimed a FTP Server was reachable, with Java 21 the connections are rejected. Looking at the debug log of the new version, we can see a session resumption ticke

Re: X-Wing KEM

2025-06-29 Thread Sebastian Stenzel
> On 28. Jun 2025, at 00:12, Wei-Jun Wang wrote: > > [...] After all, there is no parameter for X-Wing. Did you hear the authors > they want to introduce other algorithms like ed448 and ML-KEM-1024 into it? I forwarded this question and let you know the answer! >> >>> On 7. Jun 2025, at 23:34