geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3923) Provide whitelist/blacklist capability for java serialization
Date Fri, 01 Dec 2017 00:12:03 GMT

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

ASF subversion and git services commented on GEODE-3923:
--------------------------------------------------------

Commit 9ff92114d185b8c367d1746726f3ca96a58c508b in geode's branch refs/heads/develop from
[~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9ff9211 ]

GEODE-3923 Provide whitelist/blacklist capability for java serialization

Fixing a few more minor review comments - removing commented out code


> Provide whitelist/blacklist capability for java serialization
> -------------------------------------------------------------
>
>                 Key: GEODE-3923
>                 URL: https://issues.apache.org/jira/browse/GEODE-3923
>             Project: Geode
>          Issue Type: New Feature
>          Components: serialization
>            Reporter: Bruce Schuchardt
>             Fix For: 1.4.0
>
>
> I would like to be able to restrict what classes of objects Geode will allow to be deserialized
via Java's ObjectInputStream in clients and servers.  Something similar to the mechanism recently
added to the JRE (http://openjdk.java.net/jeps/290) would be pretty cool.  Geode would have
to whitelist its own stuff, of course, so I don't have to deal with it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message