Closed VladRassokhin closed 12 months ago
The verification code in apple-codesign has drifted out of sync with the signing code and is lacking compliance with Apple's implementations in a number of areas. I've actually been tempted to delete the code because I question the value of having code with so many bugs that can likely never be bug compliant with Apple's tooling.
I'm using
rcodesign
fromapple-codesign-0.20.0-x86_64-apple-darwin.tar.gz
Meanwhile executable has both Sha1 and Sha256.
Seems
macho.code_signature()
returns ony first signature? My knowledge of rust is subtle. Probablyverify_macho
should check both code directories and not complain if one of them is using good enough algorithm (sha256).