My point exactly. A large attack surface means less secure. My point was that Kali isn’t focused on being a secure OS. It is all about the tools. Even without a vulnerability, a secure OS should protect against unknowns.
N.E.P.T.R
I’m the Never Ending Pie Throwing Robot, aka NEPTR.
Linux enthusiast, programmer, and privacy advocate. I’m nearly done with an IT Security degree.
TL;DR I am a nerd.
- 0 Posts
- 23 Comments
Joined 1 month ago
Cake day: November 20th, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Ubuntu font. Idk why but I like it.
PCs aren’t secure. Linux default isnt secure. Kali has so many apps/tools installed by default that it isnt comparable to default Linux. It has massive attack surface and no security design, therefore calling it secure isn’t accurate.
If no effort was put into the security design of an OS, why call it secure?
2·4 days agoOperating systems can function very different. When creating software (like video games) the developer has to understand or use software dependencies which interact with the OS in a number of specific (OS dependent) ways. Stuff like where is app/user data stored, how to connect to the internet, how to display stuff on the screen (2D), how to display complex 3D geometry on the screen fast (3D graphics acceleration), where the host OS stores shared libraries (and what kind of libraries can the software expect to always be available), what security restrictions the host OS has, what filesystem the host OS uses, how to access the keyboard and mouse, how to interact with the kernel (very important).
Since Windows and Linux are so very different, built for different purposes by different developers, it is impossible to take a Windows exe and run it on Linux.
These days, the WINE project, with help from Valve’s fork Proton, is able to run basically any Windows game on Linux with similar performance (if not better because Linux is lighter to run than Windows). It does this by creating a environment for the software/game that provides all of the OS stuff Windows software expects and translating it to Linux specific things.
TLDR: Linux is very different from Windows. Software meant for Windows won’t work natively on Linux (since everything is different). For Windows software to work on Linux, the WINE translates all the Linux specific OS stuff and creates an environment for the Windows software that feels like Windows. Most things work with WINE except exceedingly complex stuff, like browsers which have native Linux versions anyways.
Thanks for some updated context.
What do you mean secure by design? What part of it is secure. Compare it to actually security focused Linux operating systems like QubesOS, Kicksecure, or Secureblue. Literally any OS that supports the Brace tool (made by the creator of DivestOS) is much more secure than Kali Linux. Kali is purpose built for red team work, not being secure (aka reducing attack surface or designing around a threat model).
You mention “sane defaults”. That might mislead someone because it is ambiguous. The terminal
defaultsused to default to a root prompt, exemplifying that it isn’t a distro focused on sane defaults for a desktop distro.Kali is a tool for a specific job. Its meant mostly for hacking or troubleshooting/analysis, being an OS for executing a collection CLI/TUI and GUI utils.
-Edited everything to make myself more intelligible.
It isn’t a secure operating system. It is a toolkit for pen testing and red team hackers. Definitely not a daily driver kind of OS.
For good out-of-the-box nvidia support, I recommend Bazzite.
Idk, but I just enable intelligent autohide.
For nvidia hardware, use nvidia images of Aurora/Bluefin (or Bazzite if you want gaming out of the box). All the OSes I mentioned are based on Fedora Atomic and offer image options for nvidia proprietary drivers. They even signing the kernel drivers, so you can use Secure Boot.
Docker is good when combined with gVisor runtime for better isolation.
What is gVisor?
gVisor is an application kernel, written in memory safe Golang, that emulates most system calls and massively reduces the attack surface of the kernel. This is important since the host and guest share the same kernel, and Docker runs rootful. Root inside a Docker container is the same as root on the host, as long as a sandbox escape is used. This could arise if a container image requires unsafe permissions like Docker socket access. gVisor protects against privilege escalation by only using root at the start and never handing root over to the guest.
Sydbox OCI runtime is also cool and faster than gVisor (both are quick)
Really fun/interesting read.
Nyarch honestly looks like a joke distro and most of its features are not worth IMO.
I used it for a long time as a daily driver and then as my admin workstation. Worked really well, GUI admin panels are nice, and I didnt find anything too difficult.
The weakest link of any secured system is the user. I know that will never change, especially as computers/software become more complicated over time. But I don’t understand why many people argue that “since the user is the weakest link, we don’t need more secure systems, we need better users.” We need both.
Explaination
For anyone who suggests that a user can “just be smarter and not install malware” think about this: do you check read all the commits to the software you install, for each update, and then compile from source. The answers is no. And I don’t think we should need to.
Linux is not secure, it is still meant for tinkerers and by design is very open. This is one of my favorite aspects of Linux, just how open it is. The result though is an insecure system with many attack vectors that are hard to protect against.
For example, I recently wanted to patch a game for mod support. This required me to run a script that i didnt fully understand. I did my best to read it and nothing looked suspicious, but I couldn’t fully understand because I am not a modder for that game.
This script could have done a number of things:
- Added a fake sudo script to the path in the user’s home resulting in privilege escalation.
- Created a user Systemd service that logs everything added to the clipboard or keylog, since that is also possible on Wayland with an LD_PRELOAD attack.
- Create a Systemd service that records the screen to grab passwords.
- Edit the user’s .bashrc file.
- Delete/encrypt every file owned by the user.
- Read and exfiltrate all app data from the $HOME
- Or a combination of multiple other things.
The solution is sandboxing, permission system, secure defaults, and transparency to the user. And of course a way to disable security checks for tinkerers.
My point is that the perfect user does not exist. We (inevitably) use our computers to do all sorts of niche things, the perfect user does not even turn their PC on.
X.Org server has been largely abandoned by maintainers and developers.
Here are some links:
https://www.theregister.com/2020/10/30/x_server_lead_maintainer_declares
https://www.phoronix.com/news/XServer-Abandonware
https://www.osnews.com/story/132507/its-time-to-admit-it-the-x-org-server-is-abandonware/
I would agree but it still heavily relies/requires X11 for many of the core components and apps. Wayland support on the horizon. For now though I wouldn’t recommend anyone use any DE that doesnt support Wayland, since X.Org is has been unmaintained for many years, it is a bloated protocol, and is insecure by design. This is because it was designed 40+ years ago in a time before security was a big concern to developers.
I am not a troll. You don’t need to be an ass.
Just because a system doesnt have a CVE doesn’t make it secure. It needs proper exploit mitigations. Read why Linux isn’t secure here.. The article is written by the lead developer of Whonix OS (Security hardened Debian with a focus on anonymity). If you had checked out any of the references from my previous comments you would have learned more about why I have this opinion.
Kali isn’t any more secure than regular Debian, while also having a larger attack surface, and no kernel hardening, protecting of GUI, or application isolation. What makes it “secure”?