| 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: | alerque (alosarjos) |
| Last Packager: | alosarjos |
| Votes: | 821 |
| Popularity: | 17.69 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2024-11-20 18:19 (UTC) |
@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 1.1.1.1 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.
@mixedCase Hi, I noticed a strange think in that brave version. It uses cloudflare 1.1.1.1 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.
@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 https://aur.archlinux.org/packages/brave
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.
@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.
Why is this package not in the official repos?
@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.
I noticed that with the update to 1.19.92-1, the check for user namespaces is removed from brave-bin.sh. 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.
@nowy Thanks for the reminder! That had slipped up my mind. Removed.
I think pepper-flash is no longer needed for brave since it's chromium version upgraded to 88.
It's ok, I cleared my AUR cache and re did it and it worked fine
Pinned Comments
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.