Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make compliance test suite pass again #16

Merged
merged 1 commit into from
Jan 31, 2017
Merged

Make compliance test suite pass again #16

merged 1 commit into from
Jan 31, 2017

Conversation

acogoluegnes
Copy link
Contributor

With cef06dd, some RMQMessage instances could be
normalised as though it wasn't necessary (the security
issue would happen only on consumption, and normalisation
happens only on publishing). The re-creation of those
RMQMessage instances would make the JMS compliance
test suite fail.

The current commit also enforces trusted package verification
for every received RMQObjectMessage.

With cef06dd, some RMQMessage instances could be
normalised as though it wasn't necessary (the security
issue would happen only on consumption, and normalisation
happens only on publishing). The re-creation of those
RMQMessage instances would make the JMS compliance
test suite fail.

The current commit also enforces trusted package verification
for every received RMQObjectMessage.
@acogoluegnes acogoluegnes added this to the 1.7.0 milestone Jan 30, 2017
@michaelklishin michaelklishin self-assigned this Jan 31, 2017
@michaelklishin michaelklishin merged commit 4aa3b3c into master Jan 31, 2017
@acogoluegnes acogoluegnes deleted the fix-cts branch March 21, 2019 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants