Next year, you'll get an email with your bitwarden passwords.

Bitwarden, generate a new password for EVERY SERVICE, EVEN LOCAL ONES (self-hosted)

I confirm my password on decryption.

It is common practice with most secure apps and being a whmcs plugin developer myself. You encrypt the password with a key(salt) and the salt is stored away from and in a different medium to where the

Hashed based on salt in configuration.php. I once forgot to carry over the salt and screwed up passwords for everyone. Maybe not every password field uses the salt though, modules do all kinds of thin

(Quote)

(Quote)

echo "YOUR-PASSWORD" > wecho "PASSWORD-HASH" > hashjohn --wordlist=w hashjohn --show hash

If that's confirmed the case (salt indeed in config php) then how the fuck did OP confirm his password against the hash?

(Quote)

Could you verify this if I post here both the hash they put in the email and my password? (Its a auto generated password only used for HS so I'm not risking myself there)

The only confirmation we have is someone saying the password hash matches their pass, right? Or did I misread?

Don't reuse passwords. Use a password manager - https://keepassxc.org/

how can I deal with this case? Do I need to change all my online password? thanks.

Don't forget by default WHMCS sends the password you create for your login to you via email. It also sends you the password generated for services on provision typically. These are stored in plain tex

(Quote)

mp;quot;,"language","pwresetkey","emailoptout","marketing_emails_opt_in","overrideautoclose","allow_s

(Quote)

Billing, almost positive. It was my password for https://secure.hostsolutions.ro/

(Quote)