)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"de2af54e9abc26e23d24a4580f5b974bae1f6d1b","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Remove password column in password table"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"The password column which saves unhashed password is"},{"line_number":10,"context_line":"useless now. Safe to remove it."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I6c0850c16be7900da4b882a28900926e16088b70"},{"line_number":13,"context_line":"bp: removed-as-of-rocky"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"bf659307_ec0c1344","line":10,"updated":"2018-03-23 18:45:35.000000000","message":"This is not accurate. The password column didn\u0027t contain unhashed passwords, it contained passwords hashed with a less-than-ideal hashing algorithm. The reason there are two columns is for compatibility across rolling upgrades.\n\nThis is the change that introduced the new column: https://review.openstack.org/#/c/438701/\n\nThat change did not migrate existing passwords to the new column, so if we simply drop the column we lose user\u0027s passwords.\n\nIf we\u0027re ready to drop this column then we should also address the other transitional changes in that patch, like the rolling_upgrade_password_hash_compat option and the deprecated crypt_strength option.","commit_id":"b6bc1c26cc6dbe97927a87626e860faf76f23d9f"}]}