Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code
My View | View Issues | Change Log | Roadmap | Doomseeker Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004099DoomseekerWadseeker sitespublic2023-02-12 18:512023-02-15 07:18
ReporterNecrodoom 
Assigned ToZalewa 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version1.4.0 
Target VersionFixed in Version1.4.1 
Summary0004099: allfearthesentinel.net changing to allfearthesentinel.com
DescriptionDue to a DNS issue, TSPG's DNS has changed, so wadseeker has to change accordingly. Maybe automatically redirect URLs on wadseeker if they refer to .net.
Attached Files

- Relationships

-  Notes
User avatar (0022761)
Zalewa (developer)
2023-02-12 19:29

 Domain amended:'https://bitbucket.org/Doomseeker/doomseeker/commits/c8d36dae4733c85b8b88a95df146e11c07c6a4df [^]'
User avatar (0022766)
Necrodoom (reporter)
2023-02-13 17:24

 Is it a good idea to also auto-redirect URL if wadseeker detects the old URL? Incase people had the website configured manually.
User avatar (0022768)
Zalewa (developer)
2023-02-13 22:24

 Mucking with user choices behind the scenes and making custom exceptions for special cases is not the way I usually like to do thing. I'm considering between not doing it, doing a one-time rewrite of user config on the next update, or on parsing the URLs and aliasing this website when the sites are passed from Doomseeker's config to Wadseeker.

Let me think on that.
User avatar (0022770)
WubTheCaptain (reporter)
2023-02-14 06:47

 Doomseeker should not become an IRC client, a HTTP web proxy, ...

It's up to the webmaster of said domain to do the HTTP redirect. If they can't, sucks to suck, take it as a lesson.
User avatar (0022771)
WubTheCaptain (reporter)
2023-02-14 06:57

 A more universal solution which should work with any Doomseeker version too: Use a different DNS resolver (as long as it doesn't conflict with DNSSEC). You might even get a benefit of setting up one for DNS-based adblocking in your private network, if that's your thing.
User avatar (0022772)
Necrodoom (reporter)
2023-02-14 16:33

 You do rise a good point, Wub, it doesnt feel like it should be doomseeker's department to handle issues like this, since doomseeker is its own project and is not strictly affiliated with TSPG to begin with. I guess its up to yall if its a good idea or not. My concerns were mostly oriented around the end user using doomseeker as the front end of all things zandronum and what would happen if the old domain was snatched up by a malicious actor.
User avatar (0022774)
Zalewa (developer)
2023-02-14 22:48
Quote from Necrodoom
What would happen if the old domain was snatched up by a malicious actor

With all the ways the WADs, PK3s and DEHs can be easily and uncontrollably distributed, this has always been a problem, and snatching up a domain doesn't change anything. I think we didn't have a major exploitation by a WAD file only because nobody tried anything with the WADs, yet (or maybe they did and were successful?). doom2.exe certainly has WAD related exploits that permit arbitrary code execution (tip: don't run WADs in doom2.exe, even if it's in Dosbox). Do ports have such exploits?
Quote from Necrodoom
My concerns were mostly oriented around the end user using doomseeker as the front end of all things zandronum

Yes that's my concern too. That's also why Doomseeker offers certain features that would be considered as out-of-scope for a server browser.

But, nevertheless, the problem of a dead WAD site domain is mitigated by the fact that the primary source of WADs for all servers should be the custom URL configured by the server host. If all the hosts who previously referred to the .net domain change the URL to .com, Doomseeker will keep finding the WADs just as well as before. Because of this, and because sites go offline all the time, and also because I have a bad luck for bugging such code I opt to not add the domain translator.
User avatar (0022775)
Zalewa (developer)
2023-02-15 07:18

 I've realized that yet again we're meticulously discussing and picking apart something that should be a simple string replace. Enough.

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-02-12 18:51 Necrodoom New Issue
2023-02-12 19:29 Zalewa Note Added: 0022761
2023-02-12 19:29 Zalewa Assigned To => Zalewa
2023-02-12 19:29 Zalewa Status new => needs review
2023-02-13 17:24 Necrodoom Note Added: 0022766
2023-02-13 22:24 Zalewa Note Added: 0022768
2023-02-14 06:47 WubTheCaptain Note Added: 0022770
2023-02-14 06:57 WubTheCaptain Note Added: 0022771
2023-02-14 16:33 Necrodoom Note Added: 0022772
2023-02-14 22:48 Zalewa Note Added: 0022774
2023-02-15 07:18 Zalewa Note Added: 0022775
2023-02-15 07:18 Zalewa Status needs review => resolved
2023-02-15 07:18 Zalewa Fixed in Version => 1.4.1
2023-02-15 07:18 Zalewa Resolution open => fixed




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker