Multiple password hashing schemes #8
Labels
No labels
bug
code clarity
code organization
database
documentation
improvement
new feature
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nu/CharmBoard#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
More password hashing schemes should be available as an option, with CB not throwing errors if the module for one that's not being used isn't installed. This is to hopefully allow CharmBoard to be run on a wider variety of hardware, like if someone has an old PC lying around that they'd like to host the site on. I think I also need to change the way passwords are stored in the DB to make it note which hashing scheme is used (this is really standard so I'm not sure why I didn't already do it from the get-go)
I'll have to see if optional
usestatements are a thing in Perl, like if you can have ausestatement activated with an if/else statement or something. This would also be useful for making database drivers optional!Not
usestatements, butrequirestatements, a keyword I didn't know existed before now.See: https://stackoverflow.com/questions/251694/how-can-i-require-an-optional-perl-module-if-installed
Looks like I'll have to completely change up what
CharmBoard::Model::Cryptworks like, jeez!https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html
On top of Argon2, scrypt and bcrypt should be implemented