Page MenuHomePhabricator

Change the "can see remote address?" policy to "is administrator?" everywhere
ClosedPublic

Authored by epriestley on Jan 30 2018, 8:07 PM.
Tags
None
Referenced Files
F19873101: D18971.id45503.diff
Mar 15 2026, 3:26 PM
F19865953: D18971.id45498.diff
Mar 14 2026, 4:00 PM
F19016510: D18971.id.diff
Nov 23 2025, 4:21 AM
F18855610: D18971.diff
Nov 1 2025, 5:54 AM
F18840234: D18971.diff
Oct 27 2025, 10:40 PM
F18832973: D18971.id45503.diff
Oct 26 2025, 12:02 AM
F18825198: D18971.diff
Oct 23 2025, 8:16 PM
F18822749: D18971.id.diff
Oct 23 2025, 8:16 AM
Subscribers
None

Details

Summary

Depends on D18970. Ref T13049. Currently, the policy for viewing remote addresses is:

  • In activity logs: administrators.
  • In push and pull logs: users who can edit the corresponding repository.

This sort of makes sense, but is also sort of weird. Particularly, I think it's kind of hard to understand and predict, and hard to guess that this is the behavior we implement. The actual implementation is complex, too.

Instead, just use the rule "administrators can see remote addresses" consistently across all applications. This should generally be more strict than the old rule, because administrators could usually have seen everyone's address in the activity logs anyway. It's also simpler and more expected, and I don't really know of any legit use cases for the "repository editor" rule.

Test Plan

Viewed pull/push/activity logs as non-admin. Saw remote addresses as an admin, and none as a non-admin.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable