Explore >> Select a destination
|
You are here 
|
poolp.org | ||
| | | | |
venam.net
|
|
| | | | | You've certainly heard of daemons, those processes that lurk in the background and do what they're supposed to do. You might even have written and run programs that are daemons. Today we'll talk about them, those daemons ({day,dee}mon), what there is to know about their mechanism and details. A big generic overview of daemons on ... | |
| | | | |
nfil.dev
|
|
| | | | | This post documents my attempts to manage to jump (or return?) from kernel-space to usermode in my Rust kernel so that it can do what a kernel is supposed to actually do: give the CPU to user programs. That's pretty exciting! In the next part, we'll even take control back from the programs so that we can implement a scheduler. | |
| | | | |
xcellerator.github.io
|
|
| | | | | In all the playing around I've been doing with Linux kernel modules, I decided to see what would happen if you tried to load one from a Docker container. It turns out that privileged containers (or just those with CAP_SYS_MODULE) are able to use the sys_init_module() and sys_finit_module() syscalls - which are what's used to load kernel modules. As all containers share their kernel with the host (unlike VMs), this clearly results in yet another complete system compromise. | |
| | | | |
0pointer.de
|
|
| | | Posts and writings by Lennart Poettering | ||
