extensions/test/data/content_verifier/README - Issue 585583003: Fix case-sensitivity problems in extension content verification

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: extensions/test/data/content_verifier/README

Issue 585583003: Fix case-sensitivity problems in extension content verification (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: undo change to extension_protocols.cc Created 6 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« extensions/browser/verified_contents.cc ('K') | « extensions/browser/verified_contents_unittest.cc ('k') | extensions/test/data/content_verifier/payload.json » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: extensions/test/data/content_verifier/README

diff --git a/extensions/test/data/content_verifier/README b/extensions/test/data/content_verifier/README

index 8379a83c6f325fdffc58f7a60284c417ccdce5ba..b9a8bb618f359b14ba9b9bcbc934595f8c1ba4ba 100644

--- a/extensions/test/data/content_verifier/README

+++ b/extensions/test/data/content_verifier/README

@@ -5,6 +5,10 @@ openssl genrsa -out private_key.pem 2048

openssl rsa -in private_key.pem -pubout -out public_key.pem

+The payload.json file contains randomly generated base64url encoded sha256

+hashes for a set of file paths.

The signature was generated by:

1) Take the contents of payload.json and base64url encode them:

2) Put the contents of payload_encoded.txt into the "payload" field of

verified_contents.json.

-3) Copy the contents of the "protected" field from verified_contents.json into

-protected.txt.

+3) Copy the contents of the "protected" field (the one with {"kid":

+"webstore"}) from verified_contents.json into protected.txt.

4) Concatenate the "protected" and "payload" fields with a '.' separator.