-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Brave MacOS downloads should not use .pkg #32316
Comments
DevOps issue: https://github.com/brave/devops/issues/10373 |
The solution identified is that we'll have some new extended attributes on the
The code in Currently, the code looks for a file |
similar upstream code
so looks like using #include <sys/xattr.h> is ok, but that definitely needs to run on a task runner and no UI thread |
@brave/qa-team labeling as |
|
|
|
The `.pkg` binary was replaced by a regular `.dmg` in 1.60: brave/brave-browser#32316
The `.pkg` binary was replaced by a regular `.dmg` in 1.60: brave/brave-browser#32316
The `.pkg` binary was replaced by a regular `.dmg` in 1.60: brave/brave-browser#32316
The `.pkg` binary was replaced by a regular `.dmg` in 1.60: brave/brave-browser#32316
The `.pkg` binary was replaced by a regular `.dmg` in 1.60: brave/brave-browser#32316
Currently, downloading the MacOS build from brave.com gives a .pkg (macOS installer) binary with the refcode in the file and product name
This is bad for a bunch of reasons, inc
it makes it more difficult for us to give advice to users on what downloads to trust, when the true brave downloads look “funny”
We should instead offer the binary as a standard .dmg, unprivileged app. We can solve the refcode problem by creating a different binary/.dmg for each refcode as needed
The text was updated successfully, but these errors were encountered: