News for hackers. Stuff that matters.
Re:Getting Started with WireGuard by outworlder on Tuesday April 07, 2020 @01:42PM (#22805535)
This goes both ways. Userland systems are susceptible to a myriad of attacks that a kernel, being privileged code, is not. We rely on the kernel (plus CPU rings) for most of the security enforcement in a machine, after all.

However, IF that code is compromised, the consequences are much more catastrophic.

Re:Getting Started with WireGuard by greatjack613 on Tuesday April 07, 2020 @01:52PM (#22805640)
That sounds interesting.

Can you elaborate on which attacks userland system are susceptible to that a kernel is not?

Re:Getting Started with WireGuard by eximius on Tuesday April 07, 2020 @09:21PM (#22809225)
A userland process can view/edit the memory of another userland process. Not so with kernel processes.
Re:Getting Started with WireGuard by usr1106 on Wednesday April 08, 2020 @01:02AM (#22810224)
Viewing/editing of another userland process is usually done using ptrace(2). Yama Linux security module prevents that unless you are root to disable it. It is active by default on Ubuntu.

Also reading /proc/nnnn/mem does not work even for your own processes and even though file node protections seem to allow it, not sure where that security enhancement comes from.