On Wed, 2 Mar 2022 19:04:26 GMT, zzambers wrote:
> When testing compatibility of jdk TLS implementation with gnutls, I have
> found a problem. The problem is, that gnutls does not like use of
> user_canceled alert when closing TLS-1.3 connection from duplexCloseOutput()
&
On Wed, 4 May 2022 19:22:05 GMT, Bradford Wetmore wrote:
>> When testing compatibility of jdk TLS implementation with gnutls, I have
>> found a problem. The problem is, that gnutls does not like use of
>> user_canceled alert when closing TLS-1.3 connection from duplexCloseOutput()
>> (used by
On Tue, 1 Mar 2022 17:09:57 GMT, zzambers wrote:
> Fixed API Note in javadoc for javax.net.ssl.SSLSocket class. API Note was
> introduced by JDK-8208526 [1]. At that point both Socket.shutdownInput() /
> Socket.shutdownOutput() and InputStream.close() / OutputStream.close()
> pe
On Wed, 9 Mar 2022 21:12:06 GMT, Bradford Wetmore wrote:
>> When testing compatibility of jdk TLS implementation with gnutls, I have
>> found a problem. The problem is, that gnutls does not like use of
>> user_canceled alert when closing TLS-1.3 connection from duplexCloseOutput()
>> (used by
result looks good (also
>> links work), there was just one problem with brace, but I have fixed that.
>
> @zzambers, the CSR was approved yesterday, and is just waiting your
> integration. I will sponsor it.
@bradfordwetmore, thanks
-
PR: https://git.openjdk.java.net/jdk/pull/7648
On Mon, 7 Mar 2022 21:01:12 GMT, Bradford Wetmore wrote:
>> @bradfordwetmore Sure if more changes are desired I can pull your changes.
>> When It comes to CSR I am not fully familiar with the process. Is action
>> expected from my side?
>
>> Sure if more changes are desired I can pull your chan
On Tue, 8 Mar 2022 14:21:19 GMT, zzambers wrote:
>> Fixed API Note in javadoc for javax.net.ssl.SSLSocket class. API Note was
>> introduced by JDK-8208526 [1]. At that point both Socket.shutdownInput() /
>> Socket.shutdownOutput() and InputStream.close() / OutputStream.clo
is behaviour has
> changed as result of JDK-8216326 [2]. InputStream.close() /
> OutputStream.close() no longer perform half-close but full socket close, but
> API Note was never updated.
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8208526
> [2] https://bugs.openjdk.java.ne
On Mon, 7 Mar 2022 21:01:12 GMT, Bradford Wetmore wrote:
>> @bradfordwetmore Sure if more changes are desired I can pull your changes.
>> When It comes to CSR I am not fully familiar with the process. Is action
>> expected from my side?
>
>> Sure if more changes are desired I can pull your chan
is behaviour has
> changed as result of JDK-8216326 [2]. InputStream.close() /
> OutputStream.close() no longer perform half-close but full socket close, but
> API Note was never updated.
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8208526
> [2] https://bugs.openjdk.java.ne
On Fri, 4 Mar 2022 23:43:30 GMT, Bradford Wetmore wrote:
>> zzambers has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Updated copyright for SSLSocket.java
>
> There are more changes needed, and should pr
On Thu, 3 Mar 2022 15:40:31 GMT, Xue-Lei Andrew Fan wrote:
>> When testing compatibility of jdk TLS implementation with gnutls, I have
>> found a problem. The problem is, that gnutls does not like use of
>> user_canceled alert when closing TLS-1.3 connection from duplexCloseOutput()
>> (used b
is behaviour has
> changed as result of JDK-8216326 [2]. InputStream.close() /
> OutputStream.close() no longer perform half-close but full socket close, but
> API Note was never updated.
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8208526
> [2] https://bugs.openjdk.java.ne
d probably reintroduce issues for legacy
>> apps... )
>>
>> I also ran jdk_security tests locally, which passed for me.
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1918473
>> [2] https://datatracker.ietf.org/doc/html/rfc8446#section-6.1
>> [3]
>
When testing compatibility of jdk TLS implementation with gnutls, I have found
a problem. The problem is, that gnutls does not like use of user_canceled alert
when closing TLS-1.3 connection from duplexCloseOutput() (used by
socket.close() unless shutdownOutput was called explicitly) and conside
>> [1] https://bugs.openjdk.java.net/browse/JDK-8208526
>> [2] https://bugs.openjdk.java.net/browse/JDK-8216326
>
> @zzambers I've created a corresponding issue for you in the tracker, please
> rename your PR title to 8282529 and the system should automatically mark your
Fixed API Note in javadoc for javax.net.ssl.SSLSocket class. API Note was
introduced by JDK-8208526 [1]. At that point both Socket.shutdownInput() /
Socket.shutdownOutput() and InputStream.close() / OutputStream.close()
performed half-close of TLS-1.3 connection. However this behaviour has chang
17 matches
Mail list logo
