Explore >> Select a destination
|
You are here 
|
abstractexpr.com | ||
| | | | |
crocidb.com
|
|
| | | | | Clarifying the shebang (#!) mechanism: A step-by-step look using strace and kernel code shows how Linux handles script execution directly, revealing the shell isn't involved initially. | |
| | | | |
blog.malwaremustdie.org
|
|
| | | | | MalwareMustDie (MMD) is a whitehat workgroup to reduce malware, this blog advocates research on new malware threats & Linux malware. | |
| | | | |
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. | |
| | | | |
blog.nuculabs.dev
|
|
| | | I've recently finished reading a book called Practical Binary Analysis which I consider a state of the art book (review will come soon) and I would like to post my solution to the crackme found in chapter 5. | ||
