Go Back   vb.org Archive > vBulletin Modifications > vBulletin 4.x Modifications > vBulletin 4.x Add-ons

Reply
 
Thread Tools
Prevent guests/users from using proxies at your forum Details »»
Prevent guests/users from using proxies at your forum
Version: 1.00, by borbole borbole is offline
Developer Last Online: Oct 2015 Show Printable Version Email this Page

Category: Mini Mods - Version: 4.0.1 Rating:
Released: 02-10-2010 Last Update: 02-10-2010 Installs: 173
Uses Plugins
Translations  
No support by the author.

This hack will allow you to prevent guests/users from using proxies at your forum. You can dissallow proxies for the forum as a whole or to prevent only registrations with proxies. You can enable and disable it at the Acp of your forum where you can control the settings for the mod.

Note: As you know there is no such way of preventing proxies 100% but it helps a lot. I tested it with a dozen proxies and it stopped 8 of them.

Download Now

File Type: xml No Proxy Allowed.xml (3.0 KB, 1006 views)

Screenshots

File Type: png Forums_1265928332315.png (28.8 KB, 0 views)
File Type: png Admin Control Panel_1265929975136.png (28.8 KB, 0 views)
File Type: png Forums_1265929962923.png (28.9 KB, 0 views)

Show Your Support

  • This modification may not be copied, reproduced or published elsewhere without author's permission.
Благодарность от:
nchoate97

Comments
  #12  
Old 02-12-2010, 04:41 AM
TheSupportForum TheSupportForum is offline
 
Join Date: Jan 2007
Posts: 1,158
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

would like to see the idea of adding a proxy to a list so that it blocks proxies on a list you give

instead of blocking all proxies

otherwise when i get to work i cant view my own site due to use using the internet through a proxy provided by our county area

or an option to to add or ignore proxies so that some can visit
Reply With Quote
  #13  
Old 02-12-2010, 04:47 AM
argothiusz argothiusz is offline
 
Join Date: Nov 2008
Posts: 175
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Just for everyone information, Singapore visitors usually access the web through a gateway proxy. So, if you are using this you may as well block entire country.
Reply With Quote
  #14  
Old 02-12-2010, 09:06 AM
alessai alessai is offline
 
Join Date: Feb 2006
Posts: 153
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

my whole university is running through a proxy, which is the same for many other uni's
Reply With Quote
  #15  
Old 02-12-2010, 09:34 AM
borbole's Avatar
borbole borbole is offline
 
Join Date: Jan 2010
Posts: 2,559
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Adding a proxy list would be not so effective as those proxy lists gets update very often. it si more effective this way. Although it might prevent some legit users as stated above. If you are worried about it then I think it would be better to not install the hack.
Reply With Quote
  #16  
Old 02-12-2010, 02:41 PM
lemonadesoda lemonadesoda is offline
 
Join Date: Nov 2009
Posts: 80
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

borbole,

I REALLY like the concept. Could you consider having a track, monitor and control system rather than just "block all".

The way it would work is thus:

1./ It would record all proxy attempts AFTER login name is captures, and log the proxy IP as well as the username
2./ The admin would be able to view this tracking list
3./ At any time, the admin can review proxy use ("monitor") and if the user logged in, which username it was ("track")
4./ The admin can select from the list of proxy addresses, and make specific IP's BLACKlisted or WHITElisted
5./ The admin would have an option to set the default as all (unknown) proxies BLACK or WHITE
6./ There would be an option to allow/block guest proxy access

I think that your programming hook is therefore one step later... let people log in first BEFORE running the blocking.

Yes, this requires some manual intervention by the admin to make it work properly. But this is very important for us, since we run a private vB for staff and clients. Clients may be behind proxies. By tracking, I can see who they are and the IP of the proxy. I can then decide to BLACK or WHITE list them. I cant risk blocking clients. I only want to block hackers.

When we have a new client, I could "shields down" until the client has logged in and I have the monitoring data. Then I could "shields up" again.

With this modified tool I would now have a monitoring system to see if people are trying to access via proxies, especially banned users (ex. staff and ex. clients).
Reply With Quote
  #17  
Old 02-12-2010, 03:59 PM
borbole's Avatar
borbole borbole is offline
 
Join Date: Jan 2010
Posts: 2,559
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

I have tried that before when I coded it for another forum software and due to the proxies lists getting updated dayily it made next to impossible to track them. Whereas like this it works great.

Now, if you want to block people from logging in with a proxy, change the register_start hook to login_process hook and whenever a user logs in with a proxy, it will revert him/her immediately to their real ip.
Reply With Quote
  #18  
Old 02-12-2010, 10:34 PM
djbaxter djbaxter is offline
 
Join Date: Aug 2006
Location: Ottawa, Canada
Posts: 2,601
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Quote:
Originally Posted by borbole View Post
I have tried that before when I coded it for another forum software and due to the proxies lists getting updated dayily it made next to impossible to track them. Whereas like this it works great.
Works great at what, though? Blocking entire corporations? Entire campuses? All AOL users? Apparently some countries?

It seems to me this is like using nuclear missiles to kill mosquitoes...
Reply With Quote
  #19  
Old 02-12-2010, 10:46 PM
vb4newb vb4newb is offline
 
Join Date: Feb 2010
Posts: 64
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

I am very happy with it ,I tested it thoroughly and then again my members are all home users
so I think it depends on your target membership, not all forums cater to Large corporations
that use proxies.
Reply With Quote
  #20  
Old 02-12-2010, 11:25 PM
ndut ndut is offline
 
Join Date: Sep 2007
Location: Indonesia
Posts: 335
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

thank you
Reply With Quote
  #21  
Old 02-13-2010, 06:44 AM
barcena's Avatar
barcena barcena is offline
 
Join Date: Sep 2006
Posts: 262
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Quote:
Originally Posted by lemonadesoda View Post
borbole,

I REALLY like the concept. Could you consider having a track, monitor and control system rather than just "block all".

The way it would work is thus:

1./ It would record all proxy attempts AFTER login name is captures, and log the proxy IP as well as the username
2./ The admin would be able to view this tracking list
3./ At any time, the admin can review proxy use ("monitor") and if the user logged in, which username it was ("track")
4./ The admin can select from the list of proxy addresses, and make specific IP's BLACKlisted or WHITElisted
5./ The admin would have an option to set the default as all (unknown) proxies BLACK or WHITE
6./ There would be an option to allow/block guest proxy access

I think that your programming hook is therefore one step later... let people log in first BEFORE running the blocking.

Yes, this requires some manual intervention by the admin to make it work properly. But this is very important for us, since we run a private vB for staff and clients. Clients may be behind proxies. By tracking, I can see who they are and the IP of the proxy. I can then decide to BLACK or WHITE list them. I cant risk blocking clients. I only want to block hackers.

When we have a new client, I could "shields down" until the client has logged in and I have the monitoring data. Then I could "shields up" again.

With this modified tool I would now have a monitoring system to see if people are trying to access via proxies, especially banned users (ex. staff and ex. clients).
I'm all for this!!!!

You'r hack idea is great, you have no idea how badly I/we need something like this, but not so drastic though; and I think if you implement lemonadesoda's ideas this will become MOTM in no time!.
Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 09:28 AM.


Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2024, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.08604 seconds
  • Memory Usage 2,336KB
  • Queries Executed 26 (?)
More Information
Template Usage:
  • (1)SHOWTHREAD
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)ad_showthread_beforeqr
  • (2)bbcode_quote
  • (1)footer
  • (1)forumjump
  • (1)forumrules
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (1)modsystem_post
  • (1)navbar
  • (4)navbar_link
  • (120)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (3)pagenav_pagelink
  • (11)post_thanks_box
  • (1)post_thanks_box_bit
  • (11)post_thanks_button
  • (1)post_thanks_javascript
  • (1)post_thanks_navbar_search
  • (1)post_thanks_postbit
  • (11)post_thanks_postbit_info
  • (10)postbit
  • (4)postbit_attachment
  • (11)postbit_onlinestatus
  • (11)postbit_wrapper
  • (1)spacer_close
  • (1)spacer_open
  • (1)tagbit_wrapper 

Phrase Groups Available:
  • global
  • inlinemod
  • postbit
  • posting
  • reputationlevel
  • showthread
Included Files:
  • ./showthread.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/functions_bigthree.php
  • ./includes/class_postbit.php
  • ./includes/class_bbcode.php
  • ./includes/functions_reputation.php
  • ./includes/functions_post_thanks.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
  • showthread_start
  • showthread_getinfo
  • forumjump
  • showthread_post_start
  • showthread_query_postids
  • showthread_query
  • bbcode_fetch_tags
  • bbcode_create
  • showthread_postbit_create
  • postbit_factory
  • postbit_display_start
  • post_thanks_function_post_thanks_off_start
  • post_thanks_function_post_thanks_off_end
  • post_thanks_function_fetch_thanks_start
  • fetch_musername
  • post_thanks_function_fetch_thanks_end
  • post_thanks_function_thanked_already_start
  • post_thanks_function_thanked_already_end
  • post_thanks_function_fetch_thanks_bit_start
  • post_thanks_function_show_thanks_date_start
  • post_thanks_function_show_thanks_date_end
  • post_thanks_function_fetch_thanks_bit_end
  • post_thanks_function_fetch_post_thanks_template_start
  • post_thanks_function_fetch_post_thanks_template_end
  • postbit_imicons
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • postbit_attachment
  • postbit_display_complete
  • post_thanks_function_can_thank_this_post_start
  • pagenav_page
  • pagenav_complete
  • tag_fetchbit_complete
  • forumrules
  • navbits
  • navbits_complete
  • showthread_complete