You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2009/02/04 23:11:59 UTC
[jira] Closed: (FTPSERVER-273) Do not default tha algorithm for
KeyManager and TrustManager to SunX509
[ https://issues.apache.org/jira/browse/FTPSERVER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed FTPSERVER-273.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.1
Assignee: Niklas Gustavsson
This annoys me because I know I've fixed this before but obviously screwed up the commit somehow. Anyone, now fixed in rev 740915 (1.1) and 740837 (1.0.0).
> Do not default tha algorithm for KeyManager and TrustManager to SunX509
> -----------------------------------------------------------------------
>
> Key: FTPSERVER-273
> URL: https://issues.apache.org/jira/browse/FTPSERVER-273
> Project: FtpServer
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0.0-RC2
> Reporter: Sai Pullabhotla
> Assignee: Niklas Gustavsson
> Priority: Minor
> Fix For: 1.0.0, 1.1
>
>
> The SSLConfigurationFactory class currently defaults the trustStoreAlgoritm and keyStoreAlgorithms to SunX509. This does not work on IBM's JVM unless user explicitly configures these parameters to IbmX509. Instead of defaulting to a hard coded value, SunX509, we should consider changing the code to use -
> KeyManagerFactory.getDefaultAlgorithm() and TrustManagerFactory.getDefaultAlgorithm().
> So, if the "algorithm" attribute is not specified, create key and trust managers using the default algorithm used by the JVM.
> If we decide to do this, update the documentation as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.