Re: What do you take for secure programming?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This will probably start an arguement but 'secure programming' can be
interpreted a lot of ways. To me it means using functions that arent
known for their security risks. Or using a secure library that has all
'secure' functions. I can go on and on, but at its most basic meaning
I think secure programming is typically reviewing what youve wrote to
make sure their are no obvious vulnerabilities.

Coding and programming mean the same thing to me, one just sounds
cooler ;)

Chris @
cr-secure.net
ehdr.net

Gustavo Rios wrote:

| Hey folks,
|
| i am very new to this mailing list, this is just my first message.
| I wonder what you take for "secure programming" ?
|
| Are you folks aware about the difference between coding and
| programming ? I am sure you plenty of guys/girls here are, but it
| is worthy to refresh it, isn't it ? Don't take me wrong, please,
| but i do ask that cause i have heard about many "secure
| programming" techniques that are simply put misguided. And the most
| amazing is that there are plenty of folks around "buying" many
| wrong concepts. I hope this mailing list may clarify the ones i
| bought myself too (we all do, in different amounts, of course).
|
| Thanks for your feedback.
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB+Lo8Xpi1p4x0qXsRAq7pAJ4hgWeEEQO//q/UNqUqrXwgbc+KwwCfQTJE
vRXGG3JnSdc/DFH8OXfMauM=
=rDqF
-----END PGP SIGNATURE-----