Actions
Bug #2408
closedpassword generation in history ...
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
I think the proposed command to generate password are not very secure, because history file will keep it.
So it will be better if documentation reader try to generate password with a command like this :
-----snip here---
read mypass; echo $mypass | sha512sum
-----snip here---
Updated by Francois BAYART over 12 years ago
I miss the "-n"
-----snip here---
read mypass; echo n $mypass | sha512sum
-----snip here--
Updated by Francois BAYART over 12 years ago
Humm syntax problem
-----snip here--- read mypass; echo -n $mypass | sha512sum -----snip here---
Updated by Jonathan CLARKE over 12 years ago
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:65281dc4ade4b556fb936c19d1412f8f237361a8.
Updated by Jonathan CLARKE over 12 years ago
- Tracker changed from User story to Bug
- Status changed from Pending technical review to Released
- Assignee changed from Fabrice FLORE-THÉBAULT to Jonathan CLARKE
- Target version set to 2.3.7
Thanks for taking the time to get this command right, François. I've fixed it in the docs and in the sample file distributed with Rudder, for 2.3 and 2.4 branches. Docs should be up to date in a few minutes.
Actions