-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
common-security, doors: switch to openssl where possible
Motivation: Using the javax.net.SSLContext interface currently does not allow (easily at least) for a pass-through to native (open)SSL. More recent versions of Netty, however, use a new SslContext object which looks for the presence of openssl in the environment and uses it by default, falling back to the Java implementation if it is not present on the host. For xroot TLS, we have seen at least a 20% performance gain over JSSE when using openssl. Modification: The major change comes in the CanlContextFactory. We have refitted the Builder to take the class of the context object to use. The rest of the code has been refactored to fit this API. In most cases, switching to Netty was simple, but in the few places where the javax.net.SSLContext was necessary (in order explicitly to open a socket) we have left that in place. Finally, we have refactored the Http factory beans and changed the injection to use the Netty version. Result: Where possible, the Netty context is used, which prefers openssl by default and falls back to Java where it doesn't exist. No visible changes to the user. Target: master Patch: https://rb.dcache.org/r/13044 Acked-by: Tigran
- Loading branch information
Showing
17 changed files
with
231 additions
and
164 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.