On Thursday, 9 March 2017 00:51:06 UTC+11, [email protected] wrote: > I realize that it is an integral part of fedora and debian (gross), but > it is a serious security hole and qubes should consider migrating away > from it by maybe choosing another orgin distro. > http://without-systemd.org/wiki/index.php/Arguments_against_systemd > > https://muchweb.me/systemd-nsa-attempt > "The Linux kernel, I believe, is clean. As long as Linus lives, you're > not going to subvert the kernel. Let's just assume that is true for the > sake of argument. If you can't get into the kernel, what is your next > option? You need something low level (PID 1?), ubiquitous, and vast in > scope and complexity. > > This describes systemd perfectly. It was almost like it was designed to > touch as much of a Linux system as possible. It has hooks into some many > different subsystems and APIs that it's almost impossible to build a > modern distro with current software without pulling in systemd as a > dependency. This happened almost overnight, and I think there are > malicious forces at work here." > > Assuming that it is the NSA is unimaginative, it could be literally be > any combination of interests that are doing this - who wouldn't desire > absolute control and absolute power over 99% of linux systems? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 > I am tired of the "virtualization will protect you!" excuse, it only > goes so far and some systemD issues such as using google DNS by default > are simply inexcusable from a qubes perspective (designed to be a secure > OS, but phoning home like that without asking isn't secure at all) > > Linux is about choice, but now the incompetent lennart and red hat are > choosing for you - they are more qualified to make that decision and are > doing it for your own good.
I'm currently in the middle of getting Qubes to work on Slackware, i.e. no systemd. It's taking a bit of time to get everything right though, but I believe that in the end, it will be fully functional. The only reason it's taking so long is because the Qubes Developers don't know the answers to the questions that I asked regarding Qubes. It's either that or they just refuse to answer to protect something that's open-source. As far as I know, slackware will never be using systemd. This is the reason why I am doing it. Someone ages ago said they would be building a template for slackware integrated, but that didn't go anywhere beyond that as far as they had posted. So, I started doing it myself. Soon, there will be a MORE SECURE version of Qubes available, and all updates still coming from qubes-developers themselves, or else it may have to be an off-branch version if their coding doesn't allow for non-systemd in the future. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0de248d0-5b24-4b63-a3dd-109883552751%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
