New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 625811 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Computed_hashes file is not getting re-generated if we delete it and tamper Verified_contents at the same time.

Project Member Reported by tkonch...@chromium.org, Jul 5 2016

Issue description

Version: 
OS:  Windows 7, 8.1 and XP

What steps will reproduce the problem?

1. Install and launch chrome 
2. Open CWS and install couple of Extensions (Eg : Office Online, Pin It Button)
3. Once extensions are installed open Chrome:flags and set "Extension Content Verification" to 'Bootstrap"
4. Once the flag is set relaunch chrome and check for the file 'computed_hashes.jason' from "C:\Users\XXXXX\AppData\Local\Google\Chrome\User Data\Default\Extensions\<Extension_id>\<Extension_version> or /meta" for any of the extension.
5. From Chrome:Flags set "Extension Content Verification" flag to 'Enforce" and relaunch chrome 
6. Exit chrome 
7. Navigate to "C:\Users\XXXXX\AppData\Local\Google\Chrome\User Data\Default\Extensions\<Extension_id>\" and delete "Computed_hashes.jason" and tamper "Verified_contents.jason" 
8. Relaunch chrome

Actual Result : computed_hashes file is not regenerated on next launch of chrome for the tampered extension

Expected Result : Computed_hashes file should get re-generated if we delete it and tamper Verified_contents at the same time.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jul 5 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
Bootstrap mode isn't in effect anywhere anymore, it's now Enforce mode on stable and starting in chrome 53 we've made the default be "Enforce Strict". I'm going to mark this as Wontfix but if you can demonstrate any problems with Enforce Strict mode I'd want to have a look. 

Sign in to add a comment