News for hackers. Stuff that matters.
Re:Flatpak – a security nightmare – 2 years later (2020) by syockit on Sunday March 21, 2021 @08:15AM (#26529850)
I don't have experience with MacOS to comment, but at least in Windows it's pretty much the same: as soon as you get the user to click OK in the UAC prompt, everything is fair game after that. Is there even a model desktop OS we can look to as being secure? Chrome OS perhaps?
Re:Flatpak – a security nightmare – 2 years later (2020) by Koliakis on Sunday March 21, 2021 @09:33AM (#26530290)
I've been experimenting with Qubes and it's the only OS I'm aware of that adequately addresses this issue. It's not usable for non-technical users though without a lot of learning/training and it can be a bit tedious to use sometimes.

I have all my personal data in its own isolated VM (Qube). I do all my browsing in another VM, which has its own home folder and no access to my personal VM. All my sensitive stuff like banking is done in its own VM. Every proprietary application gets its own VM (mainly Teamviewer and VS Code).

So if I do happen to run some program that's malicious, it has effectively zero access to anything sensitive unless it's aware of Qubes and knows how to break out of the hypervisor (non-trivial).

Re:Flatpak – a security nightmare – 2 years later (2020) by __turbobrew__ on Sunday March 21, 2021 @03:45PM (#26533279)
How is this different than running FreeBSD with a jail per application?
Re:Flatpak – a security nightmare – 2 years later (2020) by Koliakis on Sunday March 21, 2021 @05:51PM (#26534442)
Harder boundaries? From what I understand, a hypervisor is much harder to break out of than a FreeBSD jail and provides more isolation between the VMs.
Re:Flatpak – a security nightmare – 2 years later (2020) by GordonS on Sunday March 21, 2021 @09:14AM (#26530147)
In some ways, things are better there on Windows here, because of code signing - if something isn't code-signed, you get a more prominent warning. I often wish for something like this on Linux (and it would have to be easy to use - no compiling your own kernel with additional modules for example).

It's really not easy to get a code signing certificate fraudulently (or to steal someone else's), but of course, there are some issues with code signing: for example, certificates are relatively expensive, so very few OSS/free software projects sign binaries.

Re:Flatpak – a security nightmare – 2 years later (2020) by my123 on Sunday March 21, 2021 @08:23AM (#26529894)
For Windows, there are the Win32 apps that you talk about, which aren't sandboxed.

And there are the modern applications from the Microsoft Store or self-distributed as msix/appx which are properly sandboxed.

Re:Flatpak – a security nightmare – 2 years later (2020) by pjmlp on Sunday March 21, 2021 @08:56AM (#26530047)
Win32 applications can also be sandboxed, when packaged as MSIX.

Windows 10X original roadmap was to merge both sandbox models, and it is also part of Project Reunion goals.

Re:Flatpak – a security nightmare – 2 years later (2020) by pdimitar on Sunday March 21, 2021 @08:24AM (#26529897)
People have praised Qubes OS for its security in the past but I've never tried it.
Re:Flatpak – a security nightmare – 2 years later (2020) by GekkePrutser on Sunday March 21, 2021 @02:32PM (#26532680)
I have. It's very secure but too much towards security on the security Vs usability scale for my liking.

I use it for specific purposes like possibly hostile browsing environments but I'd never consider it for a mainstream system to work on.