Package Details: brave-bin 1:1.78.97-1

Git Clone URL: https://aur.archlinux.org/brave-bin.git (read-only, click to copy)
Package Base: brave-bin
Description: Web browser that blocks ads and trackers by default (binary release)
Upstream URL: https://brave.com
Keywords: brave browser
Licenses: BSD, MPL2, custom:chromium
Conflicts: brave
Provides: brave, brave-browser
Submitter: toropisco
Maintainer: brave
Last Packager: brave
Votes: 875
Popularity: 19.37
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-05-07 17:04 (UTC)

Dependencies (8)

Required by (9)

Sources (4)

Pinned Comments

brave commented on 2025-04-25 13:00 (UTC)

Latest Comments

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 61 Next › Last »

alosarjos commented on 2021-07-31 14:48 (UTC)

I'm not sure it's a good idea to update the package and then show a message telling users to review/alter their system settings to keep Brave working.

We are taking for granted that all Brave-bin users should know how to:

  1. Review their system settings to know if they are or not affected
  2. In case they are, modify those settings that have been working perfectly and still do for everything else
  3. Not only modify, but understand what those modifications mean

Asking people to change their working system settings because of a single package that will be fixed in a matter of days, doesn't sound good to me.

Instead asking the people with the technical skills to know if they can upgrade the package to simply use the provided PKGBUILD in the comments, is by far a safer solution.

Let's remember that there are a lot of user-friendly arch based distros out there where people is using AUR, without knowing even what DNS resolver they are using, and the probably don't even care as long as it works.

duhdugg commented on 2021-07-31 14:20 (UTC)

I confirmed the solution provided by @chandradeepdey on a fresh VM install with the archinstall script's default networking option selected (this is as close to a "default" configuration as possible, although most users are probably still used to configuring their network manually during install). Removing resolve [!UNAVAIL=return] from /etc/nsswitch.conf fixes the issue even with systemd-resolved running (no restart required). Someone in the chromium thread also pointed out that this is specific to a combination of systemd-resolved and libnss_resolve.

@chandradeepdey also brings up a good point regarding security. Given everything we know about this issue right now, I don't think the update should continue to be blocked. There should be a post_install function in this package which notifies users of the problem with resolved+libnss in the current version.

chandradeepdey commented on 2021-07-31 12:28 (UTC) (edited on 2021-07-31 12:29 (UTC) by chandradeepdey)

I think something as adversary facing as Chromium should not be blocked like this. Chromium 92 has multiple security issues fixed.

  1. As acknowledged here already, systemd-resolved is only used by a fraction of the userbase.
  2. The issue can be easily worked around by removing systemd-resolved from /etc/nsswitch.conf and setting it to something like hosts: mymachines files myhostname dns*.

*DNS resolution still happens via resolved, dns uses /etc/resolv.conf which (if symlinked correctly) contains the address of the systemd-resolved stub resolver. I had this idea because Ubuntu does not use the nss module by default and there is no issue there.

alosarjos commented on 2021-07-30 15:26 (UTC)

Filled an issue on the brave github to try to give awareness of the problem hoping they can release a fixed Brave ASAP

https://github.com/brave/brave-browser/issues/17263

alosarjos commented on 2021-07-30 13:44 (UTC)

This is the issue I'm following at least:

https://bugs.chromium.org/p/chromium/issues/detail?id=1221442

Fix is merged into Chromium, but now we have to wait until next Chromium release (Which sould be next week), and then for a new Brave release based on this Chromium release. Which I hope we can get soon after.

For example the official Arch Chromium package has a couple of patches applied that can't be applied here.

Until that the update is frozen. You can update manually if you don't want to wait by using @duhdugg PKGBUILD: https://gist.github.com/duhdugg/3cb48d09b5f3c31adbc06c55efb466c8

francoism90 commented on 2021-07-30 10:37 (UTC)

Could you guys please link to these issues? :)

Th30 commented on 2021-07-29 15:04 (UTC)

@alerque: Indeed, I do not use systemd-resolved but Unbound.

alosarjos commented on 2021-07-29 09:53 (UTC)

Looks like the fix could arrive at Chrome next week. If that happens let's hope Brave makes a new release rebased on it.

alerque commented on 2021-07-29 08:57 (UTC)

I've just tested 1.27.109 and the situation has not improved. With systemd-resolved in the mix it freezes up hard on startup with an error about not being able to reach the update check site. If I disable systemd-resolved and just use the glibc resolver it works fine.

I'm on the fence as to whether to bump this or not until that is fixed. It's clearly an upstream bug and only affects a subset of users, but I think given how common it is its probably not a good idea to force this through yet. Users that want it can bump the version easily enough themselves since no packaging changes are require other than a version bump and skipping the checksum.

alerque commented on 2021-07-29 07:03 (UTC)

@Th30 What DNS resolver is your system using?

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 61 Next › Last »