Activate keychain reauthorization.

chrome/installer/mac/sign_app.sh.in

Index: chrome/installer/mac/sign_app.sh.in
diff --git a/chrome/installer/mac/sign_app.sh.in b/chrome/installer/mac/sign_app.sh.in
index c5118ab23d49d3999fcb841375a0b39e7ae89ab8..02e618113dc5d4295dcae14bb8ac398e9812da90 100644
--- a/chrome/installer/mac/sign_app.sh.in
+++ b/chrome/installer/mac/sign_app.sh.in
@@ -49,7 +49,7 @@ requirement_string="\
 designated => \
 (identifier \"com.google.Chrome\" or identifier \"com.google.Chrome.canary\") \

[Mark Mentovai, 2017/03/10 00:56:46]

Since we’ve got to do the reauthorization now anyway, let’s expand this a bit to
avoid a potential reauthorization in the future, for when we split other
channels out for side-by-side installation (if we do that).

(identifier \"com.google.Chrome\" or \
identifier \"com.google.Chrome.beta\" or \
identifier \"com.google.Chrome.dev\" or \
identifier \"com.google.Chrome.canary\") and \
(certificate leaf = H\"85cee8254216185620ddc8851c7a9fc4dfe120ef\" or \
certificate leaf = H\"c9a99324ca3fcb23dbcc36bd5fd4f9753305130a\")

[Greg K, 2017/03/10 18:06:29]

Done.

 and (certificate leaf = H\"85cee8254216185620ddc8851c7a9fc4dfe120ef\" or \
-certificate leaf = H\"34f0bdf7f87d4f3a955862c351472e52250e4c2b\") \
+certificate leaf = H\"c9a99324ca3fcb23dbcc36bd5fd4f9753305130a\") \
 "
 
 enforcement_flags="restrict"