Plaintext user information

[computerprep 148]

I've been following LDAP progress, but hope to accomplish a simple task without getting into LDAP users yet.

 

I run a couple of other services in my server and would like to merge user accounts and passwords. For example, FTP server and Emby streaming server. I can change my FTP users password by locating the appropriate .ini file and changing it there. My hope is to find my Emby users' password stored somewhere in plaintext so I can write a script to make other plaintext passwords match.

 

In the end, my friends and family can change their Emby password like a universal password.

 

Most of my other services offer LDAP integration, but that's a project for a different time.

[Carlo 4561]

You're not going to get this.  It's stored in the database and the password isn't clear (would be bad).  This is the whole point of the LDAP plugin in that you can setup a central user account and have all your programs that support it pointed to the LDAP source.  FTP, VPN, remote login, network credentials are all prime candidates to sharing this information.

[computerprep 148]

I understand the point to LDAP. And more to my point, there would not really be anything bad about plaintext password storage for this particular case. All my connections use forced security. The only way the passwords would be vulnerable is if someone gained admin access to the entire server, at which point these passwords are the least of the problem.

[ebr 16212]

Hi.  We don't store the password in plain text for the security reasons mentioned above.  Even though it would be fine for your situation, it wouldn't be for most.

[computerprep 148]

Where is there encrypted information stored? I've found some user configuration files, but there doesn't look to be even hashed passwords stored where I was looking.

[ebr 16212]

Everything is stored in our internal database.  Start mucking with that at your own risk .  But, you're not going to find anything you can translate to a password...

[Carlo 4561]

Unless you pull down the code to use small parts of it to figure out the encryption.