Package Details: slimjet-browser 22.0.4.0-1

Git Clone URL: https://aur.archlinux.org/slimjet-browser.git (read-only)
Package Base: slimjet-browser
Description: A lightweight Browser based on Blink (removed setuid-sandbox)
Upstream URL: http://www.slimjet.com
Licenses: MIT, custom:freeware
Provides: slimjet-browser
Replaces: slimjet
Submitter: ergotamin
Maintainer: ergotamin
Last Packager: ergotamin
Votes: 1
Popularity: 0.086708
First Submitted: 2018-12-08 16:03
Last Updated: 2019-04-01 19:19

Dependencies (25)

Required by (0)

Sources (4)

Latest Comments

1 2 Next › Last »

ergotamin commented on 2019-04-01 19:21

*updated, thanks for the hint

StratosL commented on 2019-04-01 17:40

In /usr/bin/slimjet-browser, line 13 should be "/usr/share/slimjet/flashpeak-slimjet ..." instead of "/usr/share/flashpeak-slimjet ..."

ergotamin commented on 2019-01-20 14:29

:), just for fun, visit chrome://sandbox/ to verify the usage of namespace-sandbox ...

StratosL commented on 2019-01-20 13:47

@ergotamin: Thank you for your prompt reply. I'll now install it and test it.

Edit 3: I verified "namespace-sandbox". However, when I try to start if from Cinnamon menu, it does not start. Hmmm. Something about "enabled sandbox"? How do I do that? If I start it again from the terminal with "sudo", it works for that session. It has also created an extra root user as mentioned.

Edit 2: "any user will be able to start SlimJet with an enabled sandbox" -- you lost me there.

Edit 1: After installation, it still won't start initially from the menu. Needs terminal the first time.

Starting with regular user, gives error in line 13 of /usr/bin/slimjet-browser, message /usr/share/flashpeak-slimjet "no such file or directory"

Starting with sudo, it starts but you get [17327:17327:0120/163921.544243:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process. [17253:17393:0120/163921.591646:ERROR:object_proxy.cc(615)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files [17253:17253:0120/163922.109807:ERROR:global.cc(1685)] Failed to decrypt!

ergotamin commented on 2019-01-20 12:51

@dicaiopolis : Should be fixed now... skipping all checksums now, because i want to provide and up-to-date package and want to have the process as self-sustained as possible.

@StratosL : The hint means that in the process of packaging, the setuid-sandbox is removed. I fully support your statement "How SlimJet required root-access". Thats why I removed it in this package (it's deprecated anyway, the chromium- documentation points that out), in change for the more advanced namespace- sandbox, which will be used if the setuid-sandbox is not available, but only if your kernel allows unprivileged users to use this feature. (which is for ArchLinux is not the default case.) The difference is: I added a config-file for sysctl to allow unprivileged users this feature (unprivileged means a any non-root user). So from this point, any user will be able to start SlimJet with an enabled sandbox, without requiring SlimJets sandbox to have root-access.

I hope i could point it out for you :)

Best Regards

StratosL commented on 2019-01-20 12:17

Hi there, what is the meaning of ¨removed setuid-sandbox¨, security-wise? I don΄t like how slimjet required root access. How is your compilation different than ¨slimjet¨?

dicaiopolis commented on 2019-01-18 21:55

I'm getting the following error: ==> Validating source files with sha256sums... slimjet-browser-x86_64.deb ... Skipped LICENSE ... Passed flashpeak.patch ... Passed slimjet-browser ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build slimjet-browser.

ergotamin commented on 2019-01-11 11:49

Thanks for the question, this is for the reason that i personally use a pure root Environment, and by providing the slim-root Dummy User, i am able to run slimjet with the userns sandbox as root (indirect, of course).... You can just ignore or delete the User, up to you

Best regards

papakilo commented on 2019-01-11 11:29

Why your package creates a new user with administrator privileges?

ergotamin commented on 2018-12-19 17:55

sorry for the delay ... everything should be fixed now !