DebianAndy My threat model is pretty much non existent.
naibed Seems like the majority of responses completely ignored your threat model and defaulted to recommending a hardened distro as usual
I agree with this.
Good advice, I wouldn't have thought to mention: uBO prevents a common avenue for malware or phishing.
In my opinion: OP's Debian has slow updates. Browsers shouldn't be flatpak.
NoahRaketic You are wrong, and you are spreading misinformation. Stop. What you are doing is harmful.
I said that carpet-bombing malware is rare and singled out attacks on a person are even more rare, so users don't have to live under a rock--you can use Linux OP. Informed users have minimal attack surface on Linux.
Johnnyloans Most desktop linux setups don't have vulnerable ports.
NoahRaketic The same is true for Android; this isn't a security feature of Linux.
Johnnyloans e.g. mqtt, ssh, file server, hosting a website, etc
NoahRaketic Not exposing these services does not make desktop Linux safer than Android.
I know. I never said that. I am comparing the attack surface of:
Linux w/ chrome, an office suite, a network router, no services bound to ports, etc
vs Android: email, messenger apps, 2/3/4/5G, SMS, calls, app stores, no router blocking unsolicited inbound traffic, etc.
For a desktop user.
NoahRaketic A desktop messenger would most likely be running as your user
Johnnyloans qubesos sandboxing.
Selinux
NoahRaketic Neither of these are sandboxing, SELinux alone is not suitable to restrict general-purpose, user-facing apps, and Qubes OS is not Linux.
QubesOS does sandbox executable spaces:
https://en.wikipedia.org/wiki/Qubes_OS#The_User_domains:_qubes
"Selinux" i placed on a new line--a separate idea--in response to you saying an app is running "as your user." I know it isn't sandboxing.
"SELinux alone is not suitable to restrict general-purpose, user-facing apps"
I never said: "all you need is selinux to [accomplish a goal]."
NoahRaketic I'm not starting with "Linux is already infected". Do not misrepresent my argument. What I said in the next quote is ...
NoahRaketic The main question is, [let's say] your computer [is] compromised by some drive-by malware or a browser exploit, for instance, how bad would it be for you? If the answer is "very", then it would be an improvement to at least move away from Debian.
You did start your scenario with: the PC is already infected and how bad would that be. I am talking about how hackable linux is. Furthermore, every comment you said about: 'but sandboxing keeps a threat contained' is answering the question of linux security with "Let's say linux has a virus right now, linux isn't safe." Besides, there are protections for that scenario in linux and android--albeit android is better.
NoahRaketic Yes, that's why it is advisable to use a system that architecturally cannot get a virus (one with proper Verified Boot).
Anything is hackable. This is dangerous to say. collisions exist. It is trivial to setup secure boot on linux.
Johnnyloans Is AWS just 95% viruses because Linux is insecure?
NoahRaketic AWS applies hardening to their hypervisors that simply cannot apply to desktop Linux.
You are confused on a hypervisor or any sandbox's role in this. It can enforce memory protections. Hypervisors cannot fix vulnerabilities in the code. Any OS or code i run inside of ESX or AWS will still have its vulnerabilities.
The AWS hypervisor forwards network traffic to the Linux OS and applications running on it. Similar to bare metal behind a router.
Johnnyloans Zero days are extremely valuable. Yes, viruses can spread indiscriminately to everything it sees; however, the virus will be studied and patched with haste--Linux will be secure from the exploit. Likely a waste of the exploit. Conversely, very few people in the word have the knowledge and resources to target 1 person or organization. We aren't a target.
NoahRaketic Not if the vulnerability is unpatched ...
"Will be patched" > "Not if it's unpatched" ??
I'm not sure of your statement. Either researchers will refuse to fight malware or don't have the knowledge to? Both are historically not true.
There is a reason why carpet-bombing malware like wannacry is rare and why most of us won't be singled out by hackers.
NoahRaketic Desktops lack any implementation of full Verified Boot--and Secure Boot ...
Johnnyloans Does nothing unless the virus is already on the device.
NoahRaketic This is entirely untrue.
NoahRaketic If a virus is on the device [verified boot will notice and take action]
Oh.
So, yes, if is a virus already on the device?
Also, I'm curious if you are aware of and can explain what elements of desktop secure boot is so egregiously missing compared to android verified boot. Which you say is "an extremely weak protection."
Johnnyloans Sandboxing helps after your device is already compromised. They have to get inside the sandbox first.
NoahRaketic This is where any credibility you may have had falls apart. This is absolutely not how sandboxing works
Noahraketic: "[If the system is compromised, the virus can influence the app inside of the sandbox]"
Okay.
https://en.wikipedia.org/wiki/Protection_ring
This is like saying: if bad guys are in your house, they can subvert every closed drawer they want.
Of course.
Noahraketic: "A sandbox protects the host if the program is compromised."
First, the virus compromised the program residing inside of the sandbox. The sandbox then protects the host.
Okay, let's review my quote again:
JohnnyLoans "Sandboxing helps after your device is already compromised. They have to get inside the sandbox first."
NoahRaketic I am not talking about a DMZ.
You said a router doesn't prevent devices from being exposed to the world--DMZ.
NoahRaketic It is absolutely essential to treat all remote networking infrastructure as potentially hostile, and getting compromised this way is not user error.
Everyone knows that you can't trust the internet.
I don't think you understand networking. Outbound connections are initiated by our desktop PC. If it is connecting to a hostile server, it is either:
- A virus on our device that initiated this. (Linux is not secure if it is currently infected argument)
- it is user error at the helm
- A 3rd party executable. (3rd party apps aren't the linux OS. Also, we can reliably trust steam or whatever app it is.)
NoahRaketic A user's choice ... is irrelevant to the security of Android itself.
NoahRaketic Not if ... you're on an insecure distro like Debian that falls far behind on patches.
Seems contradictory. Debian is insecure or people don't update so linux is insecure?
Johnnyloans Linux PGP package signing is the same: trusting 1 key and not an entire CA.
NoahRaketic This is not the same at all. You're trusting your distribution's build and signing infrastructure. Android has the capacity to pin signing keys managed by the developer directly.
Linux and android/GOS all have to: "[trust] your distribution's build and signing infrastructure."
Where do you think android got the idea to trust a developer's key? Linux has the same.
Johnnyloans Downgrading attacks: The attacker already compromised your system before the downgrade.
NoahRaketic No.
NoahRaketic This is false. Downgrade attacks are a very real threat.
I'd love to hear how an attacker will install software without arbitrary code execution or physical access. Leave out all of the technical details if you wish--a high level overview will do.
Johnnyloans You need to chain attack the router
NoahRaketic You don't.
You're right--this is optional. However, the alternative is: an attacker would have to MITM or compromise external infrastructure that the target connects to. All difficult tasks.
(Or the user downloads a virus of course, but--again--we don't need Linus to patch linux because a user ran: rm -rf --no-preserve-root / ).
NoahRaketic Only if there is a sandbox, which isn't the case for the vast majority of apps
The only sandboxing done by app developers that I'm aware of is a web browser.
qubesOS sandboxes apps that don't normally.
flatpak
snap
There seems to be a communication disconnect here. There are great resources out there to explain these various concepts further. We can disagree Noah. Take care.