MantisBT - Zandronum
View Issue Details
0004152Zandronum[All Projects] Bugpublic2023-08-05 23:272024-03-10 19:53
pkmx 
Kaminsky 
normalminoralways
closedwon't fix 
LinuxArch Linux
3.2 
 
0004152: 3ha3.wad conflicts with Zandronum's AUTHINFO special lump
3 Heures d'agonie 3 (https://www.doomworld.com/idgames/levels/doom2/megawads/3ha3) unfortunately contains a lump named "AUTHINFO" (for author info), which contains just textural information about the megawad. This causes Zandronum to fail when it tries to parse it as the special AUTHINFO lump for lump protection.
$ sha256sum 3ha3.wad
35ecbbdc7a283ae4596c75e414c137c1abe6dce9a18bdbb9e7592c54137b7e05 3ha3.wad

$ zandronum -iwad DOOM2.WAD -file 3ha3.wad
Authenticating custom protected lumps.
Script error, "3ha3.wad:AUTHINFO" line 1:
Unknown option '', on line 1 in AUTHINFO.
Not sure what is the best way to fix it, maybe this wad can be detected by checksum and specifically disallow AUTHINFO parsing?
No tags attached.
Issue History
2023-08-05 23:27pkmxNew Issue
2023-08-06 03:59KaminskyProduct Version4.0-beta => 3.2
2024-03-10 19:53KaminskyNote Added: 0023338
2024-03-10 19:53KaminskyStatusnew => closed
2024-03-10 19:53KaminskyAssigned To => Kaminsky
2024-03-10 19:53KaminskyResolutionopen => won't fix

Notes
(0023338)
Kaminsky   
2024-03-10 19:53   
Using the MD5 hash of the WAD in question and ignore parsing any AUTHINFO lumps found in it as a workaround will be hacky and overkill at best. I don't think there's any other case where we have to check the MD5 hash of a WAD and forbid parsing any special lumps or anything.

It's unfortunate that introducing AUTHINFO in 3.2 has unknowingly created conflicts like this. However, in this case, I think the best solution might be if somebody modifies "3ha3.wad" and renames that lump to something else (e.g. "AUTHORS") that won't get treated as a special lump and parsed.