|
You are here |
cocomelonc.github.io | ||
| | | | |
goggleheadedhacker.com
|
|
| | | | | This tutorial will show how two methods of implementing the AES algorithm work. It will also demonstrate how to identify these methods in Assembly when reverse engineering an application. | |
| | | | |
begriffs.com
|
|
| | | | | Obtaining session keys to decrypt packet captures | |
| | | | |
www.da.vidbuchanan.co.uk
|
|
| | | | | [AI summary] The CTF writeup details the process of solving a cryptographic challenge involving AES key recovery through side-channel attacks. The key was recovered by analyzing timing leaks from the AES decryption process, specifically the doSboxInv function's execution time. The recovered round 10 key was then used to invert the AES key schedule to obtain the original encryption key, which was the flag. The writeup also discusses the challenges of directly recovering the original key due to timing noise and the importance of using statistical correlation to identify the correct key. | |
| | | | |
wsummerhill.github.io
|
|
| | | I'm going to cover an example of how to perform a DLL sideload from start to finish using a C++ payload and a legitimate DLL commonly found on disk. The specific technique covered is known as "DLL proxying" where we use the legitimate DLL along with a malicious DLL which exports all the functions that the legit DLL to execute properly. | ||