Administrative and Maintenance Tools - Multiple account login detector (AE Detector)

Mod of the Month winner!
Top 10 most installed mods for vB3.6!

Same plug-in found here:

https://vborg.vbsupport.ru/showthread.php?t=125871

There are no differences as this plug-in works with the 3.5, 3.6 or 3.7 releases of vBulletin.

If you are like me and migrated from .threads, a common modification was an "AE detector", a simple mod that saved a cookie of a history of ids logged into on your site. If someone logged into more than one account, you got a PM letting you know that your site was being accessed from multiple accounts.

Over the years this was very helpful in identifying users who were posting under multiple accounts (alter-egos!) and users who would return after being banned.

You might be wondering why I don't use the vbcookie call - well, thats because on logout all vB cookies are cleared, so we need to store a cookie that is not effected by the login/logout process.

New Installation
1. Add New Product with attached XML
2. Go to vBulletin Options -> AE Multiple Login Detection Settings and set your specific settings.

Time to install: Easy - 2 minutes.

Upgrade
If you installed this as a Plug-in manually, you can delete that plugin and install this Product, just make sure to go into the Options and set them accordingly.

I hope you find this useful and will click INSTALL if you use it; should it prove useful to enough people I can look at making this installation more automated without the need for edits and an Admin Options page.

To upgrade you will want to reimport this XML file and edit your options accordingly.

1.0.3
-----
. Added a check to ensure that users weren't deleted when reporting violations
. added htmlspecialchars_uni call to username

Note: I am unable to get the call to construct_phrase with $vbphrase['multiplelogin_alert'] to work reliably, as such the $message variable is still set manually inside the plug-in and not via the phrase. If anyone has an idea of why this might not always work, I'm all ears.

1.0.2
-----
. Updated to include exclusion groups, users
. Changed so PM is sent by ae sender id

1.0.1
-----
. Released as a Product (thank you PHPGeek2k3 for your help)
. Added option to post to a forum versus send a PM (or both)
. All settings moved into Admin Option

1.0.0
-----
Initial release.

[attroll]

There was one more factor that might play into this but I don't see how it could. I had one of my admins put a usergroup of 978 in the usergroups to ignore in the AE settings. I removed it after I noticed it and that was around the same time it stopped working also. I am still playing with this some to try to figure it out. I am just throwing ideas out as to what has been done since it stopped working.

[obetyance]

is there a way we could show the tripped members in the SUBJECT line of each reported post/thread? Thanks!

It messed up my Admin panel when I did this:

on line 71 of product-ae_detection.xml, it says something like:

                            $subject = $vbulletin->userinfo['username'] . " tripped the AE detector";

now, I changed it to:

                            $subject = $vbulletin->userinfo['username'] . , $andids " tripped the AE detector";

hoping that it will show all the tripped members on the subject line instead of opening all the threads.

what happened instead, my admin panel site is not working anymore.

its says:
Parse error: syntax error, unexpected ',' in /home/fas/public_html/forum/includes/functions_login.php(185) : eval()'d code on line 56

Unable to add cookies, header already sent.
File: /home/fas/public_html/forum/includes/functions_login.php(185) : eval()'d code
Line: 56

I disabled it using this: http://www.vbulletin.com/forum/showthread.php?t=196688

Thanks so much for your help.

[Jaxel]

Can this mod possibly be changed, so that instead of making a new THREAD in a predefined FORUM... it would make a new POST in a predefined THREAD?

[aleclee]

Though I haven't had trouble getting this mod to work in 3.7.1, I have experienced severe performance issues when it's active. The board slows to a crawl and then perks right back up after deactivating the mod.

I'm on a dual-server setup (separate web/db boxes) with 800-1000 concurrent users that works great until the AE Detector is turned on.

[24hourForum.com]

Thank You Installed...

[MeMySelfNi]

<font face="Comic Sans MS">I just banned a troll and i'm sitting here now watching him re-register and the login detector didnt even detect it....</font>

[cosy]

Originally Posted by MeMySelfNi

I just banned a troll and i'm sitting here now watching him re-register and the login detector didnt even detect it....

this add on dont detect a troll (how u believe that)
is about ip if 2 users share a ip
if that "troll" change the ip is a new user

[Videx]

No, this mod isn't supposed to trigger if two users share the same IP. It's supposed to trigger if 2 logins come from the same computer & browser. These could be from one user or many.

If someone suspects you've got a detector like this, then they could easily fool it. Clearing cookies or using a different browser are the easiest ways.

[richTV]

triggering under vBulletin® v3.7.1 Patch Level 1

however, like i told my staff members, don't take it at face value and only use it as a sort of guide line.

especially when we used to use this hack alongside the Registration Prevention add-on but decided to not set it to auto ban when we discovered it to be glitchy.

Multi-Detector is still a nice tool but don't use it as an absolute.

HTH.

[AnabolicResourc]

I'm using this mod for quit a while now, starting with v3.6.
Recently upgraded to 3.7.2 and it's still working great.

Just once it gave a false warning.
It said I shared the same computer with someone I don't even know......