vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 2.x Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=4)
-   -   Password Protected Forums (vB3 Style) (https://vborg.vbsupport.ru/showthread.php?t=50012)

John 03-13-2003 02:28 PM

Quote:

Today at 11:26 AM squawell said this in Post #39
nice hack...

* squawell installed.... ;)

another question if i set timeout 1 week and after 1 week i forget

set new one.so that will let everyone access or the forum still

use the old password??


No, the password will stay the same.

The timeout is the amount of time before the user will have to enter the same password again to access the forum.

John 03-13-2003 02:28 PM

Quote:

Today at 10:11 AM Pady said this in Post #38
does this also cover the profile view where the last post is also listed and within the who's online?

In the next update it will.

John 03-13-2003 02:56 PM

Quote:

Today at 12:11 PM DBs said this in Post #40
Hi

Nice hack but I think I have found a problem.

If I set a forum password and the timeout to say 1 week, then go in and change the password to something else, it doesn't match the cookie and denies access - all is well.

If I then enter the new password it still says access is denied. Seems like the cookie is not being updated with the new password I entered.

Find:

PHP Code:

if ($_COOKIE[cookpass][$forumid]) { 

Above this add:

PHP Code:

if ($_POST[forumpass]) {
$_COOKIE[cookpass][$forumid] = $_POST[forumpass];


Instructions updated.

Davey 03-13-2003 03:00 PM

Find in which file?

Dave.

DBs 03-13-2003 03:05 PM

Quote:

Today at 05:00 PM Davey said this in Post #44
Find in which file?

Dave.


forumdisplay.php
showthread.php

Thanks for the fix.

John 03-13-2003 03:08 PM

Quote:

Today at 05:05 PM DBs said this in Post #45



forumdisplay.php
showthread.php

Thanks for the fix.

That's right, both of them. :)

squawell 03-13-2003 03:25 PM

Quote:

Today at 12:28 AM Shaolyen said this in Post #41



No, the password will stay the same.

The timeout is the amount of time before the user will have to enter the same password again to access the forum.

thankz ur reply!!:D:D

now im understand...... :rambo:

sebastien69 03-14-2003 11:18 PM

install and work perfectly

but on index forumlist the $forum[description] appear what??

I have put the right code in the root/index.php

Code:

if ($forum[security] == 2) {
                $forum[description] .= " [<i>Password Protected</i>]";
        }


above
eval("\$forumbits .= \"".gettemplate("forumhome_forumbit_level$depth$te mpext")."\";");

i'didn't know what i do wrong

My forum description is like this:

Coding projects [Password Protected]


vb2.2.8

John 03-15-2003 12:25 AM

That's what is supposed to happen. It shows that the forum is password protected.

sebastien69 03-15-2003 03:30 AM

yes ok but in your screenshot the forum with the password hack show no description why??
It's because there is no description for the forum or it is the hack that hide description???

https://vborg.vbsupport.ru/attachmen...&postid=364734

John 03-15-2003 08:25 AM

There was no description. It doesn't replace it.

giang 03-15-2003 08:29 AM

Hey guys, I tried to install on 2.30 and I have some problem, maybe you guys can help me out.

1) When Edit my forums, I choose Password Protect Security then I enter the password and the time out but when I click submit, I got this message.
"Password protection enabled, yet no password was submitted.
(Forum access can be gained by leaving the password field blank on entry.)"
However when I look in the database, the forumpass field got the right password.
2) I can't get inside that protective forums when I supply the password. It keeps asking me to enter the password.

thakz

G

John 03-15-2003 08:31 AM

Hmm, do you have register_globals turned on or off?

sparky2 03-15-2003 02:50 PM

Thanks for releasing this hack. It's opens a fresh can o' worms, though.

---------------------------
Use of password-protected subforums will probably cause resentment among the excluded members, and generate repeated posts/PM from excluded members
demanding to know "Why?", "Why am I not special?", "Why can't I get in?!?"

You might preclude/alleviate this somehat by including in the forum description a CLEAR explanation of WHY the subforum is protected, HOW select members attain
eligibility to participate in it (and WHO to contact with a password request if a member believes he's eligible)...
and you'd probably need to change the forum description field to allow enough room for sufficient descriptive text ~~ the standard field is limited to 250 characters.

To avoid the "in your face, but you can't access it" effect, consider marking any password-protected subforum(s) "inactive" via the AdminCP--}Forums:Edit interface.
This will suppress the title/description display on ForumsHome, will remove the forum(s) from forumjump and from the search selectbox... yet it won't interfere with the
ability of "insiders" to use the "Search this forum" feature (included in the "forumdisplay" template).

---------------------------
Password-protection is "only as good as" the people protecting the password. Bear in mind that it's subject to "social engineering". Ultimately (eventually) you should
EXPECT that someone(s) not "officially" invited will coax a friend (to whom the password is known) into divulging the password.

So, if you decide to employ a pw-protection scheme, you should PLAN (and communicate to included members) in advance:
-- which person(s) has the ability/authority to change the password
-- when/why the password may be changed (how often // for what reason)
-- how the included members will be notified, in the event of a password change
-- who (everyone, or just the leader) is permitted to divulge the password and to invite new "insiders"
-- what penalty will be applied if someone irresponsibly divulges the password to unqualified/uninvited "outsiders"
---------------------------

John 03-15-2003 02:59 PM

People understand what they get when they install this hack.

If they wish to "brace themselves" for the potentially huge influx of people asking for access, they can do so. If they can't deal with this, they probably shouldn't be running a forum.

The hack is here to make it technically possible for people to do things with their bulletin boards, the way they deal with the results is up to them.

John 03-15-2003 03:13 PM

Quote:

You might preclude/alleviate this somehat by including in the forum description a CLEAR explanation of WHY the subforum is protected, HOW select members attain
eligibility to participate in it (and WHO to contact with a password request if a member believes he's eligible)...
and you'd probably need to change the forum description field to allow enough room for sufficient descriptive text ~~ the standard field is limited to 250 characters.
I should think that anyone who installs this hack would explain why it's there, in the form of a thread or an announcement.

Quote:


To avoid the "in your face, but you can't access it" effect, consider marking any password-protected subforum(s) "inactive" via the AdminCP--}Forums:Edit interface.
This will suppress the title/description display on ForumsHome, will remove the forum(s) from forumjump and from the search selectbox... yet it won't interfere with the
ability of "insiders" to use the "Search this forum" feature (included in the "forumdisplay" template).

If a user tries to access the forum, they'll still be prompted for a password. (Which would kind of give the game away)

Quote:

Password-protection is "only as good as" the people protecting the password. Bear in mind that it's subject to "social engineering". Ultimately (eventually) you should
EXPECT that someone(s) not "officially" invited will coax a friend (to whom the password is known) into divulging the password.
Obviously.

Quote:

So, if you decide to employ a pw-protection scheme, you should PLAN (and communicate to included members) in advance:
-- which person(s) has the ability/authority to change the password
-- when/why the password may be changed (how often // for what reason)
-- how the included members will be notified, in the event of a password change
-- who (everyone, or just the leader) is permitted to divulge the password and to invite new "insiders"
-- what penalty will be applied if someone irresponsibly divulges the password to unqualified/uninvited "outsiders"
This hack does exactly what it says it does. It password protects forums. If you can't handle having passwords, don't - stick to user access masks. It's not supposed to replace it, it's here as an alternative.

Honestly, people understand what the hack is for and if they need it, they use it. If anyone wants to release a "Enhanced Diplomatic Solutions to Ease Forum Tension in the Event of Password Protected Forum Usage" hack, be my guest.

Smoothie 03-15-2003 04:01 PM

Quote:

If anyone wants to release a "Enhanced Diplomatic Solutions to Ease Forum Tension in the Event of Password Protected Forum Usage" hack, be my guest.
LOL

jancarlo 03-19-2003 07:55 AM

Database error in vBulletin 2.3.0:

Invalid SQL: SELECT security,forumpass,passtimeout
FROM forum
WHERE forumid='2'
mysql error: Unknown column 'security' in 'field list'

mysql error number: 1054

Date: Wednesday 19th of March 2003 10:51:28 AM
Script: http://pinuvccio.altervista.org/foru....php?forumid=2
Referer:



help my

John 03-19-2003 08:27 AM

You didn't run the queries at the beginning (the very first thing listed in the instructions.)

jancarlo 03-19-2003 08:51 AM

error in musql look :(

1. SQL QUERIES

Run these queries:
-----------------------------------------------------------
ALTER TABLE `forum` ADD `security` TINYINT(1) UNSIGNED DEFAULT "1" NOT NULL;
ALTER TABLE `forum` ADD `forumpass` text NOT NULL;
ALTER TABLE `forum` ADD `passtimeout` int(8) UNSIGNED DEFAULT "0" NOT NULL;
-----------------------------------------------------------


Database error in vBulletin Control Panel 2.3.0:

Invalid SQL: UPDATE forum
SET
styleid='1', title='Main Category', description='Main Category Description',
active='1', displayorder='1', parentid='-1', parentlist='1,-1',
allowposting='0', cancontainthreads='0', daysprune='0',
newpostemail='', newthreademail='',
moderatenew='0', allowhtml='0', allowbbcode='0',
allowimages='0', allowsmilies='0', allowicons='0',
styleoverride='0', allowratings='0', countposts='1',
moderateattach='0', security='', forumpass='', passtimeout=''
WHERE forumid='1'
mysql error: Unknown column 'security' in 'field list'

mysql error number: 1054

Date: Wednesday 19th of March 2003 11:47:40 AM
Script: www.???_?????????.da.ru/admin/forum.php
Referer: http://pinuvccio.altervista.org/admi...edit&forumid=1

Smoothie 03-21-2003 03:03 AM

There is a major security flaw in this hack that was just discovered. I can tell you an easy way to get in to a password protected forum.

GoTTi 03-21-2003 06:17 AM

r u gunna tell us how?

John 03-21-2003 01:45 PM

If you've found a flaw, why haven't you contacted me about it?

TheComputerGuy 03-22-2003 11:54 AM

Well I tried to update my forum descriptions and it seems not to update any longer?

Did I miss something?

LOD-squa 03-30-2003 05:20 PM

Hmm, one of my members used another password and he was still able to get into the forum =\

Zero Complex 03-30-2003 07:01 PM

awesome. Finally someone puts a working one up. the other one had so many bugs.

Bloodfist 04-12-2003 10:17 PM

So is this hack stable or what?

What's it's status?

Crazy Pete 04-13-2003 03:50 AM

Edit - Nevermind, I forgot to clear my cookies.

Crazy Pete 04-13-2003 04:31 AM

Actually, there does seem to be a problem with this. Some people are able to click on a link to a post in the password protected thread, and it asks them for the password. So far, so good. But then, if they click back to the main index and reload it, THEN click on the password protected forum, they get right in.

I haven't been able to duplicate this, but some of my members said they got in without a password and that was one of the ways they did it.

kushtiUK 04-13-2003 08:22 AM

Quote:

Today at 06:25 AM Crazy Pete said this in Post #69
Actually, there does seem to be a problem with this. Some people are able to click on a link to a post in the password protected thread, and it asks them for the password. So far, so good. But then, if they click back to the main index and reload it, THEN click on the password protected forum, they get right in.

I haven't been able to duplicate this, but some of my members said they got in without a password and that was one of the ways they did it.


I have the same problem and I also managed to duplicate it. I am running 2.2.6 though so I don't know if that's the problem - can any else confrim?

Crazy Pete 04-13-2003 10:29 PM

FWIW, I'm running 2.3.0, and have had more reports of people being able to get in without a password today, as well.

Smoothie 04-14-2003 04:05 AM

I told you guys there was a problem with this in post #61. Did you think I was kidding?

Smoothie 04-14-2003 04:07 AM

Quote:

Yesterday at 05:16 AM kushtiUK said this in Post #70
I have the same problem and I also managed to duplicate it. I am running 2.2.6 though so I don't know if that's the problem - can any else confrim?
Confirmed this weeks ago, and I did pm the author of this hack. He complained that I didn't contact him about the problem, and when I did, I received no response.

Crazy Pete 04-18-2003 05:30 AM

That's too bad, this would be pretty badass if it weren't for that odd little bug.

Floris 04-22-2003 08:38 AM

Bug ?
Security flaw !

I hope he can still fix it, I have this installed, working and the flaw is confirmed & reproducable on 2.2.9

I hope he can fix it.

Floris 04-23-2003 04:35 PM

We really needed this hack, and after looking at it, I threw it towards Scott and he fixed it in 1 minute, lol.

Here is version 1.2 which at least works on one of the sites I have it installed on. So hopefully it works for you too.

The changes are the forumdisplay and showthread text that you have to replace, the whole chunck. So, to upgrade, just remove it from those 2 files again and put this stuff instead.

Moo

flup 05-02-2003 09:59 PM

Nice,

/me clicks install

Deathdealer 05-03-2003 07:44 PM

im getting this Invalid SQL:
SELECT security,forumpass,passtimeout
FROM forum
WHERE forumid =

mysql error: You have an error in your SQL syntax near '' at line 5

mysql error number: 1064

marlborosat 05-04-2003 12:41 AM

idem
Database error in vBulletin 2.3.0:

Invalid SQL:
SELECT security,forumpass,passtimeout
FROM forum
WHERE forumid =

mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 3

mysql error number: 1064

GaleForce 05-04-2003 05:37 AM

This looks pretty cool, I may have use for this :)


All times are GMT. The time now is 04:19 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02725 seconds
  • Memory Usage 1,842KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_code_printable
  • (2)bbcode_php_printable
  • (13)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (3)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (40)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete