Page MenuHomePhabricator

Make CSRF salt per-user instead of per-request
ClosedPublic

Authored by epriestley on Jun 4 2015, 6:49 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Dec 4, 3:25 PM
Unknown Object (File)
Tue, Dec 3, 8:26 PM
Unknown Object (File)
Thu, Nov 21, 12:13 PM
Unknown Object (File)
Wed, Nov 20, 6:08 PM
Unknown Object (File)
Nov 17 2024, 10:21 AM
Unknown Object (File)
Nov 10 2024, 5:31 AM
Unknown Object (File)
Nov 10 2024, 5:27 AM
Unknown Object (File)
Nov 10 2024, 1:56 AM
Subscribers

Details

Summary

Fixes T8326. This removes calls to PhabricatorStartup from places that daemons may access.

This salt doesn't need to be global; it's embedded in the token we return. It's fine if we use a different salt every time. In practice, we always use the same viewer, so this change causes little or no behavioral change.

Ref T8424. For Spaces, I need a per-request cache for all spaces, because they have unusual access patterns and require repeated access, in some cases by multiple viewers.

We don't currently have a per-request in-process cache that we, e.g., clear in the daemons.

We do have a weak/theoretical/forward-looking attempt at this in PhabricatorStartup::getGlobal() but I'm going to throw that away (it's kind of junky, partly because of T8326) and replace it with a more formal mechanism.

Test Plan
  • Submitted some forms.
  • Grepped for csrf.salt.
  • Viewed page source, saw nice CSRF tokens with salt.
  • All the salts are still the same on every page I checked, but it doesn't matter if this isn't true everywhere.

Diff Detail

Repository
rP Phabricator
Branch
spaces1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 6543
Build 6565: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

epriestley retitled this revision from to Make CSRF salt per-user instead of per-request.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Jun 4 2015, 8:27 PM
This revision was automatically updated to reflect the committed changes.