The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#41
|
||||
|
||||
Yes, we see enough of Nexia as it is.
|
#42
|
||||
|
||||
Hopefully the Pentagon install vB as soon as possible!
Quote:
|
#43
|
||||
|
||||
My site was "hacked" this year. My super moderator used the forum on a lan house and they got his password and deleted the whole forum. If it wasn't for Paul's daily backup mod I was screwed, blessed be him. But there's not much I can do about that. It freaked me out though, as I had never been hacked before. And I'm not using lan houses anymore too.
--------------- Added [DATE]1204614885[/DATE] at [TIME]1204614885[/TIME] --------------- Actually I think Paul should quote my message in his mod release, I think that would be a good idea. |
#44
|
|||
|
|||
3 simple rules:
1) dont give ANYONE permission to physically delete 2) keep your vbulletin patched/up-to-date 3)trust no one -don't run brand new plugins without letting the community test it out and view the code first -dont add moderators simply cause they ask to become one (if that wasn't obvious) -if you don't want to pay the hired help.. change the passwords. |
#45
|
|||
|
|||
Bro,
What the OP is suggesting is 'how it's done', the good guys get together and share info. I belong to a couple such groups in other domains. If you don't personally have the skills, then hang around such a group, and you could still pick up something valuable within your skill level. As mentioned ... best coding practices, general safeguards, security mods. These protect your site like a locking bar on your steering wheel protects your car. It keeps the casual thief/defacer out, and steers the professional thief to an easier target. There is not really a central place to discuss those on these forums. I think vB is seemingly not a full disclosure shop, and their sensitivity on that score may prevent them from fostering such a forum. Wise as serpents, gentle as doves, yah? See you there or in the air, 'snore |
#46
|
|||
|
|||
Quote:
|
#47
|
||||
|
||||
Let's be honest, would it really matter? I'd say a large majority of the vBulletin owners here are the "click-and-play" types, who understand as much about security as they do quantum mechanics. They indiscriminately install modifications with no regards as to server load, hook conflict or, yes, even security. Most people who get "hacked" are asking for it. They're generally the forum with the more modifications installed than members.
How can one really be secure without understanding the priciples behind why what they currently have is inherently insecure. At best, you would have a forum of security suggestions where people would simply peruse the thread looking for various step-by-step instructions on how to do something -- not even understanding why it is they're doing what they're doing. I just see the whole thing as a wasted effort, really. vBulletin.org does a decent enough job of trying to keep hacks with security risks under wraps and out from public consumption -- that's really all you can ask for. You want to be truly secure? Don't run a site. You want to be relatively secure? Run a default vBulletin installation. I'm not trying to be a prick, I'm just being honest. |
#48
|
||||
|
||||
Quote:
|
#49
|
||||
|
||||
To what degree? Have I suffered data loss due to an exploit? No, never.
Regardless, what does this have to do with the issue at hand? The current state of security of my own personal sites has nothing to do with a public discussion/repository for security related topics. If any of my sites are compromised, I can immediately reference my logs, find out what happened, and either patch the exploit or take it offline for further review. Could you say the same? My point being, a vBulletin-focused security discussion isn't inherently a bad thing -- but it's not going to accomplish what many think it will. If you want to keep up to date on security issues, subscribe to Bugtraq. Consider getting a basic grasp of PHP, so you can skim through the multitude of hacks before installing to look for basic security risks -- such as unsanitized inputs. Be proactive. |
#50
|
||||
|
||||
Quote:
p.s. Thanks for your time |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|