https://bz.apache.org/bugzilla/show_bug.cgi?id=59150
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> ---
Selection of the underlying crypto engine in JSSE is typically done by
specifying the "provider". So instead of useOpensslJSSEImplementation="true",
perhaps we specify JSSEProvider="OpenSSL" (or whatever the OpenSSL provider's
name actually is). This would be more extensible, and would even allow for
3rd-party crypto providers to be used, such as Bouncy Castle.
The default would be (blank) and would not specify a provider when initializing
algorithms -- giving Tomcat the JVM's default provider.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
