activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-6077) Better configuration of restricted classes for clients
Date Mon, 14 Dec 2015 19:14:46 GMT


ASF subversion and git services commented on AMQ-6077:

Commit 5a8cd29195cd63b0414a89eafe8decf181f20970 in activemq's branch refs/heads/activemq-5.12.x
from [~dejanb]
[;h=5a8cd29 ] - test

(cherry picked from commit 7951037f20e8d6752ab0bbd90189a8276bc61a55)
(cherry picked from commit f3aedc753c877cd947c6eb968f1ca8d8d1809f8a)

> Better configuration of restricted classes for clients
> ------------------------------------------------------
>                 Key: AMQ-6077
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.13.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.12.2, 5.13.1, 5.14.0
> [AMQ-6013] introduces the checks on the classes that are allowed to be serialized through
ObjectMessages. The original implementation was designed to protect the broker, so system
property configuration was the easiest solution.
> This change affect the clients that uses ObjectMessages.getObject() method. We need to
provide a better way of configuring this for clients. My initial idea is that we should provide
a configuration on ActiveMQConnectionFactory and ActiveMQComponent classes.

This message was sent by Atlassian JIRA

View raw message