-
## Environment
- OS: Ubuntu 24.04.1 LTS
- Kubernetes/K3s: K3s v1.29.6+k3s2
- AWX Operator 2.19.1
## Description
everything seems to be running fine. however, after the installation is compl…
-
Installed 3.1.1, and after deleting my old account information under .storage, I am able to create an account.
However after putting my username and password in and requesting a code, it never shows …
-
```
Passwords are currently stored as plain text in the configuration. Galaxium
should use keyring manager instead.
```
Original issue reported on code.google.com by `Zarevucky.Jiri` on 21 May 2009 a…
-
```
The ESAPI reference implementation contains a weak salting mechanism for
password storage. (Currently uses a known value, the account name) It also does
not implement or encourage salt isolation…
-
```
The ESAPI reference implementation contains a weak salting mechanism for
password storage. (Currently uses a known value, the account name) It also does
not implement or encourage salt isolation…
-
SHA512 is not an encryption algorithm, it is a cryptographic hash function. This hash function is **not suitable for passwords** because it is a very light functional that can be processed at high…
-
```
The ESAPI reference implementation contains a weak salting mechanism for
password storage. (Currently uses a known value, the account name) It also does
not implement or encourage salt isolation…
-
Main reading: https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html
- Password should be hashed, NOT encrypted.
- Hashing is a one-way function, encryption is a two…
-
```
The ESAPI reference implementation contains a weak salting mechanism for
password storage. (Currently uses a known value, the account name) It also does
not implement or encourage salt isolation…
-
```
The ESAPI reference implementation contains a weak salting mechanism for
password storage. (Currently uses a known value, the account name) It also does
not implement or encourage salt isolation…