Quote:
Originally Posted by Boofo
Let's just say it will be avoided in the future. 
|
Thats not exactly comforting, nor is it sufficient. Lets review.
Some authors were inserting, albeit harmless, hidden function code in their programs.
Those functions went unnoticed for months. The staff here didn't find the problematic code for some time, even though it affected their own site.
The points out a glaring security hole in the methodology of this site. Anyone with malicious intent, having read this thread, now knows the best way to exploit VB websites: release code here with hidden functionality.
Thats the issue that needs addressing. And you can't dismiss it with a promise that "something" that we don't get to hear about will be done.
VB.Org opened this can of worms by making it public. You've raised a secuity and business data protection issue, the highest concern in all of IT. Many forums being run support real business, not hobbiests. Your answers are insufficient for that population.
You must come forward, sooner rather than later, and explain how you will verify the integrity of the code available here.