Package Details: brave-bin 1:1.25.73-2

Git Clone URL: (read-only, click to copy)
Package Base: brave-bin
Description: Web browser that blocks ads and trackers by default (binary release).
Upstream URL:
Keywords: brave browser
Licenses: BSD, MPL2, custom:chromium
Conflicts: brave
Provides: brave, brave-browser
Submitter: vorbote
Maintainer: mixedCase
Last Packager: mixedCase
Votes: 412
Popularity: 28.76
First Submitted: 2016-04-06 13:16
Last Updated: 2021-06-17 14:45

Dependencies (8)

Required by (2)

Sources (4)

Pinned Comments

mixedCase commented on 2019-03-11 13:52


Before making your report, please note that the newer GitHub release you're looking at belongs to the "Release Channel" and --isn't marked as prerelease--.

I have a cron running that's checking every 30 minutes if there's a new release and sends me an email if so. If you see the release was tagged in the last couple of hours please give it some time before flagging.

Also please take into account a stable version may be "released" on GitHub but not marked as ready (read, NOT PRELEASE) for a long time.

Another handy tool to check latest OFFICIALLY MARKED AS STABLE version of Brave is to run:


Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

mixedCase commented on 2021-02-22 14:59

@laba I have not, this script pretty much just repackages upstream binaries as you can check yourself. Also AFAIK all Chromium derived browsers use system DNS on Linux and, well, I'm getting with DNS over TLS for I have that set up in systemd-resolved.

I can't find anyone mentioning this in the issue tracker either so it sounds like it's just your system's DNS configured to do that as well.

laba commented on 2021-02-22 10:45

@mixedCase Hi, I noticed a strange think in that brave version. It uses cloudflare dns server with dns over tls enabled even if brave doesn't support neither dns server changing nor enabling dns over tls or https on GNU/Linux. So, have you added it to brave or they have enabled it and haven't said anything ? It's really strange.

mixedCase commented on 2021-02-15 00:24

@anjanik012 @Takuya For an AUR package to go into [community] it requires adoption by a trusted user, which I'm not, don't want to be, and I haven't received word from one interested in adopting the package.

Additionally, this is the binary distribution from upstream, I'm almost certain TUs would rather adopt the package that is built from source, which is

The person who maintains that package keeps a binary repo for it. If you're comfortable with using third party repos and your goal is just to not have to deal with the AUR for updating your browser, might want to look into it.

Takuya commented on 2021-02-14 11:22

@anjanik012 I'm hoping that will change in the near future, Vivaldi already did it, a few months ago, hoping more users will vote this package so we could have it on the official repos :). So the answer to your question, I suppose that will be when this package receives much more votes from the AUR community :D.

anjanik012 commented on 2021-02-14 05:44

Why is this package not in the official repos?

mixedCase commented on 2021-02-05 20:30

@kiankasad I had forgotten to remove it after Brave fixed the SUID sandboxing fallback not working on their side and I was reminded of it by e-mail, mentioned in commit description.

Comment unpinned, thanks for the reminder.

kiankasad commented on 2021-02-05 20:18

I noticed that with the update to 1.19.92-1, the check for user namespaces is removed from Why exactly is this?

Also, with this change in effect, @simonorono's comment can be un-pinned, since the kernel.unprivileged_userns_clone sysctl no longer affects anything.

mixedCase commented on 2021-01-29 20:26

@nowy Thanks for the reminder! That had slipped up my mind. Removed.

nowy commented on 2021-01-28 23:46

I think pepper-flash is no longer needed for brave since it's chromium version upgraded to 88.

gameslayer commented on 2021-01-20 06:53

It's ok, I cleared my AUR cache and re did it and it worked fine