The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#31
|
|||
|
|||
Quote:
|
#32
|
|||
|
|||
finding a solution to the problems are number one, which should be always be the aim
however as mentioned by microhellas, you don't find vBulletin sending out an email to all their users, when they find a vulnerability, to uninstall their software. They work to first find a solution. to see how an email was sent out to all the users of Microhellas' hacks before finding a solution with the author was (imo) irresponsible and it has led to a valid contributor now making her hacks unavailable to the users of vb.org I can see her point, the email sent out creates alarm (which from a business point of view for her is plain destructive) and causes the users of her products to get the impression that there is something inferior or wrong with her products in this instance a solution was easily found by the author and this whole scenario could have been avoided hopefully those involved can learn from this Thank you everyone for working to provide a service of value to all users |
#33
|
||||
|
||||
It is recommended that you remove a hack because it isn't the product. If you still want to continue using the hack at the risk of an exploit, it's your own choice.
|
#34
|
||||
|
||||
There is no "we now have " about it - the vulnerability has always been there, it's only now been reported to us. There is a big difference there.
|
#35
|
|||
|
|||
Quote:
At the end of the day vBulletin is also still a product and the information gathered by the forums on my servers is our property. To protect this property from exploits is no different when exploits are found with vBulletin they do not send out an email to all their users telling them to uninstall. all I am saying is that this could have been dealt with differently Quote:
the timing was what I questioned I voice my concerns regarding microhellas, it is not an attack on any party in any way but more a hope of avoiding similar scenarios in the future I am thankful for the work done by vB.org however there are often many ways to skin a cat |
#36
|
|||
|
|||
i like this thread... a similar one was started by my friend Hambil 2 weeks ago, and 3 weeks ago too, with the same reasons, same debate, and same result... (none)...
so it would be just time you stop complaining and start repairing your bugs when you have some...it usually take less than 1hour to do so, and then your releases go back to public... and if you are not happy with the policies, instead of complaining, because it's useless, these are made to be unchanged because they work, you can simply release your work elsewhere better... (if you find a better place, just tell me, i'd be happy to start complaining there also!) |
#37
|
|||
|
|||
I apologize if I misunderstood it, but are you calling us hackers????
|
#38
|
|||
|
|||
Noooo, he's not saying that at all. I believe he's saying that he would rather have a board with zero modifications, rather than have a board that was defaced by hackers due to exploited modifications or modifications with security issues.
|
#39
|
|||
|
|||
Quote:
Are you defacing other peoples websites? If the answer is "Yes" then, yes he is calling you a hacker. |
#40
|
|||
|
|||
Funny!! That's why I wrote "I apologize etc etc". I don't know the meaning of "deface". I got the meaning of "full of" as the other member wrote above.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|