Skip to content

Commit b1d58d3

Browse files
committed
update README to be about java 10
1 parent a703c86 commit b1d58d3

File tree

1 file changed

+9
-14
lines changed

1 file changed

+9
-14
lines changed

README.md

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
1-
### todo
2-
3-
## Token Binding Protocol Negotiation TLS Extension support for Java 9
1+
## Token Binding Protocol Negotiation TLS Extension support for Java 10
42

53
### Introduction
64
Token Binding over HTTP [[I-D.ietf-tokbind-https]] provides a mechanism
@@ -20,7 +18,7 @@ with the Token Binding ID, which ensures those tokens cannot be used
2018
successfully over a different TLS connection or by a different client
2119
than the one to which they were issued.
2220

23-
This project provides an implementation of the TLS Extension for Token Binding Protocol Negotiation as well as TLS Keying Material Exporters (also TLS Extended Master Secret Extension [[RFC 7627]] in some older versions) for Java 9. An an open source library for consuming or producing Token Binding message structures, which applications do after negotiation, can be found with the [token-binding-java] project.
21+
This project provides an implementation of the TLS Extension for Token Binding Protocol Negotiation as well as TLS Keying Material Exporters for Java 10. An an open source library for consuming or producing Token Binding message structures, which applications do after negotiation, can be found with the [token-binding-java] project.
2422

2523
### Usage
2624
This implementation relies on modifications of a few JDK classes in the `sun.security.ssl` package. The JVM needs to be told to use those modified classes in place of those in the base modul of the JRE. And your application needs to interact with the API of some of those classes, likely through reflection and dynamic method invocation.
@@ -29,10 +27,10 @@ This implementation relies on modifications of a few JDK classes in the `sun.sec
2927
To use the functionality of this project, the JVM needs to be started using the `--patch-module` option as follows:
3028

3129
```
32-
java --patch-module java.base=<path-to-java9-token-binding-negotiation-jar> --add-exports java.base/sun.security.ssl=ALL-UNNAMED ...
30+
java --patch-module java.base=<path-to-java10-token-binding-negotiation-jar> --add-exports java.base/sun.security.ssl=ALL-UNNAMED ...
3331
```
3432

35-
Where path-to-java9-token-binding-negotiation-jar is the path on the file system for this project's jar file. This prepends the jar file to the default bootstrap classpath so that its classes will be used in place of the default JRE classes. Be certain to use the jar version which corresponds to the version of the JRE being used (see [Versions](#versions) below).
33+
Where path-to-java10-token-binding-negotiation-jar is the path on the file system for this project's jar file. This prepends the jar file to the default bootstrap classpath so that its classes will be used in place of the default JRE classes. Be certain to use the jar version which corresponds to the version of the JRE being used (see [Versions](#versions) below).
3634

3735
#### API
3836
A few new methods have been added to the OpenJDK implementations of `SSLEngine` and `SSLSocket` to facilitate an application doing Token Binding using the functionality provided by this project.
@@ -83,22 +81,20 @@ byte[] ekm = (byte[]) ekmMethod.invoke(object, "EXPORTER-Token-Binding", 32);
8381
With the EKM and the negotiated key parameters type, a library like [token-binding-java] can be used to consume or create Token Binding messages.
8482

8583
### <a name="versions"></a> Versions
86-
The Token Binding negotiation implementation relies on modifications to a few OpenJDK classes so needs to be updated to stay in sync when there are changes to those OpenJDK classes in a Java update. As such, the java9-token-binding-negotiation jar version matching the JRE version needs to be used. The following provides the version mappings.
84+
The Token Binding negotiation implementation relies on modifications to a few OpenJDK classes so needs to be updated to stay in sync when there are changes to those OpenJDK classes in a Java update. As such, the java10-token-binding-negotiation jar version matching the JRE version needs to be used. The following provides the version mappings.
8785

88-
| Java 9 Version | java9-token-binding-negotiation Version
86+
| Java 10 Version | java9-token-binding-negotiation Version
8987
| ------------- |-------------
90-
| 9.0.4 | [1.0.0.v2]
91-
| 9.0.1 | [1.0.0.v1]
92-
| 9 | unsupported
88+
| 10.0.1 | [1.0.0.v1]
89+
| 10 | [1.0.0.v1]
9390

9491
See [java8-token-binding-negotiation] for Token Binding Protocol Negotiation support with Java 8.
9592

9693
### License
9794
The modified OpenJDK classes are released under the same GPLv2 + Classpath Exception license as the OpenJDK.
9895

9996

100-
[1.0.0.v1]:https://github.com/pingidentity/java9-token-binding-negotiation/releases/tag/java9-token-binding-negotiation-1.0.0.v1
101-
[1.0.0.v2]:https://github.com/pingidentity/java9-token-binding-negotiation/releases/tag/java9-token-binding-negotiation-1.0.0.v2
97+
[1.0.0.v1]:https://github.com/pingidentity/java10-token-binding-negotiation/releases/tag/java10-token-binding-negotiation-1.0.0.v1
10298

10399

104100
[token-binding-java]:https://github.com/pingidentity/token-binding-java
@@ -110,4 +106,3 @@ The modified OpenJDK classes are released under the same GPLv2 + Classpath Excep
110106
[I-D.ietf-tokbind-negotiation]:https://tools.ietf.org/html/draft-ietf-tokbind-negotiation
111107

112108
[RFC 5705]:https://tools.ietf.org/html/rfc5705
113-
[RFC 7627]:https://tools.ietf.org/html/rfc7627

0 commit comments

Comments
 (0)