•   Please read these simple rules before you request:

    1. Before requesting, always search with the FULL release name in the search box. The "is this being discussed" window is not a search engine.
    2. You can make up to 10 requests (including RE-UP) per day (24h period) to avoid abuse.
    3. Include a link with info about the release, typically from srrDB or PreDB.
    4. Once your request has been fulfilled, edit the thread and mark it with the prefix "FILLED".
    5. Show your gratitude by thanking the user with a Like, do not reply with "thank you" messages.
    6. If a link is dead, leave a reply asking for a re-up instead of making a new topic.
    7. Fillers should prioritize user-friendly hosts with decent retention when possible.

      Updated on 2025-04-30.

FILLED Hex.Rays.IDA.Pro.v9.0.240925-HEXRAYS

4

4yd4pr0

Member
Joined
13 Oct 2024
Messages
1
Appreciation score
0
the files seems ok, except the nfo. the crc32 from the original links (scnlog.me/apps/hex-rays-ida-pro-v9-0-240925-hexrays --- the ddownload is the only working link) is 3507B2B7. but the crc32 of the nfo from these two links is 33265862. any idea which one of the nfos (or crc32 checksums) is not corrupted?

thanks.
 
F

formeruser

LEGEND
Joined
9 Jun 2023
Messages
3,955
Appreciation score
9,688
TL;DR: The upload in this thread is "correct".

Neither NFO is "corrupted" in the sense of being incomplete or having been modified as both files clearly contain the exact same visible text. The difference comes from the EOL format the NFOs were saved in. This modifies the file's binary data by changing all instances of 0x0D 0x0A to simply 0x0A, which decreases the size by 1 byte for each line and causes a different hash to be calculated.

Conversion between the EOL formats can easily be done with
You do not have permission to view link Log in or register now.
(Edit -> EOF conversion) or from the terminal (note the hashes):
Code: 
# apt install libarchive-zip-perl
$ file idaprov9.nfo && crc32 idaprov9.nfo
idaprov9.nfo: ASCII text, with CRLF line terminators
33265862

# apt install dos2unix
$ dos2unix idaprov9.nfo 2> /dev/null && file idaprov9.nfo && crc32 idaprov9.nfo
idaprov9.nfo: ASCII text
3507b2b7

$ unix2dos idaprov9.nfo 2> /dev/null && crc32 idaprov9.nfo
33265862

Both admin's source ("AXX") and that of the srrDB upload have a Unix EOL format NFO, which may have been caused by a misconfigured FTP client as speculated in the last paragraph of the comment linked above. This would also explain why the NFOs of some non-0DAY scene releases "leak" to P2P in the Unix EOL format, but their SFVs all still use the standard Windows one.
Though for this particular release one can be certain which EOL format is "correct" because rule 2.3 of the current
You do not have permission to view link Log in or register now.
requires an NFO to be "included in at least the first disk of the release" (most groups put them into all ZIP parts) and all eleven match the Windows CRC32 shown above:
Code: 
$ 7z l -slt "Hex.Rays.IDA.Pro.v9.0.240925-HEXRAYS/*.zip" idaprov9.nfo | grep ^CRC
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
CRC = 33265862
 
H

heavenlyphoenix

Member
Joined
3 Sep 2024
Messages
67
Appreciation score
7
The difference is only spaces or LF CR !
 

Attachments

  • Screenshot from 2024-10-29 11-20-21.png
    Screenshot from 2024-10-29 11-20-21.png
    214.3 KB · Views: 26
You must log in or register to reply here.
Top Bottom