You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2016/08/02 04:57:20 UTC

[jira] [Commented] (HBASE-16317) revert all ESAPI changes

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

Nick Dimiduk commented on HBASE-16317:
--------------------------------------

You read my mind [~busbey]. Mind if I pick this one up while you work through the build side?

> revert all ESAPI changes
> ------------------------
>
>                 Key: HBASE-16317
>                 URL: https://issues.apache.org/jira/browse/HBASE-16317
>             Project: HBase
>          Issue Type: Sub-task
>          Components: dependencies, security
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
>
> to unblock releases, we'll start cleaning up the category-x problem by reverting all the ESAPI changes.
> we should try to include a release note with what this means we'll be vulnerable to.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)