Post: File Comparison patches may be a flaw
08-31-2009, 11:14 PM #1
(adsbygoogle = window.adsbygoogle || []).push({}); :confused:I'm french so sorry for writing.

I have lost a few hours I made a comparison with patch 1.3 and 1.2 so I found some differences.
on the 1.3 I found 79 different offset compared with 1.2 so I do not know if this can lead to something concrete.
Tomorrow I will try to remove those lines and change in raport to 1.2, then I'll do a test.
but if other people want me to lend a hand you are the welcome.

ps: may be that the signature is found in the differance.SmileSmileSmile
(adsbygoogle = window.adsbygoogle || []).push({});
08-31-2009, 11:40 PM #2
are you talking about the patches signature, and what offsets? Ill lend a hand.
09-01-2009, 12:02 AM #3
Default Avatar
drewbie
Guest
but isn't there some sort of hash checking so it knows its unaltered
09-01-2009, 01:05 AM #4
abz247uk
Do a barrel roll!
Count me in
09-01-2009, 10:28 AM #5
the solution in theory would make a program to gather information on the PS3 in the transfer of the patch, then you look at the info and we can know how the authentication file is.
good practice in its plot thickens as the probe must go directly to the processor.
if there are programmer help is always good to take.
09-01-2009, 10:33 AM #6
but 1.4 is out now?
09-01-2009, 12:26 PM #7
I have 3 patch file for the comparison will be better
parcontre I think I detected the signatures but not the problem now c can decrypt the patch to work on this signature and to create a clone to pass authentication
09-01-2009, 01:02 PM #8
abz247uk
Do a barrel roll!
Signature file. You will never break AES encryption, so I think this method is flawed.

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo