Version: 1.00, by mt_100
Developer Last Online: Aug 2003
Version: 2.2.x
Rating:
Released: 08-01-2002
Last Update: Never
Installs: 22
No support by the author.
OK, my first "hack"!
I created this because I want to have security and logins for my sites non VB pages but don't want two logins, one for the site and one for the forums.
There are other hacks that do the same thing, but this one is different.
1. It creates a PHP session, which means when the user closes the browser they will have to login to the site again later. It doesn't access the VBulletin cookie at all.
2. The user is prompted to login on any page you include this on, once logged in they are taken to that page minus the security.
3. No modification to the VBulletin code.
4. Uses the VBulletin user table so any information in there can be used, like welcoming them on all pages with their login name or telling the user who they are loggin in as.
5. You can block poeple based on their VBulletin user group! That way only certain user groups can see the rest of your site.
6. RUNS ON WINDOWS 2000 AND IIS!!!!!!
Let me know how you like it!
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Originally posted by Velocd Screenshots, demo's, anything to show us why this hack is different than so many of the other security hacks?
Not to seem antagonistic here, but why should the burden of proof fall squarely on the shoulders of MT_100 ? I see this sort of post here all the time -- someone makes a hack and releases it and invariably someone else comes along and "challenges the legitimacy" of that hack.
Variety is the spice of life. Maybe MT_100's code is just cleaner than the rest ... maybe his/hers is the one that works best with Microsoft web servers ... maybe it was created without harming any laboratory animals. Who knows!
I doubt it is cleaner, I'm certainly not a pro, but it works.
I saw a great hack for Apache on Unix/Linux with .htaccess that did the same thing and loved it, use it on one of my servers.
I just wanted one that would work the same on IIS, so I made it and wanted to share it.
I did forget that you need to put a file called connect.php in the same folder with membercheck.php with your server connection varioables in it, or hardcode them into membercheck.php.
Originally posted by mt_100 I doubt it is cleaner, I'm certainly not a pro, but it works.
I just wanted one that would work the same on IIS, so I made it and wanted to share it.
Thanks for releasing it. As an IIS person myself, I can assure you that it will come in handy for several of us in the VBulletin community.
The thing that irks me is how some people essentially spit in the face of generosity by expecting a coder to justify the worthiness of his contribution. People are here sharing their code, tricks and tips -- for free. Why look a gift horse in the mouth?
Sorry for the comment earlier, until I actually looked at the code I didn't realize it was so simple enough it didn't need screenshots. I have a dull imagination when it comes to hacks that I'm usually not sure what they do before I install, so I tend to need some visuals.
1. Create a file called connect.php and define the connection variables. Here is an example:
PHP Code:
<?
// Variables that are used are the following
// $DB_SERVER : Name of MySql server by default "localhost"
// $DB_USER : User name taht is used to connect to MySql
// $DB_PASS : User password for MySQL conenction
// $DB_NAME : Name of database to use
$DBSERVER = "yourserver here";
$DBUSER = "DB User Name Here";
$DBPASS = "DB Password Here";
?>
2. Put the membercheck.php file in the folder with connect.php
3. Put an include for membercheck.php at the top of each page you want to secure.