News for hackers. Stuff that matters.
Re:Malware in open-source web extensions by Kalium on Tuesday February 16, 2021 @08:02PM (#26161236)
You can always just accept the risk.

Or you can not, and work to control your supply chain. Host the artifacts yourself and choose carefully which ones you use.

There is no magic bullet, just boring and painful risk-control processes. But they do help.

Re:Malware in open-source web extensions by SilverRed on Tuesday February 16, 2021 @09:20PM (#26161832)
The future is sandboxed apps with flatpak. Who cares if Spotify is malware when it can't access anything.

Wayland, SELinux, Flatpak, PipeWire. These will save us or at least reduce the problem of evil maintainers.

This model has been tried and proven for over a decade on mobile. What we call malware on mobile is simply the app doing bad things with what you enter in to the app itself and not the desktop class "steals all your data and then encrypts it"

Re:Malware in open-source web extensions by cycomanic on Wednesday February 17, 2021 @04:56AM (#26164675)
Except that often the sandboxed apps are also a nuisance to work with. They don't pick up themes from the desktop, keyboard shortcuts don't work anymore (if you have e.g. set some global shortcuts), exchanging data with other programs can be a pain as well...
Re:Malware in open-source web extensions by SilverRed on Wednesday February 17, 2021 @08:04PM (#26174128)
They are only a nuisance right now. Almost all of the issues you encounter are minor implementation problems and not fundamental issues with sandboxing or flatpak. Things are getting better.
Re:Malware in open-source web extensions by eeZah7Ux on Wednesday February 17, 2021 @08:50AM (#26166227)
> The future is sandboxed apps with flatpak.

If the sandbox is configured by the same person or organization that writes the code there's no improvement in trust.

That's why package maintainers have a role in Linux distributions.

Re:Malware in open-source web extensions by flyinghamster on Wednesday February 17, 2021 @08:06AM (#26165858)
I'd like to agree, but as always, the problem is the security/ease-of-use tradeoff. SELinux can be a nightmare to deal with, particularly if you're compiling an application from source and you want to take advantage of it (and even if you aren't, it can lead to mysterious failures). I managed to make Asterisk work in SELinux, until I tried to add a Bluetooth channel module to the mix. At that point, I was backed into a corner; there just didn't seem to be a way for me to let Asterisk access Bluetooth with SELinux running.
Re:Malware in open-source web extensions by andrey_utkin on Saturday February 20, 2021 @07:08AM (#26203547)
So you count on SELinux. Who maintains SELinux policies for you, so that it knows what is allowed to a program and what isn't? It's people just like other software maintainets.

There is no way around having to trust somebody else.

Re:Malware in open-source web extensions by bscphil on Wednesday February 17, 2021 @12:07PM (#26168656)
No. The solution to the problem of evil m̶a̶i̶n̶t̶a̶i̶n̶e̶r̶s independent software vendors is maintainers.

See http://kmkeen.com/maintainers-matter/

Re:Malware in open-source web extensions by SilverRed on Wednesday February 17, 2021 @08:02PM (#26174115)
Maintainers do not review code. At best they test it to make sure it works. The Debian maintainers let in a timebomb borderline malware in to the xscreensaver package without them noticing it.

Maintainers do not have the time or ability to check for even intentional malware let alone security bugs.

Re:Malware in open-source web extensions by swiley on Wednesday February 17, 2021 @04:45AM (#26164570)
Encouraging people to run random binaries from strangers is probably worse.