Skip to content
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

optional updates #211

Closed
tommycarstensen opened this issue May 18, 2018 · 5 comments
Closed

optional updates #211

tommycarstensen opened this issue May 18, 2018 · 5 comments

Comments

@tommycarstensen
Copy link

I was just forced to install the latest update and was unable to continue my browsing session before doing so. Could you please make the upgrades optional unless they are security updates? Thanks!

@srirambv
Copy link
Contributor

You can follow the steps mentioned here. This is applicable for browser-laptop and not on brave-browser.

@bbondy bbondy modified the milestones: Releasable builds, Dupe / Invalid Jun 14, 2018
@cbehan
Copy link

cbehan commented Jun 5, 2019

All of the discussions about auto-updating don't even define what that is.

  1. I have brave installed to a directory that is only writeable by root.
  2. Setuid bit on the brave executable is off.
  3. I run brave as an unprivileged user which is how a browser should always be run.

Now you can't honestly tell me that Brave has a team working round the clock to find kernel exploits that allow updates to still be installed in the above setup. Updates must already be enabled only for specific use cases. Can you be please be transparent about what those are for the benefit of people like me who are considering switching to Brave? Thanks.

@bsclifton
Copy link
Member

bsclifton commented Jun 24, 2019

@cbehan the original post was by a user of the old Electron based browser (accidentally posted here instead of the browser-laptop repo). An un-supported work-around was linked to

On the live product:

  • For Linux, auto-updates aren't happening. You'll have to do this yourself via apt/rpm/dnf/etc
  • For other platforms, updates will happen. It may be possible to disable updates, but that is not something we support

All of this said, what exactly are you asking, @cbehan? (having trouble understanding what is the question or ask)

@cbehan
Copy link

cbehan commented Jun 26, 2019

I'm asking what the conditions are for Brave to download an update. You have answered much of the question by saying that on Linux it never will (regardless of how many privileges the user has).

But are there other checks besides the OS and CPU? Right now, I'm imagining a Windows or Mac user who compiles his or her own executable. Is Brave smart enough to detect that the compilation flags were not the official ones and that therefore this custom build should not be replaced by the Windows or Mac updates online?

I'm sure there is a better place for discussing this. But the concern is fundamental enough that it should probably be on one of the wiki pages.

@bsclifton
Copy link
Member

bsclifton commented Jul 17, 2019

@cbehan

  • compiled builds won't check for updates

  • Updates on Windows or macOS require an official executable (release/beta/dev/nightly channel) and they know an update is present because a request is sent to Brave. Upon receiving the response, Brave will start to update itself... but requires the user to exit/relaunch (green icon shown in hamburger button, restart button also shown in chrome://settings/help) to finalize the process

A lower level description of the process (which could use updating) is on our wiki at:
https://github.com/brave/brave-browser/wiki/How-update-works

@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants