accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-891) Authorizations not actually immutable
Date Mon, 10 Jun 2013 16:37:19 GMT

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

Christopher Tubbs updated ACCUMULO-891:
---------------------------------------

    Attachment: ACCUMULO-891.v2.patch

Add [^ACCUMULO-891.v2.patch] as a compromise to get the desired behavior in the Authorization
API, but without breaking thrift constraints. (This makes a copy of the Authorizations when
serializing to thrift, but I don't believe this will have a significant performance impact.)
                
> Authorizations not actually immutable
> -------------------------------------
>
>                 Key: ACCUMULO-891
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-891
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Mike Drob
>            Assignee: Christopher Tubbs
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-891.v1.patch, ACCUMULO-891.v2.patch, AuthorizationsTest.java
>
>
> Instances of {{Authorizations}} are not actually immutable, despite the API making it
seem like they are. A user can make changes that will write-through to the backing data by
using the ByteBuffer getter.
> This is a potential issue if a trusted application acts as a connection broker between
accumulo and untrusted clients.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message