[
https://issues.apache.org/jira/browse/GEODE-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273163#comment-16273163
]
ASF subversion and git services commented on GEODE-3923:
--------------------------------------------------------
Commit 28755d68e335c30fe074d17d352610babe9b7932 in geode's branch
refs/heads/feature/GEODE-3923 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=28755d6 ]
GEODE-3923 Provide whitelist/blacklist capability for java serialization
Removing commented-out code and a Thread.sleep(). I opened GEODE-4037
to track the hot loop that made us, perhaps inadvisedly, add the
Thread.sleep().
> 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)
