Public discussions of staff decisions are not permitted on the site.

[RedTyger]

Originally Posted by SirAdrian

I run a gaming site, pretty much overrun by stupidity.

Haha! Boy does that ever ring true for gaming forums.

Originally Posted by SirAdrian

Considering this is a business site, and not really a public discussion board, they have a public image to maintain. Having hacks here with security holes could hurt thousands of customers, so they treat it with the highest priority to 1) remove the hack, and 2) notify the customers at risk. 3) is a lower priority, and that's notifying the creator of the hack for it to be dealt with.

Normally I wouldn't put my oar in, a person's forum is their own and they can run it how they like. But since this appears to be open for discussion I'll expand on what I said in the locked thread.

vBulletin.org when finding a vulnerability:
- instantly remove the software
- notify all the customers and then allow the author to organise a fix and issue an update to the software
- when it's done the software back in circulation. It could be done at any speed so I can't comment.

vBulletin.com when finding a vulnerability:
- Do Jelsoft remove the vulnerable versions until a fix is released? I don't know.
- organise a fix and issue an update to the software, usually within a day or so
- notify all the customers when it's done, anywhere between instantly via an announcement and the AdminCP message to several days via email.

Well, I'm hoping the point is made there.

[Michael Biddle]

Originally Posted by RedTyger

vBulletin.com when finding a vulnerability:
- Do Jelsoft remove the vulnerable versions until a fix is released? I don't know.

I do not think the announce until its fixed already.

[Dismounted]

Yea, vB.com don't announce there's any problems until a fix is out. It's better that way, as script kiddies don't catch wind of it.

[The Geek]

Isn't this post ironic? It is a discussion about not allowing discussions on the very topic it is discussing

I would hope that constructive threads regarding current policies would be welcomed with open arms (as I am sure all of us do). But threads reacting to specific incidents where policies were enforced only do more harm than good.

[RedTyger]

Originally Posted by Dismounted

Yea, vB.com don't announce there's any problems until a fix is out. It's better that way, as script kiddies don't catch wind of it.

That wasn't what I was getting at, whether it's better or worse is up to the individual. Both have their pros and cons.

But if vBulletin.org say that this is the minimally acceptable way of dealing with vulnerabilities then it makes Jelsoft look rather slack and raises questions about why coders here should be subject to stricter rules than they are.

And if you subsribe to the Jelsoft method then it raises questions about why vBulletin.org are laying out such hardass smackdown on the coders.

I appreciate that in Jelsoft's case you are guaranteed to get a very swift fix which is not true of coders here, but surely it's only fair to at least offer them the opportunity? It would seem reasonable to me that we should be subject to the same standards as Jelsoft, otherwise as I say, questions are raised.

[Paul M]

Originally Posted by Dream

I don't agree with this rule. And this is feedback about the site.

Actually, you agreed with it when you joined.


Almost every forum I know has such a rule - (i.e. Staff decisions are final, no public discussion of them will be entered into).


Equally, there are many laws I don's agree with, but I still have to abide by them or face the consequences - this is just the same.

[cyberphr]

This rule should stay. And I believe those whom wrote the TOS here have more experience in these fields than almost all of the members.

[Dream]

Originally Posted by Paul M

Actually, you agreed with it when you joined.

I would never agree to such a rule *shakes fist*

May you all see the light one day. I pray for your souls.

actually we did not agree to these rules, because they are not in the welcome rules but in a specific section of the site...

and i was registered here even before these rules were written...

[Paul M]

Rule 1 is all that we actually require if you boil it down

1. Staff decisions are final. Ultimately, staff has complete discretion over what is and is not acceptable on the site.

However we do list a lot of things specifically to aid you.


You might also note ;

Members of VBULLETIN.ORG are responsible for reviewing VBULLETIN.ORG General Site Rules. VBULLETIN.ORG reserves the right to modify General Site Rules at any time. Your continued use of the VBULLETIN.ORG constitutes your consent to such changes.