|
You are here |
chao-tic.github.io | ||
| | | | |
pwning.systems
|
|
| | | | | I'm writing this post because I often hear that kernel exploitation is intimidating or difficult to learn. As a result, I've decided to start a series of basic bugs and exercises to get you started! Prerequisites Knowledge of the Linux command line Knowing how to read and write basic C may be beneficial Being able to debug with the help of a virtual computer or another system Able to install the kernel module compilation build requirements A basic understanding of the difference between userland and kern... | |
| | | | |
manybutfinite.com
|
|
| | | | | After examining the virtual address layout of a process, we turn to the kernel and its mechanisms for managing user memory. Here is gonzo again: Linux processes are implemented in the kernel as insta | |
| | | | |
0x434b.dev
|
|
| | | | | Continuing to walk down Linux Kernel exploitation lane. This time around with an unanticipated topic: DirtyPipe as it actually nicely fits the series as an example. | |
| | | | |
danq.me
|
|
| | | Quick Links Download from RubyGems.org Source on GitHub Mobile-OTP standard About the project This RubyGem implements the Mobile-OTP standard in Ruby, allowing you to write Ruby (and Rails) powered servers and client implementations. This enables you, for example, to implement strong two-factor authentication into your web application, where your users use their mobile phones as a remote token. Installation gem install motp Server Implementation For each user, come up with a secret and allow them to specify their PIN. Store both. When they use your system, ask them for the One-Time Pad. They can get this by using their mobile phone (which they've already configured with the secret) and entering their PIN. require 'motp' Motp::check(secret, pin, otp) Returns ... | ||