![]() |
![]() |
![]() |
||||
Welcome to the GoFuckYourself.com - Adult Webmaster Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
![]() ![]() |
|
Discuss what's fucking going on, and which programs are best and worst. One-time "program" announcements from "established" webmasters are allowed. |
|
Thread Tools |
![]() |
#1 |
Amateur Gynecologist
Industry Role:
Join Date: May 2009
Location: Medellin
Posts: 4,436
|
liability for storing member passwords unencrypted?
OK so recently I stumbled on a thread in another forum where a victim of credit card fraud had contacted the website his card was used on and was given the username, password and email used to create the bogus account.
The cardholder then attempted to access the email account using the same password, and it worked. Through the email he was able to discover that the thieves had his SSN and quite a bit of other information and also seemed to have stolen the identity of several other people using the same email. He wanted to report it to the authorities but was concerned since he had made unauthorized entry to someone's email and didn't want to end up getting charged with hacking or whatever. This led to a lot of anal retentive self declared ipsecurity experts and armchair lawyers claiming that passwords should NEVER be stored as anything but a hash and should not be visible to anyone, ever, no the site owner, not customer service or anyone, and furthermore that storing them in any other way opens the site owner up to criminal (not civil) liability. I find this highly doubtful simply because it seems that pretty much the entire industry does not work that way. All the industry standard tools that I use or am aware of including nats, mechbunny, netbilling and others make the password visible to admins and CS reps, are frequently used to review for potential fraud patterns, and with the various postback systems it may not even be possible to completely encrypt them. Is it true that we are all exposing ourselves to criminal liability? Are you guys storing passwords encrypted? Are the passwords visible to anyone? What's the real story?
__________________
- As soon as I think up a good sig it's going here. |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#2 |
Too lazy to set a koala
Industry Role:
Join Date: Jan 2007
Location: CZ/EU forever!
Posts: 16,139
|
i dont understand, why even ccbill is showing to program owners plain user and pass combination of members, this is something what i really never understood ...
![]() ![]() ![]()
__________________
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#3 |
Confirmed User
Industry Role:
Join Date: Jul 2014
Location: 64 00 N, 26 00 E
Posts: 4,450
|
What? You store passwords unencrypted? I thought that it was some Flintstone era thing.
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#4 |
Amateur Gynecologist
Industry Role:
Join Date: May 2009
Location: Medellin
Posts: 4,436
|
I don't know how they are stored, but I all the systems I use allow me to see the passwords of surfers.
Nats, Netbilling, allow me to see it. I just realize I mis-spoke regarding Mechbunny, I cannot see the password there (5.0.6). The camscript also hides it. My point is that all the passwords secure is my content. So I don't know what my liability to the user is if someone gets ahold of "his" password and sees MY content. I mean sure that's potentially a loss for me, but what are the user's damages? I am guessing zero?
__________________
- As soon as I think up a good sig it's going here. |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#5 | |
Confirmed User
Industry Role:
Join Date: Jul 2014
Location: 64 00 N, 26 00 E
Posts: 4,450
|
Quote:
|
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#6 | |
Amateur Gynecologist
Industry Role:
Join Date: May 2009
Location: Medellin
Posts: 4,436
|
Quote:
I do see that nats does have the ability to store passwords encrypted only but it appears this would destroy my billing setup, as key elements rely on us using self hosted join forms and not the biller's gateway forms.
__________________
- As soon as I think up a good sig it's going here. |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#7 | |
Confirmed User
Industry Role:
Join Date: Jul 2014
Location: 64 00 N, 26 00 E
Posts: 4,450
|
Quote:
For example Paypal setup can be secured between your store and Paypal.. well, it is just basic SSL, but that is encryption too. I don't see how encrypting some password in either end would be any different. You know, either send it SSL encrypted to NATS and they do the actual encryption, or you encrypt the password at your end and send it through SSL (or without SSL). |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#8 | |
Amateur Gynecologist
Industry Role:
Join Date: May 2009
Location: Medellin
Posts: 4,436
|
Quote:
According to this: Member Usernames & Passwords - Tmmwiki it seems i would need to use the biller's join page as that is the only place the password can be entered in a way that it would get to the biller and thus propagate to the site they are buying access to. If I do that my members would not be able to do the token plus upgrade that allows them to buy site tokens. Maybe I am wrong.
__________________
- As soon as I think up a good sig it's going here. |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#9 |
Confirmed User
Industry Role:
Join Date: Aug 2006
Location: Poland
Posts: 9,228
|
There's not really much legal liability here - you are storing access to YOUR website and not someone elses, so if you are running a paysite and no one can actually cause any monetary damage to the person with that data then there's nothing you are liable for. The fact they are maybe using the same password for thier email and other sites isn't really your fault nor your problem.
Somethign like NATS would have to store them as plaintext because not all scripts and programming languages that may authenticate off of nats db can work with specific hashing methods.
__________________
Mechanical Bunny Media Mechbunny Tube Script | Mechbunny Webcam Aggregator Script | Custom Web Development |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#10 |
Confirmed User
Join Date: Feb 2007
Location: Los Angeles, CA
Posts: 1,854
|
If your database is breached and you have more than 500 California residents in that database you are required to send notice of the breach to them under the California Data Security Breach Act...
Data Security Breach Reporting | State of California - Department of Justice - Kamala D. Harris Attorney General Failure to do so means possible fines and being the defendant in a class action lawsuit. |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#11 | |
Confirmed User
Industry Role:
Join Date: Aug 2003
Location: Vegas and Los Angeles
Posts: 2,122
|
Quote:
__________________
The Only Time When Success Comes Before Work Is In A Dictionary. Did you ever notice: When you put the 2 words 'The' and 'IRS' together it spells 'Theirs.' |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#12 | |
Confirmed User
Industry Role:
Join Date: Oct 2003
Location: L.A.
Posts: 5,740
|
Quote:
I miss the days of the CCBILL log. |
|
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#13 |
It's 42
Industry Role:
Join Date: Jun 2010
Location: Global
Posts: 18,083
|
If you are the user -- use a throw away password for every sensitive website
Keep a record of them ![]() Code:
barry@deathstar9:~$ openssl rand -base64 12 M6ce0Xu0Ios1JFgj ![]() The email junk signups might as well be 'password' -- they will hijack your junk mail? I hope that is where that 123456: password: qwerty: frequency is found and people are no longer that naïve ... You are liable for your customer's loss on your website if your site is breached, and his website assets disappear, and you have made no reasonable effort to prevent this -- like cam credits -- on an ethical basis IMHO. Security Breach Notification Laws eu-data-breach-notification-rule-the-key-elements https://privacyassociation.org/news/...-key-elements/ |
![]() |
![]() ![]() ![]() ![]() ![]() |
![]() |
#14 |
Confirmed User
Join Date: Feb 2007
Location: Los Angeles, CA
Posts: 1,854
|
Here's the information covered by Cali's law... usernames with password & email count.
(g) For purposes of this section, ?personal information? means either of the following: (1) An individual?s first name or first initial and last name in combination with any one or more of the following data elements, when either the name or the data elements are not encrypted: (A) Social security number. (B) Driver?s license number or California identification card number. (C) Account number, credit or debit card number, in combination with any required security code, access code, or password that would permit access to an individual?s financial account. (D) Medical information. (E) Health insurance information. (2) A user name or email address, in combination with a password or security question and answer that would permit access to an online account. (h) (1) For purposes of this section, ?personal information? does not include publicly available information that is lawfully made available to the general public from federal, state, or local government records. |
![]() |
![]() ![]() ![]() ![]() ![]() |