-
Notifications
You must be signed in to change notification settings - Fork 157
OCSP Stapling Checks #756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCSP Stapling Checks #756
Conversation
michael-simons
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work. There are only some minor changes regarding tests and method visibility.
I also think we should keep the way loading certs through the keystore as opposed to the intermediate suggestion with the TrustAnchors.
As this is for 4.2, we can maybe make the CertificateTool final and add a private constructor too (we tend to do this in OGM and Spring world for those utils classes).
driver/src/main/java/org/neo4j/driver/internal/security/SecurityPlanImpl.java
Outdated
Show resolved
Hide resolved
driver/src/main/java/org/neo4j/driver/internal/security/SecurityPlanImpl.java
Outdated
Show resolved
Hide resolved
driver/src/main/java/org/neo4j/driver/internal/security/SecurityPlanImpl.java
Outdated
Show resolved
Hide resolved
driver/src/main/java/org/neo4j/driver/internal/security/SecurityPlanImpl.java
Outdated
Show resolved
Hide resolved
driver/src/test/java/org/neo4j/driver/internal/SecuritySettingsTest.java
Outdated
Show resolved
Hide resolved
driver/src/test/java/org/neo4j/driver/internal/SecuritySettingsTest.java
Outdated
Show resolved
Hide resolved
driver/src/test/java/org/neo4j/driver/internal/SecuritySettingsTest.java
Outdated
Show resolved
Hide resolved
driver/src/test/java/org/neo4j/driver/internal/SecuritySettingsTest.java
Outdated
Show resolved
Hide resolved
driver/src/test/java/org/neo4j/driver/internal/SecuritySettingsTest.java
Outdated
Show resolved
Hide resolved
…cate revocation checking is to be carried out. By default revocation checking is disabled. If enabled with the corresponding server configuration, the driver will check the validity of stapled OCSP (Online Certificate Status Protocol) response(s). These responses are returned during the TLS handshake by the server and if not present, the driver will fail to accept the certificate. See: https://tools.ietf.org/html/rfc6961
ca3e866 to
fdc6e95
Compare
michael-simons
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only typos in JavaDoc.
driver/src/main/java/org/neo4j/driver/internal/security/SecurityPlanImpl.java
Outdated
Show resolved
Hide resolved
michael-simons
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, only docs. I remember us discussing this change in standup. I like it very much and its closer to the standard in this way.
Adds the ability for TrustStategy to configure whether or not certificate revocation checking is to be carried out. By default revocation checking is disabled.
If enabled with the corresponding server configuration, the driver will check the validity of stapled OCSP (Online Certificate Status Protocol) response(s). These responses are returned during the TLS handshake by the server and if not present, the driver will fail to accept the certificate.
See: https://tools.ietf.org/html/rfc6961