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

Upgrade to the next generation of Brave browser (brave-core) #4

Closed
crazy-max opened this issue Oct 30, 2018 · 7 comments
Closed

Upgrade to the next generation of Brave browser (brave-core) #4

crazy-max opened this issue Oct 30, 2018 · 7 comments
Assignees

Comments

@crazy-max
Copy link
Member

crazy-max commented Oct 30, 2018

Some caveats to note before an upgrade to the next generation of Brave browser.

Passwords are not saved

Brave (as Chromium) stores passwords in such a way that they are encrypted in a way tied to current PC. While the passwords are not kept or left behind on the PC itself, they won't be retrievable when you move to a new PC.

Certificates not portable

Brave (as Chromium) has no certificate manager. It uses Windows certificates manager. So, any certificates you install through the Brave interface are stored on the current local machine and will not be portable.

Some settings and extensions are locked per machine

Brave (as Chromium) locks specific settings to a given PC. This behavior is by design by the Chromium team. If you would like this changed, please open an issue on the brave-core repository. A suggested workaround is to sign in to Brave Safe Storage to restore all settings and extensions but this is not available on the current release of Brave.

And as stipulated in this thread :

Brave reset my browser settings

Sometimes, programs that you install can change your Brave settings without you knowing. For your safety, the browser checks if your settings have been changed every time you launch Brave. If Brave notices that something’s not right in your settings, it will automatically go back to the original settings.

Settings that might automatically get reset

  • Default search engine
  • Homepage
  • Startup pages
  • Pinned tabs
  • Extensions

These issues are specific to Brave due to Chromium's design and not something we can work around without fixes to brave-core.

Import profile data from Muon

The current stable release (0.55) cannot handle migration of profile data from Muon but there is a work in progress. See brave/brave-core#729

Linked threads

@crazy-max
Copy link
Member Author

crazy-max commented Nov 2, 2018

@caspertone2003 I maybe have a clean solution with a patch of Chromium. I will open a PR on brave-core repository when my tests are ok.

@bnscv
Copy link

bnscv commented Nov 14, 2018

Don't know if it is of any help, but Iridium Browser has an official portable version and it's also Chromium based. They recommend creating a shortcut using --user-data-dir=/IridiumUserData.
Links:
https://iridiumbrowser.de/downloads/windows
https://github.com/iridium-browser

@crazy-max
Copy link
Member Author

@bnscv --user-data-dir is not enough. We have to deal with machine ID and encryption otherwise extensions, passwords and settings are not saved across computers. That's why I have created this PR : brave/brave-core#795

@bnscv

This comment has been minimized.

@crazy-max
Copy link
Member Author

@caspertone2003 Post a message here if you want to know : brave/brave-core#795

@crazy-max
Copy link
Member Author

@caspertone2003 Nop it's not. I only wait until my PR is approved before resolving conflicts. No need to work for nothing 🙃

@crazy-max crazy-max changed the title Upgrade to 0.55 Upgrade to brave-core Jan 15, 2019
@crazy-max crazy-max changed the title Upgrade to brave-core Upgrade to the next generation of Brave browser (brave-core) Jan 15, 2019
@crazy-max
Copy link
Member Author

Give it a try : https://portapps.github.io/news/2019-01-31-brave-portable-0.61.5-45/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants