Major revamp of security. Passwords are first SHA1 hashed and then
that hash is bcrypted. Bcrypted hashes are stored in a new column on users. This separate column is only to allow for rollbacks, eventually the old SHA1 hash column will be removed. Sensitive cookie details are now encrypted to prevent user tampering and more stringent checks on secret_token and session_secret_key are enforced.
This commit is contained in:
@@ -2596,7 +2596,8 @@ CREATE TABLE users (
|
||||
default_image_size character varying(255) DEFAULT 'large'::character varying NOT NULL,
|
||||
favorite_tags text,
|
||||
blacklisted_tags text,
|
||||
time_zone character varying(255) DEFAULT 'Eastern Time (US & Canada)'::character varying NOT NULL
|
||||
time_zone character varying(255) DEFAULT 'Eastern Time (US & Canada)'::character varying NOT NULL,
|
||||
bcrypt_password_hash text
|
||||
);
|
||||
|
||||
|
||||
@@ -6207,4 +6208,6 @@ INSERT INTO schema_migrations (version) VALUES ('20130221032344');
|
||||
|
||||
INSERT INTO schema_migrations (version) VALUES ('20130221035518');
|
||||
|
||||
INSERT INTO schema_migrations (version) VALUES ('20130221214811');
|
||||
INSERT INTO schema_migrations (version) VALUES ('20130221214811');
|
||||
|
||||
INSERT INTO schema_migrations (version) VALUES ('20130305005138');
|
||||
Reference in New Issue
Block a user