[PasswordManager] RemoveByKey() shouldn't decrypt the password value
LoginDatabase::RemoveLoginByPrimaryKey() returns a change list that contains the forms that have been deleted. Therefore, it needs to first load the forms from the database. Before this CL: LoginDatabase::RemoveLoginByPrimaryKey() would actually decrypt and fill in the password value. Therefore, it fails in case of a decryption failure. After this CL: Since it doesn't make sense to block the removal of a form in case of decryption failure, LoginDatabase::RemoveLoginByPrimaryKey() won't actually fill in the password value. Hence, the password in the change list will be missing a password value. This change list is used to communicate the change to other observers of the password store. This should be fine because none of the password store observers is interested in the password value in case of deletion. Change-Id: I697e507584d77406280604a1481e437b80184890 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503322 Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Reviewed-by:Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#637664}
Showing
Please register or sign in to comment