@ 4:13: This actually would not be a buffer overflow. Because 'char name[4]' means 5 elements (in C and C++) because you have to include the 0th element.

Great video!

I was charged as an accessory to murder at the age of 10 because I used my iphone 16 to film a good friend of mine in a fight, and he ended up killing the his opponent, with a body-slam🏠🏡

Awesome videos. Come back! The World needs you man...

Keep it up man, loved the video

Thank you, omw to the atm rn

perfect !

"buffer overflow" -rare wubbox

Thanks, man! Your content is wholesome :)

Great explanation

great video bro!

really good explanation

those endians...

ty king

Thank you very much after I searched a lot of video tutorials I still didn't understand until I came across your video, it's so easy to understand, easy to visualize

Great video, Thanks!

These videos are truly awesome. I have learned so much from them. I wish more people would use diagrams like yours to talk about these low-level topics. I aspire to teach as well as you do.

The real problem is people try to write code without using the basic functions/loops of the C and C++, which these languages originally designed in mind with. When I deal with buffers, I always and always use them in a for loop, which is the best loop of all, I practically don’t use any other loop in my codes, almost for 15 years I only used for loops. Just keep track of your buffer size, array size, you’ll be fine.

One of the best video for the endianess. Cause u included the topics where people get stuck.

which psycopath thought that little endian would be a good idea

Thank you very much !

Great video 👏

Great video man

Mr. Doug told me to come here

Thank you very much for explanation!

Seriously you have to come back

Why have you stopped making videos. I just discovered you

great content

pretty good video

I thought this has something to do with India lol

hi aaron, i dont mean to be rude but i think the binary representation of 16 is wrong it needs an extra zero, tnx

Good video, but I didn't get, how can we test byte by byte in the real world

It is simple, in little-endian, multi-byte values are stored such that most significant bytes are stored at a higher addresses and least significant at lower addresses (this is in fact the natural way of storing things).

I just discovered your channel and you deserve more views !

thank you!! you just save my exam tomorrow!!!

The only video in this channel, but it's really a gem!. Kudos to you. Hope you get more time to publish videos like this.

Dude you are the best. suscribe

this channel is like a precious gem

greatest video on buffer overflow

thanks man. This is really helpful

Great presentation !

Short video Crystal clear explanation Great job mate

Pls come back ❤

You are intelligent and talented!

It makes sense to me that data would be executable by default. Code is just another form of data (assembly opcodes are just numbers after all). Unless you dedicate memory or circuitry to it, the only obvious way to know whether a program is reading code or data is by essentially setting some kind of flag in the program and update it whenever a program starts or ends - to keep track of whether the program saw a "start of executable section" or "end of execution" section. It would be expensive to check every single byte between the current and target locations before executing a jump, so all we can do is put it in the normal program code. Its unsurprising that an exploit that alters program control can be used to skip over part of the program control process.

Simple and awesome. Thanks

it's helpful!

not sure if this comment would even reach you, but man your videos are amazing. hope you still find the passion in making more of these

what an amazing explanation. Dude make more videos. The professionals need you to make their life easy.

Thank you for byte-wise guessing. Now I will do bitwise guessing so that I can move from 4294967296 -> 1024 -> 64 (2*8*4)