Package Details: brave-bin 1:1.75.180-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: 848
Popularity: 20.49
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-02-21 22:41 (UTC)

Dependencies (8)

Required by (8)

Sources (4)

Pinned Comments

wknapik commented on 2025-02-06 18:10 (UTC)

alerque commented on 2021-11-27 03:11 (UTC)

@ant0n et all, lets keep the comments here about packaging issues, general Brave usage issues should go in another forum to not clutter up this comment space. I'm deleting comments that have no relation to packaging. Grey areas like crashes that could be blamed on Arch can stay until proven otherwise, but things like how to configure Brave to handle popups or site X or whatever just don't belong here. Thanks for understanding.

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 60 Next › Last »

alosarjos commented on 2021-08-03 10:23 (UTC)

The Chromium team has released the new version with the corrections. I'm not sure if Brave will make a new 1.27 rebased release or if they will wait until 1.28 which is due for next week.

chandradeepdey commented on 2021-08-02 17:19 (UTC)

@francoism90 assuming you are talking about Arch Linux only and not other distributions whose users use AUR for some reason.

It is impossible to say which systems/users are using systemd-resolved.

Still a fraction of users, Arch offers a variety of ways to set up name resolution.

can't assume that they want to adjust their system

Why not? I don't see anything wrong with "if there is a regression, either hold the package yourself or apply the available workarounds"

francoism90 commented on 2021-08-01 07:43 (UTC)

@chandradeepdey It is impossible to say which systems/users are using systemd-resolved. I think there are many, and you can't assume that they want to adjust their system (resolve) settings just for Brave.

duhdugg commented on 2021-07-31 16:10 (UTC)

Fair points, @alosarjos. The package is appropriately flagged as out-of-date currently. I think most types of AUR users are covered.

chandradeepdey commented on 2021-07-31 16:09 (UTC) (edited on 2021-07-31 16:10 (UTC) by chandradeepdey)

@duhdugg oh lol. the workaround was known for 10 days and I found out today. @alosarjos ¯\_(ツ)_/¯

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

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 60 Next › Last »