Secure Programmer: Keep an Eye on Inputs
An anonymous reader writes "This article discusses various ways data gets into your program, emphasizing how to deal appropriately with them; you might not even know about them all! It first discusses how to design your program to limit the ways data can get into your program, and how your design influences what is an input. It then discusses various input channels and what to do about them, including environment variables, files, file descriptors, the command line, the graphical user interface (GUI), network data, and miscellaneous inputs."
Man, have there been some crappy stories posted today or what?
This one is about as useless and boring as it gets!
Definitely not "stuff that matters".
NO fscking SHIT!
jesus christ on a pogo stick... somebody had to put this in an fsking security magazine?
... hi bingo
Let's see...I'm a programmer...I should really watch my inputs and uotputs....GOSH, THEY NEVER TOLD ME THAT IN FSCKING KINDERGARTEN!!!
*cragen