Security.

[gavin]

Hi guys.

I was wondering as i am improving my knowledge every few days in assembler,
what do i look out for concerning bugs[mistakes]  in my code?

Is it safe to assume i should be only worried about the functions we use from c?

Thanks alot.

[Tedd]

There will be as many bugs in your own code as there are in anyone else's. The only difference is that you look at other people's code with fresh eyes. It's good to have someone else check your work, or at least come back to it a few days later when you haven't been thinking about it.

[gavin]

Good point Tedd.

My question still stands tho.
I'll refraise it to ,what type of things should i be looking out for regards the security of my programming.
Secure coding.

Thanks.

[roticv]

Buffer overflow.
Passing correct parameters to functions.

and so on...

[sluggy]

Never trust your input, whether it be keyboard, file, a stream from the web, whatever. When checking your input, don't check for bad things because there could be a million and one of them, instead just check for good input and reject everything else.

[gavin]

I'm going to read about what you said and i'll be back with some examples.
Thanks lads.