[
https://issues.apache.org/jira/browse/AMQ-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011304#comment-15011304
]
ASF subversion and git services commented on AMQ-6013:
------------------------------------------------------
Commit d7a3b9406b8496c3f1508bebf3c7ff5367374b90 in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=d7a3b94 ]
https://issues.apache.org/jira/browse/AMQ-6029 - make certs available to tunnle
servlet - HttpsNeedClientAuthSendAndReceiveTest regression, add javax.security
so login exceptions can propogate over http -
https://issues.apache.org/jira/browse/AMQ-6013
> Restrict classes that can be serialized in ObjectMessages
> ---------------------------------------------------------
>
> Key: AMQ-6013
> URL: https://issues.apache.org/jira/browse/AMQ-6013
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.12.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.11.3, 5.13.0
>
>
> At some points we do (de)serialization of JMS Object messages inside the
> broker (HTTP, Stomp, Web Console, ...). We need to restrict classes that can
> be serialized in this way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)