Shared password protection

[sharedpasswords]

Hi there!

We are going to launch new product - custom engine, which will search over internet for the shared passwords and provide them to the webmasters.

If you own member site - will you be interested in working together to prevent password sharring?

I have tried to contact few big networks like Bangbros, busty.pl and some others - but they are not interested in such service...

Thats pretty strange, becouse we have already founded tons of the working passwords for the sites from their networks - I do not understand, why they do not want to change passwords for that accounts or do somethink?
As for me, they loose sales on password sharing - what do you think?

From other side, they get more traffic, but no profit from it ;)

I will appreciate any comments/proposals about this idea

Thanks, Andrew

[sharedpasswords]

Most sites have some kind of the automated system which detect password sharing. But all automated solutions work extremely bad - at the internet you may find passwords for the member area for the literally any adult site.

Shared passwords = lost sales.
The most effective solution - just monitore web for the shared passwords and do some actions after it will be founded (change password/close account etc.)
Why nobody want stop it?

Any comments about this idea?
If you think that its sux - please said it

If you will explain why its sux that will be great

[directfiesta]

Some of those programs " leak " passwords to bring traffic, to later desactivate them ....
A bit like a free trial

[FC168]

ProxyPass works great for me but your idea is interesting. Good luck with your project!

[Jenny S.]

Well

Well, there are certain issues to consider. First off, I've noticed that sometimes when my PW is on a hacker site I get more traffic AND get more signups as well.

How can that be? My explanation is this. I use Pennywize to protecte the site which shuts the PW down if two IPs access it with the same PW or, one PW user sucks down an excessive amount of GB. This means when the guys are just getting into the site with a shared PW and start wanking off their little weenies the fucking thing shuts down down them. Some of the frustraded guys seem to join teh site after because they are all horned up and don't give a fuck about the measly bucks. Also, the PW still remains on the hacker site which drives traffick to my sites, and some of this traffic seems to convert. My theory. I might be wrong.

My computer geek has used this as a PR trick to drive traffick to dead pages, means, he has deliberately shared PWs with hacker sites for a while.

Now let's look at the cost. Another thing my geek told me that actually seems to make sense. If you have a dedicated server with 1.5 terrabyte of transfer volume and only 10 MB/S connection speed you may not pay any overages at all, no matter how many users are on the page because you most likely will never reach teh 1.5 TB. So all this costs you nothing.
Example. 10 MB/S means typically 9 MB/S because the system needs some juice too to operate. Now lets say if 15 users sucking down a MB file at the same time 6 out of the 15 get nothing for a while because of the connection, right? You can't suck more content down than what your connection speed allows, right?

10 MB/S is shitty. I have 100 MB/s on most pages and that's why I have Pennywize. So many other sites have 10, or even 5 only because they look only at the transfer volume included with the server deal, and, may be, at the processor speed, but totally disregard the connection speed.

[ultimatebbwdotcom]

I use Pennywize to protecte the site which shuts the PW down if two IPs access it with the same PW or, one PW user sucks down an excessive amount of GB.

Just a question on the side - how do you deal with the AOL users and the dynamic IPs. I use the same system as part of my security, the only problem i have is the AOL users that get banned temporarily when the dynamic IP triggers the security prog forcing them to write to me to unblock.

Is there a settting im missing that allows more leeway on the dynamic IPs but recognises the "real" threats???

[Jenny S.]

Never had an AOL problem and we run 15 sites through Pennywize. You can play with the settings, ie the subnet disbale threshold. This is configurable and can be changed. I set it on 5 or 6. Even ISPs with dynamic IPs like AOL don't give a user too many IPs, they change only a couple of times in an hour. If the password is on a hacker page you have dozens of totaly different IPs with one and the same PW acessing the site within minutes, and then the system kicks the PW out.

Pennywize has also a bytes disable threshold. Users of hacked PWs try to load down the hole site quickly, mostly by using a site sucker program because they don't know how long the PW is going to work. So set the bytes threshold in a sensible way. If your site has 500 MB put the settings between 400 and 500 MB. It's unlikely that a real user downloads the whole site more than once a day.

[ultimatebbwdotcom]

Never had an AOL problem and we run 15 sites through Pennywize. You can play with the settings, ie the subnet disbale threshold. This is configurable and can be changed. I set it on 5 or 6. Even ISPs with dynamic IPs like AOL don't give a user too many IPs, they change only a couple of times in an hour. If the password is on a hacker page you have dozens of totaly different IPs with one and the same PW acessing the site within minutes, and then the system kicks the PW out.

Pennywize has also a bytes disable threshold. Users of hacked PWs try to load down the hole site quickly, mostly by using a site sucker program because they don't know how long the PW is going to work. So set the bytes threshold in a sensible way. If your site has 500 MB put the settings between 400 and 500 MB. It's unlikely that a real user downloads the whole site more than once a day.

Thanks Jenny,

I do have my settings set up similar - i thought however there might have been a seperate setting other than Subnet Disable Threshold that allowed the AOL style dynamic IPs to be bypassed if consecutive.

For example, those sites that suspend after 2 IPs must have a nightmare with AOL users being that AOL can give 2 consecutve (all but the last 3 digits) and then another 2 non consecutive to the first fairly quickly.

Ill just stick with what ive got lol