Explore >> Select a destination
|
You are here 
|
michaelneuper.com | ||
| | | | |
vlad.website
|
|
| | | | | The default C string handling functions have a lot of problems. The biggest of these issue is the fact that they are unsafe, in the sense that they can lead to buffer overflows by copying something past the end of a string. There are safer versions, such as strlcpy, but they also have their own issues, such as implicit truncation of strings. I needed a more reliable set of string handling functions, so I created pstr, which is a set of functions that allows you to more easily work with static C strings while preventing buffer overflows and truncation, so you don't have to worry worrying about safety as much. pstr has two principles: | |
| | | | |
manybutfinite.com
|
|
| | | | | Last week we looked at how the stack works and how stack frames are built during function prologues. Now it's time to look at the inverse process as stack frames are destroyed in function epilogues. | |
| | | | |
blog.nuculabs.dev
|
|
| | | | | Hello, In this article I present you the solution to nice and short cracking challenge from Root-Me. After opening it up in Ghidra, I saw that the challenge is easy to solve, all you need is to find the password, which is in plain text. Basically just copy paste and you get the flag, but wait, there's a twist! I should have learned my lesson from the other challenge from Root-Me, which also had a twist. | |
| | | | |
cookie.engineer
|
|
| | | Linux Assembly Part 1: Syscalls | ||
