Migrate away from MD5 to $Discuss #4592
Replies: 2 comments 5 replies
-
|
I've considered moving to SHA-3 before, but given it's not used for security really, it's not been that high on my list to implement |
Beta Was this translation helpful? Give feedback.
-
|
Well, BLAKE3 isn't in the standard library until 3.11, so that's out. Could migrate to one of BLAKE2 though or SHA3 |
Beta Was this translation helpful? Give feedback.
-
|
I'd suggest SHA3, if only to make my accountant happy. |
Beta Was this translation helpful? Give feedback.
-
|
What about SHA3 makes your accountant happy? Does it integrate with some software they use? If so, which one? |
Beta Was this translation helpful? Give feedback.
-
|
My accountant used to be a programmer and keeps an eye on advances in various fields (in particular, cryptography - she used to be a cypherpunk). MD5 has been deprecated for a long time, and SHA1 isn't as trustworthy as it used to be. SHA3 seems to be the logical successor across the board. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I thought it was something applicable to them being an accountant. |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically closed due to lack of community support. Please see our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
Description
MD5 is utterly broken., Another hash algorithm should be used instead. However, practical considerations have to be accounted for- existing data sets, 3rd party applications using APIs, possible internal use within the database as keys, etc.
I humbly suggest one of the following:
Thoughts?
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions