RFR: 8253368: TLS connection always receives close_notify exception [v2]
Sean Coffey
coffeys at openjdk.java.net
Tue Dec 22 15:40:22 UTC 2020
> removing the "closing inbound before receiving peer's close_notify" exception that can be seen with TLS stack if calling close on inbound. After reading the relevant parts of the TLS v1.2/v1.3 RFCs, I believe the local end point doesn't have to wait for close_notify alert from remote end.
Sean Coffey 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 three additional commits since the last revision:
- version 2 redesign
- Merge branch 'master' of https://github.com/openjdk/jdk into JDK-8253368
- 8253368: TLS connection always receives close_notify exception
-------------
Changes:
- all: https://git.openjdk.java.net/jdk/pull/1205/files
- new: https://git.openjdk.java.net/jdk/pull/1205/files/85d41030..86d9dac5
Webrevs:
- full: https://webrevs.openjdk.java.net/?repo=jdk&pr=1205&range=01
- incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=1205&range=00-01
Stats: 284235 lines in 2912 files changed: 188350 ins; 66757 del; 29128 mod
Patch: https://git.openjdk.java.net/jdk/pull/1205.diff
Fetch: git fetch https://git.openjdk.java.net/jdk pull/1205/head:pull/1205
PR: https://git.openjdk.java.net/jdk/pull/1205
More information about the security-dev
mailing list