[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-user
Subject:    [jira] [Resolved] (WSS-340) support Certificates revocation check before encrypt on sender side
From:       "Colm O hEigeartaigh (Resolved) (JIRA)" <jira () apache ! org>
Date:       2012-02-17 15:13:59
Message-ID: 1010231251.50870.1329491639576.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh resolved WSS-340.
-------------------------------------

    Resolution: Fixed
    
> support Certificates revocation check before encrypt on sender side
> -------------------------------------------------------------------
> 
> Key: WSS-340
> URL: https://issues.apache.org/jira/browse/WSS-340
> Project: WSS4J
> Issue Type: Improvement
> Affects Versions: 1.6.4
> Reporter: Freeman Fang
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.5
> 
> Attachments: WSS-340.patch
> 
> 
> currently WSS4J can support Certificates revocation check(CRL and OCSP) when \
> receiver side validate a signature. Similarly WSS4J should also support \
> Certificates revocation check before encrypt on sender side, as in both case it's \
> possible to use a revoked certificate. We can do it in EncryptionAction where we \
> can load encrypt crypto and use the verifyTrust(certs, enableRevocation, \
> enableOCSP) already there.

--
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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]