ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Giger (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WSS-360) Port BSP enforcer to streaming code.
Date Fri, 06 Apr 2012 17:49:22 GMT

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

Marc Giger commented on WSS-360:
--------------------------------

Commit r1310493 introduces BSP enforcement for the receiving side (Should the sending side
have BSP enforcement too)?
The rules can be disabled individually.
Not all rules are implemented, but just these which didn't complicate/pollute things to much.
During implementation of these I asked me the question how valuable the BSP rules
are for production use. Wouldn't it be wiser to have a separate BSP Module for static
analysis during development time?
                
> Port BSP enforcer to streaming code.
> ------------------------------------
>
>                 Key: WSS-360
>                 URL: https://issues.apache.org/jira/browse/WSS-360
>             Project: WSS4J
>          Issue Type: Sub-task
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0
>
>
> This task is to port the BSP enforcer used in the DOM code to the streaming code, to
enforce Basic Security Profile 1.1 requirements.

--
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


Mime
View raw message