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

Fix a write on read situation #17

Merged
merged 1 commit into from
Oct 23, 2015
Merged

Conversation

gforcada
Copy link
Member

Move the assignable where is actually needed, thus preventing a write on read.

Note that there is a possible vector for a write on read, see assigned_rules method, where it needs the assignable, but if that is not found it causes a write on read.

This last issue is fixed with plone/plone.contentrules#2

@jensens
Copy link
Member

jensens commented Oct 21, 2015

I'd add a short comment why its twice inside the block to the code.

@jensens
Copy link
Member

jensens commented Oct 21, 2015

and changelog entry is missing

Only get the rule management assignable if it's going to be used.

Getting it has the side effect of creating it if it does not exist,
thus causing a write on read.
@gforcada
Copy link
Member Author

@jensens change log entry added. From the last commits seems that this can only be applied on plone 5, it will be needed to be backported at 4.3 (will do afterwards).

Jenkins: http://jenkins.plone.org/job/pull-request-5.0/504/

@gforcada
Copy link
Member Author

Jenkins is green :-) so ready to be merged

jensens added a commit that referenced this pull request Oct 23, 2015
@jensens jensens merged commit f2839b9 into plone:master Oct 23, 2015
jensens added a commit to plone/buildout.coredev that referenced this pull request Oct 23, 2015
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.

2 participants