Page MenuHomePhabricator

Apply application visibility checks during normal object filtering
ClosedPublic

Authored by epriestley on Jan 1 2017, 7:10 PM.
Tags
None
Referenced Files
F15508172: D17127.id41194.diff
Wed, Apr 16, 2:42 AM
F15492237: D17127.id.diff
Sat, Apr 12, 12:39 PM
F15489848: D17127.diff
Fri, Apr 11, 12:42 PM
F15470955: D17127.id41189.diff
Sat, Apr 5, 2:18 AM
F15470954: D17127.id41194.diff
Sat, Apr 5, 2:18 AM
F15468745: D17127.id41189.diff
Fri, Apr 4, 5:00 AM
F15448419: D17127.id41189.diff
Fri, Mar 28, 4:46 AM
F15431802: D17127.id41194.diff
Mon, Mar 24, 2:36 PM
Subscribers
None

Details

Summary

Fixes T9058. Normally, "Query" classes apply an application check and just don't load anything if it fails.

However, in some cases (like email recipient filtering) we run policy checks without having run a Query check first. In that case, one user (the actor) loads the object, then we filter it against other users (the recipeints).

Explicitly apply the application check during normal filtering.

Test Plan

Added a failing test case and made it pass.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jan 2 2017, 1:10 AM
This revision was automatically updated to reflect the committed changes.