in reply to How many security holes can you find?
Not to be a party-pooper but did you have permission to post that code? If someone originally paid to have that written and are paying you to write a new version, they may own the copyrights to this version and the one you are writing. Clearly posting the code in it's entirety (whether it is full of holes or not) is bound to infringe their copyright.
I only bring it up because the OSS community and the GPL itself is being tested now by this whole SCO debacle and while I am all for free (as in speech) software, I feel that the community as a whole still needs to respect the rights of those who own and maintain "closed-source" software.
Peace
|
|---|