Language Selection

English French German Italian Portuguese Spanish

The problem with "sudo"

I have written about biometrics a few days ago and how it's a bad idea to use biometric technologies for security. Today we'll be talking about a different rather popular security technology called "sudo".

Many linux distributions use "sudo" for pretty much everything (if you don't set one manually Ubuntu does set a random root password that you don't even have for example), "sudo" is installed on Mac OSX to allow you to gain full access to the system (espcially on the linux distributions that rely sudo all the GUI tools that modify the system are pretty much wrappers around sudo).

Now I don't want to talk about bugs. Every software has them, why should "sudo" be different, even though bugs in security software are often a lot nastier than in random apps? What I want to talk about is the actual problem I see in using "sudo".

rest here

More in Tux Machines

Android Leftovers

GNOME Shell vs. KDE Plasma Graphics Tests On Wayland vs. X.Org Server

A premium member this week had requested some benchmarks of openSUSE Tumbleweed when looking at the performance of KDE Plasma vs. GNOME Shell in some open-source graphics/gaming tests while also looking at the Wayland vs. X.Org Server performance. With KDE Plasma 5.12 that openSUSE Tumbleweed has picked up, there is much better Wayland session support compared to previous releases. While KDE developers aren't yet ready to declare their Wayland session the default, in my experience so far it's been working out very well but still routinely will find application crashes in Kate and the like when testing under the KWin's Wayland compositor. Read more

Stable kernels 4.15.6, 4.14.22, 4.9.84, 4.4.118 and 3.18.96

Android Leftovers