Sounds like a good solution if a problem like this is ever found.

Good to see this new policy in place. Great news.

I must have missed the bit that says you will close the thread - what exactly does this achieve besides denying anyone further support ?

Closing the thread helps to prevent ppl posting exploits for example.

Um, right ...... I think that's a little far fetched tbh. I can imagine people are now goinig to create new threads when they want support for said hack (and could also post exploits in a new thread if it comes to that). It's your policy I suppose, but I can't see the benefit in closing the support thread. The main thing is to remove the files, which has happened. Just my opinion. :)

Any policy will need refining, but putting the code on hold and trying to avoid the exploit being spelled out till fixes are applied is a good idea.

Leaving the thread open will lead to members speculating as to what the exploit is - a bright spark will probably inadvertently post it and before it gets removed people would read about it. Like we said - if we get a fix, we will send it to the people who have already installed it (rather than posting it in the open for example). The aim is to do damage control, not to make things worse.

very good !

I like the policy and the fact that exploits are not fully discussed in public. I am just glad I have always clicked "INSTALL" and I think this policy will further encourage all members to always click "INSTALL" with every hack they use.

I think this is a great idea!

I would also encourage the vb.org staff to write a short tutorial on
what to look for, preventing, what is ??, etc, etc

something short and to the point ... at the very least, it will make your job easier