FILLED Call_of_Duty_Infinite_Warfare_Unlocker-HHT

[matase]

https://www.srrdb.com/release/details/Call_of_Duty_Infinite_Warfare_Unlocker-HHT

 

[Palinkat]

https://www.srrdb.com/release/details/Call_of_Duty_Infinite_Warfare_Unlocker-HHT

You do not have permission to view link Log in or register now.

Pass scnlog.me

 

[Yamato]

You do not have permission to view link Log in or register now.

Pass scnlog.me

Hello, I have made some verification of this release:

• The checksum of the "hht-codiw.rar" file in the shared file is "57C83955".
• However, the attached svf in the shared file states:
  hht-codiw.rar 976bca8b
  
  
• The same checksum can be found at srrdb and dats.
• The checksums of the files located inside of the file "hht-codiw.rar" look correct (on condition srrdb is considered as a standard for comparison).

I am wondering if such a checksum missmatch is caused by a regular compression of the "hht-codiw.rar" file or there is something else.
However, if there is no intention of sticking to the Scene in preservation purposes and the file is kept as is, I would highly appreciate if you could confirm it.

 

[Palinkat]

Hello, I have made some verification of this release:

• The checksum of the "hht-codiw.rar" file in the shared file is "57C83955".
• However, the attached svf in the shared file states:
  hht-codiw.rar 976bca8b
  
  
• The same checksum can be found at srrdb and dats.
• The checksums of the files located inside of the file "hht-codiw.rar" look correct (on condition srrdb is considered as a standard for comparison).

I am wondering if such a checksum missmatch is caused by a regular compression of the "hht-codiw.rar" file or there is something else.
However, if there is no intention of sticking to the Scene in preservations purposes and the file is kept as is, I would highly appreciate if you could confirm it.

This is the only source I have for this release, a number of things could have happened to the rar for the crc to be changed (if srrdb is correct).
If the content of hht-codiw.rar matches then we are good I guess.

Thanks

 

[Yamato]

This is the only source I have for this release, a number of things could have happened to the rar for the crc to be changed (if srrdb is correct).
If the content of hht-codiw.rar matches then we are good I guess.

Thanks

Thank you for you prompt reply.

I have an additional queston, if possible, please let me know what kind of method you use to verify releases in your collection/library to be certain they indeed belong to The Scene.

 

[formeruser]

Call_of_Duty_Infinite_Warfare_Unlocker-HHT

You do not have permission to view link Log in or register now.

You do not have permission to view link Log in or register now.

Password: gNs7synOXRi1BrqgxlHz

 

[formeruser]

Nevermind, the other upload has the correct SFV and RAR, though the NFO is in the "incorrect" Unix EOF format. There must have been an issue during your download/extraction. If you still have the previous file, please check it against this SHA-256 hash:

bd4e47690898bf9ff7b1ce5b19eeba33d44257f60bf565edd65a66752039f48e *Call_of_Duty_Infinite_Warfare_Unlocker-HHT.rar

 

[Yamato]

There must have been an issue during your download/extraction. If you still have the previous file, please check it against this SHA-256 hash:

bd4e47690898bf9ff7b1ce5b19eeba33d44257f60bf565edd65a66752039f48e *Call_of_Duty_Infinite_Warfare_Unlocker-HHT.rar

You are 100% right. I have done some additional testing from my end.

If Palinkat's archive file is opened with WinRAR (I am using WinRAR 5.80 (64-bit)) to look through the files, it will show the following checksums:

Call_of_Duty_Infinite_Warfare_Unlocker-HHT/hht-codiw.rar 57c83955
Call_of_Duty_Infinite_Warfare_Unlocker-HHT/hht-codiw.sfv 241cf6cf
Call_of_Duty_Infinite_Warfare_Unlocker-HHT/hht.nfo c92868b4

After extracting the files with the help of WinRAR and calculating checksums, they will be exactly the same as above.

However, if the same archive file is extracted with 7-Zip (I am using 7-Zip 19.02 x64), the file checksums will be different from the ones above:

Call_of_Duty_Infinite_Warfare_Unlocker-HHT/hht.nfo 4865da0a
Call_of_Duty_Infinite_Warfare_Unlocker-HHT/hht-codiw.rar 976bca8b
Call_of_Duty_Infinite_Warfare_Unlocker-HHT/hht-codiw.sfv 2158eb3c

They completely match the ones specified at srrdb (including NFO). The most confusing thing is that 7-Zip displays the same checksums as WinRAR does if Palinkat's archive file is just opened with 7-Zip to browse the files. To be honest this is something new to me. I would never imagine that file checksums may be different depending on an application used for data extraction or browsing.

 

[formeruser]

TL;DR: This is a quirk of the RAR5 archive format and not an actual file hash difference.

Spoiler: Explanation

"That is indeed rather odd. I do not use WinRAR though, so I can only speculate that this may have something to do with the archive using encryption but not for the file names."
- My first guess some time ago now...

I was able to reproduce your findings except for the third sentence. Both WinRAR v5.80 (

You do not have permission to view link Log in or register now.

) and 7-Zip v19.02 alpha (

You do not have permission to view link Log in or register now.

) list the "wrong" file hashes in their GUI and from the command-line, but extracting the archive produces files with the same correct CRC32 hashes, most importantly 976BCA8B for hht-codiw.rar.

The cause of this issue is a difference between the RAR4 and RAR5 archive formats, specifically the stored checksum.
Notice how in WinRAR v5.80 the hash column is labeled "Checksum" instead of the usual "CRC32". That is because this archive is a particular combination of two parameters: RAR4/RAR5 and plaintext/encryption/full encryption. To illustrate this, here are commands to create and parse all six possible variations:

Spoiler: Script

Switches:
-ma[4|5] Specify a version of archiving format
-m<0..5> Set compression level (0-store...3-default...5-maximal)
-p[password] Set password
-hp[password] Encrypt both file data and headers

$ Rar.exe a 4a.rar -ma4 -m0            Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 4b.rar -ma4 -m0 -phunter2  Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 4c.rar -ma4 -m0 -hphunter2 Call_of_Duty_Infinite_Warfare_Unlocker-HHT

$ Rar.exe a 5a.rar -ma5 -m0            Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 5b.rar -ma5 -m0 -phunter2  Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 5c.rar -ma5 -m0 -hphunter2 Call_of_Duty_Infinite_Warfare_Unlocker-HHT

$ Rar.exe lt           4a.rar | grep -m 1 CRC32
$ Rar.exe lt           4b.rar | grep -m 1 CRC32
$ Rar.exe lt -phunter2 4c.rar | grep -m 1 CRC32
$ Rar.exe lt           5a.rar | grep -m 1 CRC32
$ Rar.exe lt           5b.rar | grep -m 1 CRC32
$ Rar.exe lt -phunter2 5c.rar | grep -m 1 CRC32
    CRC32: 976BCA8B
    CRC32: 976BCA8B
    CRC32: 976BCA8B
    CRC32: 976BCA8B
CRC32 MAC: CENSORED
    CRC32: 976BCA8B

$ Rar.exe lt Call_of_Duty_Infinite_Warfare_Unlocker-HHT.rar | grep -m 1 CRC32
CRC32 MAC: 57C83955

As you can see, only 5b.rar has the wrong hash and MAC was appended to the hash name.
You can see that Call_of_Duty_Infinite_Warfare_Unlocker-HHT.rar is the same combination as 5b.rar because it is RAR5 (see the last paragraph of the spoiler or alternatively click on the "Info" button in WinRAR) and is encrypted (hence the password), though only the data, since opening it lets one see the metadata such as directory and file names without having to enter a password.
Encrypted archives (both RAR and 7-Zip) are never identical even if created with the exact same command and files to prevent certain kinds of cryptographic attacks, but the decrypted contents including the metadata obviously match. In the above-mentioned special case though, the CRC32 MAC changes each time:

Spoiler: Script

$ Rar.exe a 1a.rar -ma5 -m0            Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 1b.rar -ma5 -m0            Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 2a.rar -ma5 -m0 -phunter2  Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 2b.rar -ma5 -m0 -phunter2  Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 3a.rar -ma5 -m0 -hphunter2 Call_of_Duty_Infinite_Warfare_Unlocker-HHT
$ Rar.exe a 3b.rar -ma5 -m0 -hphunter2 Call_of_Duty_Infinite_Warfare_Unlocker-HHT

$ Rar.exe lt           1a.rar | grep -m 1 CRC32
$ Rar.exe lt           1b.rar | grep -m 1 CRC32
$ Rar.exe lt           2a.rar | grep -m 1 CRC32
$ Rar.exe lt           2b.rar | grep -m 1 CRC32
$ Rar.exe lt -phunter2 3a.rar | grep -m 1 CRC32
$ Rar.exe lt -phunter2 3b.rar | grep -m 1 CRC32
    CRC32: 976BCA8B
    CRC32: 976BCA8B
CRC32 MAC: AAAAAAAA
CRC32 MAC: BBBBBBBB
    CRC32: 976BCA8B
    CRC32: 976BCA8B

Just in case it is not obvious, this

You do not have permission to view link Log in or register now.

is a defensive measure for archives that have encrypted file data but plaintext headers, which is why it is not used for fully encrypted archives. To quote the

You do not have permission to view link Log in or register now.

:

File encryption record
This record is present if file data is encrypted.
[...]
0x0002 Use tweaked checksums instead of plain checksums.
If flag 0x0002 is present, RAR transforms the checksum preserving file or service data integrity, so it becomes dependent on encryption key. It makes guessing file contents based on checksum impossible. It affects both data CRC32 in file header and checksums in file hash record in extra area.

The latest version of the unrar source code (

You do not have permission to view link Log in or register now.

) gives further insight:

Spoiler: Code

# list.cpp:336
if (hd.FileHash.Type==HASH_CRC32)
  mprintf(L"\n%12ls: %8.8X",
    hd.UseHashKey ? L"CRC32 MAC":hd.SplitAfter ? L"Pack-CRC32":L"CRC32",
    hd.FileHash.CRC32);

# headers.hpp:226
// Use HMAC calculated from HashKey and checksum instead of plain checksum.
bool UseHashKey;

// Key to convert checksum to HMAC. Derived from password with PBKDF2
// using additional iterations.
byte HashKey[SHA256_DIGEST_SIZE];

# arcread.cpp:1049
hd->UseHashKey=(Flags & FHEXTRA_CRYPT_HASHMAC)!=0;

# headers5.hpp:103
#define FHEXTRA_CRYPT_HASHMAC  0x02 // Use MAC for unpacked data checksums.

# hash.cpp:274
bool DataHash::Cmp(HashValue *CmpValue,byte *Key)
{
  HashValue Final;
  Result(&Final);
  if (Key!=NULL)
    ConvertHashToMAC(&Final,Key);
  return Final==*CmpValue;
}

# crypt5.cpp:193
void ConvertHashToMAC(HashValue *Value,byte *Key)
{
  if (Value->Type==HASH_CRC32)
  {
    byte RawCRC[4];
    RawPut4(Value->CRC32,RawCRC);
    byte Digest[SHA256_DIGEST_SIZE];
    hmac_sha256(Key,SHA256_DIGEST_SIZE,RawCRC,sizeof(RawCRC),Digest,NULL,NULL,NULL,NULL);
    Value->CRC32=0;
    for (uint I=0;I<ASIZE(Digest);I++)
      Value->CRC32^=Digest[I] << ((I & 3) * 8);
    Value->CRC32&=0xffffffff; // In case the variable size is larger than 32-bit.
  }
[...]
}

In combination with the miniscule GUI label change, that does not adequately explain the situation at all, an unsuspecting user is led to assume that the actual file hashes are different.
Though 7-Zip is also quite bad as the column is always called CRC and since

You do not have permission to view link Log in or register now.

the rows are simply blank with the following bullet point in the changelog: "Speed optimizations for hash caclulation [sic]: CRC-32, CRC-64, BLAKE2sp". I guess it really is that much quicker to just leave it out completely...

In the end this may not have been another case of old programs causing issues, but the real question remains: Why you are still using those ancient software versions. WinRAR v5.80 is

You do not have permission to view link Log in or register now.

and 7-Zip v19.02 is an alpha

You do not have permission to view link Log in or register now.

.
Unless you have a good reason not to, you should probably update

You do not have permission to view link Log in or register now.

(

You do not have permission to view link Log in or register now.

).
While you are at it, you might as well install the latest version of WinRAR (

You do not have permission to view link Log in or register now.

), then apply the following crack courtesy of BTCR to prevent the nagging:

Spoiler: Crack

1. Open WinRAR.exe in a hex editor such as

You do not have permission to view link Log in or register now.

(

You do not have permission to view link Log in or register now.

).
2. Go to (CTRL+G) B5A30.
3. Replace the first two bytes at that location (8A C3) with B0 01 by just typing the latter without the space.
4. Save the file (CTRL+S) and close the hex editor.
5. If you plan on using the command-line version, repeat the previous steps with Rar.exe but go to 1ADAA instead.
These offsets are for WinRAR v7.01.