Remove support for deprecated cryptographic options (MD2, MD4, MD5) & release to cocoapods #77
Comments
LowAmmo
changed the title
3 tasks
LowAmmo
added a commit
to LowAmmo/BlueCryptor
that referenced
this issue
Nov 21, 2024
…D4, MD5 for iOS Rework md5 into md5_insecure Provide a SHA1_insecure Update travis.yml
LowAmmo
added a commit
to LowAmmo/BlueCryptor
that referenced
this issue
Nov 21, 2024
…hms MD2, MD4, MD5 Update travis.yml
LowAmmo
added a commit
to LowAmmo/BlueCryptor
that referenced
this issue
Nov 21, 2024
…D4, MD5 for iOS Rework md5 into md5_insecure Provide a SHA1_insecure Update travis.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like Apple is considering MD2, MD4, M5 "cryptographically broken"
'CC_MD2_Final' was deprecated in iOS 13.0: This function is cryptographically broken and should not be used in security contexts. Clients should migrate to SHA256 (or stronger).So, might as well remove those options.
Then, once the options are removed - would be awesome to release the new version to cocoapods! 😄
(working on a PR to address, now)
-Thanks!
The text was updated successfully, but these errors were encountered: