epriestley ab7d89edc8 Use better secrets in generating account tokens ... Summary: When we generate account tokens for CSRF keys and email verification, one of the inputs we use is the user's password hash. Users won't always have a password hash, so this is a weak input to key generation. This also couples CSRF weirdly with auth concerns. Instead, give users a dedicated secret for use in token generation which is used only for this purpose. Test Plan: - Ran upgrade scripts. - Verified all users got new secrets. - Created a new user. - Verified they got a secret. - Submitted CSRF'd forms, they worked. - Adjusted the CSRF token and submitted CSRF'd forms, verified they don't work. Reviewers: btrahan Reviewed By: btrahan Subscribers: epriestley Differential Revision: https://secure.phabricator.com/D8748		2014-04-10 11:45:10 -07:00
..
autopatches	Use better secrets in generating account tokens	2014-04-10 11:45:10 -07:00
patches	Add a checkbox to the LDAP auth configuration UI to "Always Search"	2014-04-08 11:36:23 -07:00
quickstart.sql	Update quickstart SQL	2014-01-17 16:11:16 -08:00