back

by stevekemp·1y ago·view on hn ↗
This is a hard sell:

      sudo chown root electron/chrome-sandbox
      sudo chmod 4755 electron/chrome-sandbox
Installing a new setuid root binary? I guess that the sandbox process is small, and not really electron, but just hearing "electron" and "setuid" in the same sentence is enough to make me run away!
1 comments
It's known issue for any application that uses Electron but don't have enough money to get Ubuntu to whitelist it (I believe?)

I heard that this can be worked around if someone submit a package to the distro. I have no experience in packaging for distros, and help is welcomed!

> It's known issue for any application that uses Electron but don't have enough money to get Ubuntu to whitelist it (I believe?)

for the laymen can you cite a source for this?

> I have no experience in packaging for distros, and help is welcomed!

Do you have an issue tracking what is currently happening and what you want to happen instead?

I'm really perplexed by your talk about "having enough money for allowlisting" because I have never heard of anyone paying a distro any amount of money for any purpose, and that's not even getting into the obvious fact that Ubuntu isn't the only distro out there

Sure! Sorry for saying something probably totally wrong -- I don't know much about packaging at all. I opened an issue here https://github.com/neomacs-project/neomacs/issues/80
What happens uf you don't setuid it?
Electron won't start. Or it could start with --no-sandbox flag but that is even more insecure.
Won't it be more reasonable to run it inside bubblewrap then?