Changing to Chromium
1 1

40 posts in this topic

Recommended Posts

Based on a quick discussion with @Xaliustoday I think we should overthink Chromium (non) sandboxing. Currently we use --no-sandbox which removes several layers of protection: https://chromium.googlesource.com/chromium/src/+/lkcr/docs/linux_sandboxing.md

 

With enabled sandboxing we run in troubles on arm64 platforms since for whatever reasons there Seccomp-BPF doesn't work. Potential workaround: Disabling this similar to this commit for A64 legacy: https://github.com/ayufan-pine64/linux-pine64/commit/7a78cc22d6a4b79feedc821c9514da59dc3f19de

 

In the end chrome://sandbox should show the first 3 in green and the last 2 in red only:

Chrome-Bumps-Up-Sandbox-Security-in-Chro

 

Any objections against removing '--no-sandbox' from default settings affecting arm64 kernel configs for Pine64 and ODROID-C2 currently?

manuti likes this

Share this post


Link to post
Share on other sites
1 hour ago, Igor said:

Firefox 54 finally goes multi-process, eight years after work began

And Armbian released 5.30 yesterday and ships with Chromium with sandboxing completely disabled (bad) even if we knew better, see my post above from 6 days ago that got ignored. 

 

Is it really necessary to mark @Igorand @zador.blood.stainedin every post where I need an opinion since removing '--no-sandbox' switch from chromium config would require

  • changes to a few kernel configs
  • tests with Chromium later

To be honest: To me the whole 5.30 release came as a surprise especially since a few open issues exist(ed).

manuti likes this

Share this post


Link to post
Share on other sites
On 9.6.2017 at 4:57 PM, tkaiser said:

Any objections against removing '--no-sandbox' from default settings affecting arm64 kernel configs for Pine64 and ODROID-C2 currently?

 

Thank you for all the answers.

Share this post


Link to post
Share on other sites
2 hours ago, tkaiser said:

Thank you for all the answers.

 

Patience. My response time is currently close to one month and going faster, working more than possible, means risking burn out / mental breakdown, which leads to no response at all for longer period of time. This bug affect all humans and workarounds make things only worse.

op1tjaap likes this

Share this post


Link to post
Share on other sites

Qupzilla is a pretty good browser which is multi-threaded. It's also faster than both Firefox and Chrome, and can run JS bloatware like Google Docs etc. I think it strikes a good balance between features and speed for "normal people".

Share this post


Link to post
Share on other sites

While I am pretty content now with the performance of Chromium after all the tweaks that were applied, I never heard of qupzilla before and am testdriving that on my Pinebook atm. It seems a bit more capable compared to the other lightweight options like Midori.

Share this post


Link to post
Share on other sites
3 hours ago, Igor said:

Patience

Nope, I was aware that 'sometimes in the future' there will be a new Armbian major release exchanging Firefox with Chromium. To my surprise it 'happened' few days ago, now we're at 5.30 and ship with a new default browser on new desktop images and a default config that is slightly more insecure than 'needed'.

 

I was asking for opinions since our current 'style' of development (anyone with commit rights to Armbian repo does whatever he wants) is not that great IMO. I was waiting for something like 'yes, let's do it this or that way' to start working on it (changing kernel configs for the affected arm64 platforms, then testing). But then 5.30 happened without any announcement so there was not even an opportunity to check open issues that need to be fixed prior to release.

pfeerick likes this

Share this post


Link to post
Share on other sites
On 14. Mai 2017 at 4:16 PM, hojnikb said:

 

is midori even working stable on arm ?

 

 

Jup, tested it on RPI, OPiZ and some time ago in an chroot on an older armhf tablet.

I use midori on a regular basis. You cannot replace midori with firefox or chromium. Major websites do not render well, or simply won't work.

Since a few weeks logging into my google account simply does not work with midori. I have tested many of these "lightweight" browsers. Midori beats them all, but is far away from replacing Firefox or Chromium.

 

On 17. Juni 2017 at 2:04 PM, rocketpenguin said:

Qupzilla is a pretty good browser which is multi-threaded.

 

Looks nice, I have to test this one and maybe it will replace midori in my package list. :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.