Package Details: iridium-deb 73.0-3

Git Clone URL: (read-only, click to copy)
Package Base: iridium-deb
Description: An attempt at creating a safer, faster, and more stable browser (Stable Channel)
Upstream URL:
Licenses: BSD
Conflicts: iridium
Provides: iridium
Submitter: necklace
Maintainer: necklace
Last Packager: necklace
Votes: 13
Popularity: 0.000000
First Submitted: 2018-04-07 21:56 (UTC)
Last Updated: 2021-01-11 11:43 (UTC)

Dependencies (21)

Required by (0)

Sources (1)

Latest Comments

necklace commented on 2022-06-13 14:10 (UTC) (edited on 2022-06-13 14:14 (UTC) by necklace)

They have removed the .deb builds and no longer list neither debian nor ubuntu on their downloads page: archive

So I guess this package is pretty much dead.

Edit: see for more info. Once they release a .deb package I will update this package.

s0lid7 commented on 2021-11-13 01:57 (UTC) (edited on 2021-11-13 01:59 (UTC) by s0lid7)

I get error 404 in pacman when it tries to download from iridium url. Also url returns 404 if opened in browser. Is it enough to replace the url in pkgbuild, but with which url instead?

necklace commented on 2020-01-28 06:58 (UTC)

So, there's been a release but they haven't made a .deb build yet.

Only flag this as out of date if there's an actual .deb build, check deb/ and ubuntu/ in their downloads:

In the meantime you could test out

gcala commented on 2019-08-01 15:44 (UTC)

version 73 is out:

CommodoreCrunch commented on 2019-01-01 22:49 (UTC)

For the record, I think a better workaround is starting Iridium with the "--no-sandbox" option and using it with firejail to make up for the lack of sandboxing.

jayftn commented on 2018-11-24 08:37 (UTC)

The Iridium project is active again after a hiatus. Could you update the package to match the newest release?

svein83 commented on 2018-08-27 01:25 (UTC)

There's a reason why unprivileged user namespaces are disabled in the kernel. Enabling them will create a larger attack-surface for attackers, and with the amount of bugs in the implementation, it is a BAD idea. This could give the entire internet access to your KERNEL.

If someone doesn't know how dangerous that is, they'd be better off waiting for better sandboxing, than opening their system to even more threats.

HellishINC commented on 2018-06-08 01:50 (UTC) (edited on 2018-06-26 10:47 (UTC) by HellishINC)

sudo echo kernel.unprivileged_userns_clone=1 > /etc/sysctl.d/00-local-userns.conf

sudo sysctl --system

To fix sandboxing issues.