-
Notifications
You must be signed in to change notification settings - Fork 877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for development signing #1247
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -37,7 +37,7 @@ | |
} | ||
|
||
#if !defined(OFFICIAL_BUILD) | ||
return "com.brave.Browser.development"; | ||
return "com.brave.Browser"; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why did this need to change? Was it defaulting non-official builds to the dev ID? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. actually this shouldn't be needed. I think it's just leftover from when I couldn't get it to work when everything was set to com.brave.Browser.development. I'll check now |
||
#else | ||
switch (chrome::GetChannel()) { | ||
case version_info::Channel::CANARY: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,11 @@ | ||
diff --git a/chrome/installer/mac/variables.sh b/chrome/installer/mac/variables.sh | ||
index cb07976f21bacda46b4a2b7db229d869dca80f1a..00c389cea0cad4766559b1e99bb8c98584736f01 100644 | ||
index cb07976f21bacda46b4a2b7db229d869dca80f1a..f75c2b4ccae6418fdf2b2f853107778deff39f2d 100644 | ||
--- a/chrome/installer/mac/variables.sh | ||
+++ b/chrome/installer/mac/variables.sh | ||
@@ -19,5 +19,6 @@ enforcement_flags_installer_tools="${enforcement_flags_helpers},kill" | ||
@@ -19,5 +19,5 @@ enforcement_flags_installer_tools="${enforcement_flags_helpers},kill" | ||
# contains the hash of the certificate used to sign Chrome. When transitioning | ||
# signing certs, this may include the hash of both the old and new certificate. | ||
requirement_suffix="\ | ||
-and certificate leaf = H\"c9a99324ca3fcb23dbcc36bd5fd4f9753305130a\" \ | ||
+and (certificate leaf = H\"${codesign_id}\" or \ | ||
+certificate leaf = H\"${codesign_id}\") \ | ||
+and certificate leaf = H\"${codesign_id}\" \ | ||
" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This logic is changing; is an empty dummy.provisionprofile OK for non-official builds? (have you tested this code-path?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this logic isn't changing, signing never worked for non-official builds. This is in fact the only code path I have tested because I can't test the dev/beta signing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for dev signing we only pass a provision profile to simplify things with the number of arguments. It isn't actually used in the signing script when
--development
(below) is passed