The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#21
|
||||
|
||||
Also, you will find in the ToS here:
Quote:
|
#22
|
||||
|
||||
I've read the TOS - I understand the concept of cheap motor oil. But at the same time - do you guys seriously think that implementing a system which will ultimately benefit the vB.org Memberbase is a BAD thing? I mean - Seriously?
Again - I will say - I did not post this thread so that we can argue the virtues of "Sorry bud, you're on your own. You've purchased the product. Good luck with the maintenance, especially if you've modified your product..." --- I think we each understand responsibility. I'm simply suggesting that the .org might implement a simple policy of information share with Members who have installed a product. It's not about liability Redlinemotors - I'm not trying to take Jelsoft to court - are you kidding - can barely afford to pay my electricity bill - What the hell can I do with a lawyers invoice accept to ball it up and toss it in the trash LOL Meh - maybe it's just a horrible suggestion and just too dang difficult for a community of coders to implement and I just don't realize it? I tell you one thing I do realize though is that I'm a bit peeved at the notion that the current policy is to simply send out an email with absolutely no information in it. IMO it kinda defeats the purpose of sending out the email in the first place. And yes - I do realize that the email itself is infact a courtesy. All I'm saying is that the system can be bettered. I think Lynne said it can be bettered as well... And for me = bettered in favor of the vB.org Member is aces in my book. Jacquii. |
#23
|
||||
|
||||
If they didn't care, they wouldn't send an email about it and they certainly wouldn't quarantine it.
All the information you need to know is that is contains a security hole large enough to warrant a quarantine and you should disable it until a fix is posted. |
#24
|
||||
|
||||
Quote:
|
#25
|
||||
|
||||
Quote:
Also one should consider any quarantine a serious matter and continue running an addon in such a state as a security risk to your site. |
#26
|
||||
|
||||
just a thaught on my part, seeing as issues with mods are encouraged to be discussed in threads under the modification, a vulnerability should also be considered an issue as the same. By all rights, it should be shared so others can learn from it as well. and know to not repeat someone else's mistake. I do understand not wanting to share the info so others that see it can exploit it. this is a two way street that has a dead end in both directions. Ultimately we end up with more modifications that are vulnerable because of lack of knowlege.
Like i said, just a thaught. :erm: |
#27
|
||||
|
||||
How about this, in the notification email, saying it's been quarantined, also list the files contained in the quarantined mod, so that the user would be able to fully uninstall it..
So something like this Quote:
|
#28
|
||||
|
||||
^ That's actually a very nice idea Mikey
Simple, yet effective and has more information added for the enduser. I'd also like to see info about why the modification has been quarantined or graveyarded as well. Jacquii. includes/xml/bitfield_mikeyrocks.xml?!?!? HAHAHA - too funny |
#29
|
||||
|
||||
Quote:
|
#30
|
||||
|
||||
Please do not patronize me Dean, though I do appreciate your feedback on the suggestion at hand. And if a group of people such as vB.org Members who I have personally witnessed using stronger words than "hell" are condemning me for doing the same - well - it's not I who have the issue dude --- And I particularly would like to say, "Grow up and stop being hypocrits!" --- So yes - If you have a comment on the suggestion I've made - then feel free to make it or otherwise I would advise that you not post in this thread at all.
Jacquii. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|