[ 
https://issues.apache.org/jira/browse/QPID-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260984#comment-13260984
 ] 

Robbie Gemmell commented on QPID-3973:
--------------------------------------

Hi Jesse,

I don't believe this will have been change since 0.10, but I do know the code 
your patch updates has been modified significantly since then and as a result 
there is little to no chance it applies to the current codebase. Qpid 0.16 has 
long branched for release and should be out in the next couple of weeks, but if 
you wanted to produce an updated patch against the current trunk we can 
certainly look to include it in the 0.18 release ~July/Aug.

(sidenotes: the patch seems to have a scratch file in it, and we need you to 
grant permission for inclusion when attaching patches to JIRAs in order to 
actually use them).

Robbie
                
> QPID Java SSLUtil does not support non-JKS key store types
> ----------------------------------------------------------
>
>                 Key: QPID-3973
>                 URL: https://issues.apache.org/jira/browse/QPID-3973
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client, Java Common
>    Affects Versions: 0.10
>         Environment: Java 1.6 in FIPS mode (NSS)
>            Reporter: Jesse Sightler
>              Labels: nss, pkcs11
>         Attachments: qpid-java.diff
>
>
> We are required to run our system in FIPS-compliant mode, using the NSS 
> library for Java Security. In this mode, we cannot use JKS for private key 
> storage.
> Unfortunately, SSLUtil does not support configurable KeyStore types, and will 
> throw an exception if we attempt to do this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to