Page MenuHomePhabricator

Allow encrypted mail to be more specific about which object is affected
ClosedPublic

Authored by epriestley on Jun 12 2018, 3:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Mar 16, 1:17 AM
Unknown Object (File)
Sun, Mar 10, 3:13 AM
Unknown Object (File)
Feb 16 2024, 8:47 PM
Unknown Object (File)
Feb 11 2024, 2:05 PM
Unknown Object (File)
Feb 9 2024, 3:02 PM
Unknown Object (File)
Feb 7 2024, 5:17 PM
Unknown Object (File)
Jan 30 2024, 1:17 PM
Unknown Object (File)
Dec 6 2023, 2:59 AM
Subscribers
None

Details

Summary

Depends on D19487. Ref T13151. See PHI647. For some objects, like revisions, we can build slightly more useful secure email without actually disclosing anything.

In the general case, the object monogram may disclose information (#acquire-competitor) but most do not, so applications can whitelist an acceptable nondisclosing subject and link.

Support doing this, and make Differential do it. When we don't have a whitelisted URI but do know the object the mail is about, include a generic PHID-based URI; these are always nondisclosing.

Test Plan
  • Without the Differential changes, sent normal mail (no changes) and secure mail (new generic PHID-based link).
  • With the Differential changes, sent secure mail; got richer subject and body link.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable