Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004152Zandronum[All Projects] Bugpublic2023-08-05 23:272024-03-10 19:53
Reporterpkmx 
Assigned ToKaminsky 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionwon't fix 
PlatformLinuxOSArch LinuxOS Version
Product Version3.2 
Target VersionFixed in Version 
Summary0004152: 3ha3.wad conflicts with Zandronum's AUTHINFO special lump
Description3 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.
Steps To Reproduce$ 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.
Additional InformationNot sure what is the best way to fix it, maybe this wad can be detected by checksum and specifically disallow AUTHINFO parsing?
Attached Files

- Relationships

-  Notes
User avatar (0023338)
Kaminsky (developer)
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.

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2023-08-05 23:27 pkmx New Issue
2023-08-06 03:59 Kaminsky Product Version 4.0-beta => 3.2
2024-03-10 19:53 Kaminsky Note Added: 0023338
2024-03-10 19:53 Kaminsky Status new => closed
2024-03-10 19:53 Kaminsky Assigned To => Kaminsky
2024-03-10 19:53 Kaminsky Resolution open => won't fix






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker