Re: CipherInputStream may not be closed

Am 08.09.23 um 17:32 schrieb axh: Hi Anna-Katharina, what version are you using? In the current 3.0, the stream is closed (implicitly) by using the try-with-resources syntax (https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html): try (CipherInputStream cis = n

Re: CipherInputStream may not be closed

Hei Axel, Thanks a lot for pointing this out! We both weren’t (anymore?) aware of this syntax! We will adapt the respective file! Best, Anna > On 8. Sep 2023, at 17:32, axh wrote: > > Hi Anna-Katharina, > > what version are you using? In the current 3.0, the stream is closed > (implicitly)

Re: CipherInputStream may not be closed

Hi Anna-Katharina, what version are you using? In the current 3.0, the stream is closed (implicitly) by using the try-with-resources syntax (https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html): try (CipherInputStream cis = new CipherInputStream(data, cipher)) {

CipherInputStream may not be closed

Hei dear maintainers, For a benchmark [1], we randomly sampled JCA usages to decide if the API usage is a violation of any API usage constraint. We believe we found one for the JCA class CipherInputStream. The call to *close* is missing for the call sequence to *CipherInputStream*. Thus, the inp