N.E.P.T.R

deleted by creator

Flatpak apps cant use namespaces. Flatpak (the software) uses namespaces but Flatpak apps can not.

Yes, I understand Flatpak does some seccomp syscall filtering. It still isn’t enough to consider a secure sandbox where the threat model is that the app is untrusted. Bubblewrap is generally considered a weak sandbox and isn’t “secure by default”, allowing for easy footguns.

LXC/Incus does support proper VMs but it isnt as common.

Neither are really designed to run untrusted apps.

I guess I just don’t understand your question. Explain in more detail.

1. Who is the threat actor? (State, APT, Hackivist, etc)
2. What is their goal (what do they want)? (Money, data, persistent access, blackmail)
3. What tools do they have?

Really think about the Ws (who, what, where, when, how).

If you want to protect against an “advanced” threat actor, you can not do that without multiple layers of isolation, including but not limited to virtualization, MAC (SELinux), namespaces, seccomp.

All protections are meaningless without a clear understanding of what assets you are protecting, the threat you face, and they want from you.

Distrobox is design to be the opposite of confined. Its goal is integration. The container is stripped away as much as possible to allow for sharing host resources.

As it says on the Distrobox website:

Security implications

Isolation and sandboxing are not the main aims of the project, on the contrary it aims to tightly integrate the container with the host. The container will have complete access to your home, pen drive, and so on, so do not expect it to be highly sandboxed like a plain docker/podman container or a Flatpak.

I would also argue calling “plain docker/podman container or a Flatpak” being “highly sandboxed” is also quite wrong and a misuse of those technology.

It uses Docker/Podman which is not a security sandbox. The purpose is app containers, not a security boundary. It shares the sane kernel as the host, which makes kernel vulnerabilities a source of container escapes. Docker (the default) runs as root and could be a source of privilege escalation. Best case is use gVisor or SELinux. Still not a secure sandbox.

Similar problems with Flatpak. Not a secure sandbox. Doesn’t Barely filters syscalls (and in a general way instead of per-app), barely reduces attack surface, granting frequently required permissions often significantly reduces the strength of the sandbox, shares a kernel with the host (and no application kernel like gVisor or sydbox), weak use MAC (like SELinux). Most of this can also be said of the previous 2 container software (and also LXC/LXD/Incus).

Also, don’t use browsers with Flatpak, they have a significantly weaker sandbox because it is missing a layer of sandboxing (namespaces). This makes attack exponential more likely by reducing the need chain another major vulnerability to execute a successful sandbox break.

What you want is a VM. It is designed to be a secure sandbox but needs some configuring.

I would probably go with Artix because it is arch based and therefore you will get updated packages instead of perpetually outdated Debian packages. Then maybe switch out the kernel for the CachyOS kernel and you should be good.

Honestly, I saw it in a video recently that i cant remember. It showed some screenshots of the engineer’s Twitter taking about it.

Artix (Arch w/out systemd) supports many inits. I’d recommend dinit (which is very easy to use) or s6 (which seems more stable on Artix, but less user friendly helper tools). Both are very fast, faster than the other inits.

• There is also Chimera Linux which uses dinit and is very clean imho. A very modern take on making a traditional Linux distro which does things well and uses clean and simple OS software stack.
• Void Linux uses runit
• Devuan (Debian w/out systemd) you can use sysV, OpenRC, or runit
• And obviously there is Gentoo, which supports using OpenRC, with unofficial community guides for some other inits.

I very much doubt it. The only reason Asahi is even installable is because M series Mac were designed to allow installing other OSes. I know that sounds crazy, especially with all the reverse engineering needed to get Asahi to work. But without intentional design on the part an Apple engineer working on the initial M series chip, installing alternative OSes would be impossible.

I think it is worth noting that while what Russia is doing is evil, they are not the only evil players in the game. So many countries are complicit and actively support Israel (monetarily), and most countries do business with USA (mega)companies (like Google, Microsoft, Meta) even with the current regime.

And support for extensions like uBlock Origin.

On Debian I would choose Flatpak because it will be generally much more up-to-date than native packages (which becomes even further true the longer through the release cycle we are).

Anything really. Just use Docker/Podman or LXC and then the base OS won’t matter.

• Ubuntu is still fine
• Debian I have personally used and it is good
• I used openSUSE Slowroll for a while as well
• Fedora server is just as good as RHEL derivatives IMO

Next thing I am looking at is secureblue for Fedora CoreOS. Security matters and a rock solid base with hardened defaults is really nice. It also is Atomic and because it is effectively just CoreOS, you install it with a JSON file (I think). Using the provided example butane file it took like 30 seconds to install. Now I need to customize it further.

I am not trying to say that SailfishOS (or Jolla) isnt a cool project, it just doesnt belong here. Whenever people post Obsidian.md in here I say the same thing for the same reason. Try posting in the Linux phones community. I don’t subscribe to this community to see proprietary software invade the FOSS space.

AOSP is open source, Google’s Certified Android is not. You can contest that if you want.

That doesn’t change that SailfishOS is straight up proprietary for most of its developed compotents. It does not belong in this community. The Wikipedia page for SailfishOS says under license “proprietary with some open source components”.

Sailfish OS is proprietary. It does not belong in this community.

I still dont understand /e/OS. Just use LineageOS. It supports all the same devices and doesnt lag as far behind. You can choose to run an insecure OS if you like (see: all Windows 10 users) but definitely don’t recommend it to others.

You cannot have privacy without at least basic security. Targeted attacks are not the most common kind of attack by long shot. Threat actors scan for vulnerable devices and use automated scripts to execute attacks. Android is one of the most exploited targets. With an outdated OS your browser could be exploited and used to get a sandbox escape, possibly chaining it into root escalation. It all depends on the vulnerabilities found and the longer you wait the more likely for the “stars to align” for the perfect attack. Look at CVE-2025-48593 for an example, zero-click RCE. In recent memory there was also a zero-click RCE utilizing specially crafted MMS, meaning an threat actor could send messages to all phone numbers and try the attack in mass.

/e/OS is by far the most behind on updating security patch levels of the AOSP ROMs (at ~2 months), iode is ~1 and everything else is better than those two.

Privacy without security is not real privacy, it is a mirage.

Security without privacy is like a fortress with cameras inside, a known threat (eg. Gapps Android).

Privacy with security is like a fortess with no known threats at all (eg. AOSP with timely security patches).

Privacy without security is like a fortress where some of the locks have rusted through and if someone tries they can open the doors. It is like replacing the walls with cardboard. “No one can spy on me now” you say in your cardboard castle.

There is no privacy without security. Android is one of the most widely exploited OSes and every month a dozen or more critical severity vulnerabilities are patched. Being 1-2 months behind on security patches is inexcusable for a privacy project.

@Uair@autistics.life

Linux Mint is based on Ubuntu Linux. Make sure you are using a .deb which is meant for Ubuntu (or Debian). Laptop is Desktop, as in they are the same OS.

Either double-click the .deb file and click the install button.

Alternatively you might be able to right-click to get a context menu and click install from there.

Last option, you could install the .deb from the terminal app. Open the terminal, type cd ~/Downloads (if the file is in your Downloads folder), then type sudo dpkg -i ./EXPRESSVPN.deb (replace EXPRESSVPN with the exact file name), press enter and type your password.

All these install options do the same thing.

Don’t worry about CPU architectures. If you dont know what that is, then ypu dont need to worry. If the .deb has x86, x64, or amd64, that is tbe right file. If it doesnt say anything then just choose the normal .deb.

From the description of this repo:

OpenCal is a web-based open-source software designed to make online appointment scheduling effortless and efficient. Whether you’re managing a team or running a business, OpenCal takes the hassle out of coordinating appointments, eliminating the need for endless back-and-forth emails. With OpenCal, you can streamline communication, save time, and focus on what really matters.