Rig'n'Roll enq files (again)

[RacingSoundtracks]

Hello,

Back on ZenHAX forums, there was a thread where someone also asked about these ENQ files found in Rig'n'Roll game - see this thread - and I assume I'm not supposed to reply or re-launch these threads.

Anyway, is there anyone who ever tried to figure out how 1C / SoftLab encrypted the audio files (music in radio stations)? This game is also known as "Дальнобойщики 3" as well in Russia.

The general principle of this game's data storage was around hiding a lot of information from being modified, but someone figured out how to decrypt some of the data - see https://github.com/JosueCA/RigNRoll-modding

Sadly, the tool presented there cannot be applied to the audio files, that use ENQ file format, which is obviously not any kind of common audio format, but rather some encrypted or encoded data, so the game recognizes that it needs to be decoded / decrypted during runtime. Given two examples that I attach (had to change the extension to PDF to make it accepted to upload) that are pretty pointless without the access to the game and starting reverse engineering) show that first bytes of both files are pretty much the same, so I would expect some kind of similar "decoded" header like RIFF-WAVfmt to be there.

I haven't gone down the rabbit hole of debugging with Ghidra + x64dbg to figure it out, so far I only noticed that the game executable has references to functions like " fm_decoder::decode_portion()" or " fm_dlg_system::play_file()". I think one of the DLLs mentioned AES generation with random IV but I haven't tried using any tools to see if any AES key can be found within the exe or game's memory dump.

Game is available on Steam - here - and these functions definitely exist in that release, but it is probably easier to investigate standalone release with DLC mentioned in GitHub repository

Would be great to see if someone already tried or wants to try it - this encryption remains a mystery up to this day and I haven't made any progress, although I only barely touched reverse engineering in the past and maybe I'm not giving myself more time to spend on debugging.

 

Harsh=01.pdf Harsh=02.pdf