Hello,
the [Only registered and activated users can see links. Click Here To Register...] works fine ... except when it failed :confused:
I nearly never had issues with it when processing a single file but issues may appear when extracting the whole .sah file or large subfolder as well as with big big saf.
So ... I post there my own extractor; it behaves more or less like the lilprohacker's tool (.sdata are unciphered for instance) *but* it does not support import or repack of files because I don't know what to do with the 5th item of the "file record".
Basically these records contain:
int32 length of filename
<var> filename
int64 offset of file within data.saf
int32 length of file
int32 useless CRC or /something/
if someone has more accurate information regarding that last item, thank for clarification.
Refs: Thanks to lilprohacker for the publishment of the sbox used to encrypt .sdata files.
Edit: stamps of original .exe
SHA1: F33DAC4AB30E52BB567C3D34D78E51DF4B992114
MD5: 7CCD53B205FA5FC4162A1E84CCD67DB6
the [Only registered and activated users can see links. Click Here To Register...] works fine ... except when it failed :confused:
I nearly never had issues with it when processing a single file but issues may appear when extracting the whole .sah file or large subfolder as well as with big big saf.
So ... I post there my own extractor; it behaves more or less like the lilprohacker's tool (.sdata are unciphered for instance) *but* it does not support import or repack of files because I don't know what to do with the 5th item of the "file record".
Basically these records contain:
int32 length of filename
<var> filename
int64 offset of file within data.saf
int32 length of file
int32 useless CRC or /something/
if someone has more accurate information regarding that last item, thank for clarification.
Refs: Thanks to lilprohacker for the publishment of the sbox used to encrypt .sdata files.
Edit: stamps of original .exe
SHA1: F33DAC4AB30E52BB567C3D34D78E51DF4B992114
MD5: 7CCD53B205FA5FC4162A1E84CCD67DB6