-
Notifications
You must be signed in to change notification settings - Fork 30
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
Push IPs address to SSLEngine session #983
Conversation
For the code coming from tomcat I have indicated the differences in the file and add the copyright disclaimer for each file following the indication from the Free Software Law Center, section 2.2. If I have understood correctly licence in spec file should not be modified because that is the distribution licence for the artefact and this will not change, we need to incorporate the copyright only in the file. Is this correct? |
8791361
to
4ed08d1
Compare
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.
Hi @fmarco76 , I can see that comments from PR #73 are addressed. Thanks! So, this (PR #983) is to go with PR #972 ? I see that both are for the master branch. So after that, they will be ported to v10.13? Anyway, as far as I can tell with my limited knowledge with Tomcat, this looks good to me, as long as it works. I recall that you put in some test cases in one of the tickets before. Please put those in the proper Bugilla bug for QE to follow. Thanks!
**SSLEngine** is by design unaware of the underlying communication channel. In tomcat the communication channel is started by the classes `NioEndpoint` and it is maintained in `SecureNioChannel` which will create the buffer used with the SSLEngine in order to wrap and unwrap the messages. To allow the audit of TLS messages to include IP addresses of the client and server, the above classed have been extended in order to store the IPs in the SSLEngine session after its creation. Replace the tomcatJSS PR#73 (dogtagpki/tomcatjss#73)
4ed08d1
to
2264fa8
Compare
Apache-2.0 added in |
Yes, I will port to the other branch after merge. |
Kudos, SonarCloud Quality Gate passed! |
@ladycfu Thanks! |
SSLEngine is by design unaware of the underlying communication channel. In tomcat the communication channel is started by the classes
NioEndpoint
and it is maintained inSecureNioChannel
which will create the buffer used with the SSLEngine in order to wrap and unwrap the messages.To allow the audit of TLS messages to include IP addresses of the client and server, the above classed have been extended in order to store the IPs in the SSLEngine session after its creation.
Replace the tomcatJSS PR#73
(dogtagpki/tomcatjss#73)