View Single Post
Old 07-12-2017, 12:48 PM   #1433
coplate
Guru
coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.
 
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
Quote:
Originally Posted by knc1 View Post
Are the first four characters of the package included in the signed checksum?
If not, just hex edit them to one of the other package types.

The only change I have seen (so far) is that they took 'FB03' out of the acceptable package types case statement.
That is the package type used by the initial (load to anything) factory firmware packages.

Hmm...
Just hexedit the '3' to a '2' (or something else) and see if the signature check still passes.

The FB02 and FB03 appear to have a different header layout, so it doesn't suffice to just change the type.

I don't have the details handy, but it might be possible. On an SP01 file, the signature only applies to the data that come after the signature.


I haven't looked at the signatures inside an FB02 or FB03 file, to see where the start and end, but the short version is that a signature cannot include itself, there could be other protections though.
coplate is offline   Reply With Quote