We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description: Replaces Base64 encoding with SHA-256 hashing for enhanced security.
Implementation Details: Replace "base64" module with "hashlib" module.
Reason for Change: Base64 is not secure, while SHA-256 provides a secure, non-reversible hash suitable for sensitive data.
Cons: Make the users enter the mining key everytime they want to start a new mining sesssion
The text was updated successfully, but these errors were encountered:
A hash is unsuited for this application. An encryption standard would be a better fit.
Sorry, something went wrong.
I think OP is referring to the mining key encryption where the encrypted key is stored in Settings.cfg by python miner
Still, a hash is unsuited. If you have to re-enter the mining key with every start anyway, why even save it?
No branches or pull requests
Description:
Replaces Base64 encoding with SHA-256 hashing for enhanced security.
Implementation Details:
Replace "base64" module with "hashlib" module.
Reason for Change:
Base64 is not secure, while SHA-256 provides a secure, non-reversible hash suitable for sensitive data.
Cons:
Make the users enter the mining key everytime they want to start a new mining sesssion
The text was updated successfully, but these errors were encountered: