Have we seen this link ?
https://reverseengineering.stackexchange.com/questions/12286/defeat-rsa-hash-verification/12287
Basically it covers the MetafileChecksum and the signatures. Problem is I need an A, B, C of how to do the activities. I sort of guess that the public key is the same or failing that it can be read from the unit ?. Have we got that key yet ?.
The n in the example is a chunk of the public key.
I can't work out the process for doing "signature s raised to the power of 3 modulus n" (my two maths degrees were too long ago for that). I guess somewhere on the net there are some boxes to fill in that gives you the
0x1ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff003021300906052b0e03021a050004145e3246e50a4dad079a61f99fa3297c01d802e038
I've loaded up openssl but I really need to know in simple terms using an online process or tool how to compute the process "signature s raised to the power of 3 modulus n".
Any help most appreciated. Having emulated the process described in the link, one then wants to see what it means for the MIB2.
I reckon if one mastered this then one can start editing the map upload files and anything else that needed signed files etc.
Edit you do the maths in python, I was kindly given the formulae for the worked example:
384fc032192a20fd1e242ad64af5b509a76a7432f754aff0d6b74a7ec2072cbb11e91f68f569508b77712d1869edd6d0b9923eb77ba815dba8e44d5e09412cdf2e830518f3b38d48df892a3a0c65cc67f109e5e0f5f06ce0376d032ab21051510f3dab7f75fcdf54a96d8aa7f3c617f76d
e=3
n=0xC0F389EEC7B66C9DC736508FF88AEB1FB113942EAD020814D08D29E868F14B2086BCD7DDCCBA7559F999E76D24619660BBE17434DA59988087F2A99CD465B1FF423522B78CB0DE463A669613D356DFA9E86E0E2E0B6DAB5DE89131C5A0727AEAB1767278AB101DCD9C3CFC1026705C1DAB3BF53BF50AFAFB3F52DA2CEB0BEE57
>>> x = pow(s, e, n)
>>> hex(x)
'0x1ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff003021300906052b0e03021a050004145e3246e50a4dad079a61f99fa3297c01d802e038L'
>>>
Pick off this bit as per the worked example.
3021300906052b0e03021a050004145e3246e50a4dad079a61f99fa3297c01d802e038
Feed into
https://lapo.it/asn1js/#3021300906052B0E03021A05000414A9BC4DC6DBF5A02B19E87DD56D9236EBADA47A2A
For the final bit to give the ANS.1 hex string which is the lock to the file. The metachecksum is locked to the rest of the file less the signature and the statement itself. The chipping away process and this program to get the SHA.1
https://raylin.wordpress.com/downloads/md5-sha-1-checksum-utility/
The keys in the original post are applicable to the MIB2 High ones since I got the SLA.1 hash from the method to tally with the signatures that were protecting a VW POI upload file and a map update file. Haven't progressed it further yet, but interesting to note the public signatures are out there.
Perhaps all this is known....