View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001823 | unreal | ircd | public | 2004-05-19 07:00 | 2004-05-26 21:32 |
| Reporter | A-KO | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | 3.2 | ||||
| Summary | 0001823: Deny version by build date and time | ||||
| Description | The ability to deny links to servers using the deny version {} by using the build date and build time of the server software in use. | ||||
| Additional Information | This would allow a user of self-compiled versions of the software to be able to distinguish between links that are using the original UnrealIRCD or are using the proper self-compiled copy. Just the version code alone is not enough to distinguish between the original and self-compiled copy. | ||||
| 3rd party modules | |||||
|
|
How so? I could build a custom build today, or I could build it a week from now. Furthermore, we do not support source modification. |
|
|
codemastr: I understand that you guys do not support source modification, but otherwise making sure of this would involve a module of itself to verify the build date and time of the server. Build version checking already exists within the software. I am only proposing an extension to check build dates. Alternatively, you can look at this from the other way around. Granted we all should only link with other servers with Administrators that we trust, but what if one of them were to load a self-compiled version of unrealircd with modules that happen on their server that don't exist on the entire network? (Keep in mind that I'm still talking about Win32 here) There is no method of validating that this user is in fact using the ACTUAL build of UnrealIRCD released by you guys. |
|
|
Erm. Correct me if I am wrong, but isnt build date set when you compile? So, even if you compiled one second out, they would have different times. Perhaps some kind of checksum would be better, but what do I know... As for checking for modules, try /modules |
|
|
the /module command does not properly report what modules are loaded in the Win32 compilation because they are compiled directly into the source code and as of yet it does not function with external modules like the *nix variant of the software. And that's the point of my request for this feature. The build date is set when you compile. If you want to make sure all servers on your network are utilizing that build date, there ought to be an option for this. It can be argued, again, that they do not support self-compiled versions of the software. However, I stated in a previous post that such a function can prove useful even for people who use the UnrealIRCD provided by the developers. And yes, a checksum would be even better in this scenario. |
|
|
I think this bug can be closed. The modules@win32 thingy is also no longer a issue since in current cvs / 3.2.1 windows supports modules (as dll files). Furthermore.. if someone is deliberately launching a modified ircd there's not much you can do. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-05-19 07:00 | A-KO | New Issue | |
| 2004-05-19 13:31 |
|
Note Added: 0006337 | |
| 2004-05-19 19:41 | A-KO | Note Added: 0006341 | |
| 2004-05-19 19:52 | w00t | Note Added: 0006342 | |
| 2004-05-19 20:06 | A-KO | Note Added: 0006344 | |
| 2004-05-26 21:32 | syzop | Status | new => closed |
| 2004-05-26 21:32 | syzop | Note Added: 0006438 |
