The recent problem of obfuscated filenames in rar sets

[jnaes]

This is how many posts are now appearing on Usenet. The problem is that SAB cannot extract or process these rar sets properly.

Is there any plan to implement a fix for something like this? It's a growing problem that will only get worse if files continue to be posted this way, and they are increasingly so right now.

[jnaes]

Also note that this can be fixed manually by (Windows) simply highlight all rars+pars and renaming to a common filename. This is no problem if the rars are sequentially named (.r01, .r02, etc.)

[sander]

Out of curiosity: can you PM a link to such a NZB? I would like to experience it myself.

[nawo69]

I have PM you a zip with a few nzb causing the same problem for me

[sander]

Thanks for the NZB. I tried the first one (D*...), and indeed SABnzbd got a problem due to all the different names.

Do you have any idea why the obfuscated filenaming is done?

From the SABnzbd result popup:

Unpack
[5500f3a9101ed9e2881373e0ca99ee8c] Unpacking failed, unable to find 5500f3a9101ed9e2881373e0ca99ee8c.r20
[16b2b1431cc8a7fc370d44adbaf162f3] Unpacking failed, unable to find 16b2b1431cc8a7fc370d44adbaf162f3.r03
[4e24abade62d97377d222000cd19bc8f] Unpacking failed, unable to find 4e24abade62d97377d222000cd19bc8f.r02
[6c829be842be9c9d4eb91002e04744f0] Unpacking failed, unable to find 6c829be842be9c9d4eb91002e04744f0.r05
[b4ebb2e0083cd5bf22212c5d60c38ae2] Unpacking failed, unable to find b4ebb2e0083cd5bf22212c5d60c38ae2.r14
[39fadd6efe2523c610ac1117a9038250] Unpacking failed, unable to find 39fadd6efe2523c610ac1117a9038250.r19
[6254d07755605b0c7609c2fb917cbebb] Unpacked 0 files/folders in 0 seconds
[1d48b35f03757de491d4fdb5a2aa7f86] Unpacking failed, unable to find 1d48b35f03757de491d4fdb5a2aa7f86.r21
[4eb736035af0256390cd8b8f7891a69d] Unpacking failed, unable to find 4eb736035af0256390cd8b8f7891a69d.r12
[ee5d2791362bc0c1aef959de83188b1d] Unpacking failed, unable to find ee5d2791362bc0c1aef959de83188b1d.r07
[4b1cdddf81071b1648368b45d47d2fe3] Unpacking failed, unable to find 4b1cdddf81071b1648368b45d47d2fe3.r09
[1ed35dc89846c86762a2da4fe8369029] Unpacking failed, unable to find 1ed35dc89846c86762a2da4fe8369029.r22
[b3f358777a792d0be408d1f762b06e81] Unpacking failed, unable to find b3f358777a792d0be408d1f762b06e81.r18
[08f7fd6d0aec18221b3d5985ee0f31bb] Unpacking failed, unable to find 08f7fd6d0aec18221b3d5985ee0f31bb.r10
[27f7feb758a0686f7e0e34e2555a9e8e] Unpacking failed, unable to find 27f7feb758a0686f7e0e34e2555a9e8e.r16
[87dd3b505f602f577cb8cb565b20636a] Unpacking failed, unable to find 87dd3b505f602f577cb8cb565b20636a.r13
[06859fac541fd979e5ac52130dea5329] Unpacking failed, unable to find 06859fac541fd979e5ac52130dea5329.r15
[b9e30088047aad73d5f1ab31710d8c64] Unpacking failed, unable to find b9e30088047aad73d5f1ab31710d8c64.r08
[367f23a40d1e7e541bb9d8068c5c0d5e] Unpacking failed, unable to find 367f23a40d1e7e541bb9d8068c5c0d5e.r06
[03352be4717848b769b545db061b0b6b] Unpacking failed, unable to find 03352be4717848b769b545db061b0b6b.r00
[fcdb09be2c253e7b5edb569bdab63a42] Unpacking failed, unable to find fcdb09be2c253e7b5edb569bdab63a42.r17
[367ca9a142dffcc2ee8b21ff21f60ba9] Unpacking failed, unable to find 367ca9a142dffcc2ee8b21ff21f60ba9.r04
[1fe660b74da15ddb8993da818d38158b] Unpacking failed, unable to find 1fe660b74da15ddb8993da818d38158b.r01
[74e8afaa8d06c46c7e9ab080f8a255e9] Unpacking failed, unable to find 74e8afaa8d06c46c7e9ab080f8a255e9.r11

Repair
[03352be4717848b769b545db061b0b6b.rar] Quick Check OK

[nawo69]

No idea just Sickbeard picked them up from a popular nzbs site

[jnaes]

Do you have any idea why the obfuscated filenaming is done?

I have heard that it's done in order to prevent DMCA takedowns. I am guessing that NZB sites on their own are somehow matching the hashes with post titles through another party.

[sander]

Just for fun: If you run the piece of code below on the directory containing the obfuscated filenames, the "unrar x *.rar" then works.

Code: Select all

import os, glob

prefix = 'just-a-name'

for filename in glob.glob("*.r*"):
	extension = filename.split('.')[-1]
	newname = prefix + '.' + extension
	os.rename(filename, newname)

Some regexp checking on r[\d\d] would be nice. And counting rar, r01, r02, etc, to detect double rar's

[friendsfan]

ok, using this thread, because my problem is kinda related. under all those obfuscated rars (whether they are all named the same or not), are some that causing sabnzbd to stop download due to an disk error (which is not the case actually). Reason seems to be when the last charakter of the name is "=". if you just unpause the download it will eventually finish the download. I use sab under windows, not sure if nix handles that better.

Code: Select all

2013-07-20 15:38:18,913	FEHLER:	Festplatten-Fehler beim Anlegen der Datei C:\Users\xxx\Documents\Downloads\incomplete\Falling Skies S03E03 Der Baum der Freiheit GERMAN DUBBED 720p HDTV x264 ZZGtv\17f53674286af344a92a8754c4e59e55.RmFsbGluZy5Ta2llcy5TMDNFMDMuRGVyLkJhdW0uZGVyLkZyZWloZWl0LkdFUk1BTi5EVUJCRUQuNzIwcC5IRFRWLngyNjQtWlpHdHY=.vol032+

Code: Select all

2013-07-19 21:14:37,325	FEHLER:	Festplatten-Fehler beim Anlegen der Datei C:\Users\xxx\Documents\Downloads\incomplete\The.Vampire.Diaries.S04E21.Das.letzte.Mittel.GERMAN.5.1.DUBBED.DL.720p.WebHD.h264-euHD\d33b9f8d9a172cc330ed4b2fe6dd43b6.VGhlLlZhbXBpcmUuRGlhcmllcy5TMDRFMjEuRGFzLmxldHp0ZS5NaXR0ZWwuR0VSTUFOLjUuMS5EVUJCRUQuREwuNzIwcC5XZWJIRC5oMjY0LWV1SEQ=.par2

Those are from two different releases, only common thing i see is both file ends with "=".

[shypike]

The total path is above 254. It's not the "=" sign.
Trim your paths, e.g. by setting a value like 50 in Config->Special->folder_max_length

[friendsfan]

The total path is above 254. It's not the "=" sign.
Trim your paths, e.g. by setting a value like 50 in Config->Special->folder_max_length

ah, okay then, i give it a try. i wasnt thinking of that, because when i ran into that problem a while back, there was actually a specific error that stated the fact with the path and not something bout HDD Error...

thx