Skip to content
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

Merged
merged 1 commit into from
Aug 29, 2023

Conversation

fmarco76
Copy link
Member

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)

@fmarco76 fmarco76 requested a review from edewata August 28, 2023 17:35
@fmarco76
Copy link
Member Author

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?

@fmarco76 fmarco76 force-pushed the IPAddressToSSLEngine branch 2 times, most recently from 8791361 to 4ed08d1 Compare August 28, 2023 18:01
Copy link
Contributor

@ladycfu ladycfu left a 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)
@fmarco76
Copy link
Member Author

Apache-2.0 added in jss.spec.

@fmarco76
Copy link
Member Author

So after that, they will be ported to v10.13?

Yes, I will port to the other branch after merge.

@sonarcloud
Copy link

sonarcloud bot commented Aug 29, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 6 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@fmarco76
Copy link
Member Author

@ladycfu Thanks!

@fmarco76 fmarco76 merged commit ac5a2a2 into dogtagpki:master Aug 29, 2023
40 checks passed
@fmarco76 fmarco76 deleted the IPAddressToSSLEngine branch September 5, 2023 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants