Create Account only with PasswordHASH

[Shirkit]

Hello.

I need some help here. As the title of the topic said, I haven't found a way to simply when I create a new account only shows the PasswordHASH on the accounts.txt. Any ideas, besides changing the pol.cfg the RetainCleartextPasswords to 0?

[Yukiko]

Just curious, why not change pol.cfg and be done with it or did you want some passwords hashed and some not? If that's the case I don't think it's possible. Sounds like it might be a good feature request to add to the create account function. I could see where you might want, say, the master developer(s) account passwords hashed for security reasons but to leave all others visible so the "lesser minions" working on a shard could have access to the account files to aid in account retrieval requests.

[Shirkit]

Just curious, why not change pol.cfg and be done with it or did you want some passwords hashed and some not? If that's the case I don't think it's possible. Sounds like it might be a good feature request to add to the create account function. I could see where you might want, say, the master developer(s) account passwords hashed for security reasons but to leave all others visible so the "lesser minions" working on a shard could have access to the account files to aid in account retrieval requests.

That's the exaclty the point! ^^ If the server simply change the pol.cfg by an attack on the server, and restart the POL he'll be able to see the passwords. So, there's no way to hide the real password unless the RetainClearTextPasswords?

[CWO]

Its much more secure if you just set RetainClearTextPasswords to 0 and then if someone needs their password recovered, just change it to whatever they want. That's how I do it.

[Nando]

That's the exaclty the point! ^^ If the server simply change the pol.cfg by an attack on the server, and restart the POL he'll be able to see the passwords.

There's no way to find a password after it has been hashed, except by brute-force. So even if someone changes pol.cfg, he won't be able to see your old passwords in plain text. (And if someone gets as far as changing pol.cfg, I wouldn't be worried about acct passwords... he'd be able to do anything he wants with the server.)

As CWO said, the most secure solution is changing user's password when it's lost. It's done like this in every system that is at least the minimum concerned about security. You should do the same.