An Immature Admin on a Server my friend and I like to play and have invested hours of time into has serial banned us for no reason what so ever. Additional How to change serial mta selection Basler CCT+ The Basler Camera Configuration Tool Plus (CCT+) is a convenient Windows® based tool that can be used to change settings via a serial connection.
ID Project Category View Status Date Submitted Last Update 0003684 Multi Theft Auto: San Andreas Security public 2008-06-12 -12-02 00:22 Reporter IJs Assigned To ccw Priority low Severity feature Reproducibility N/A Status closed Resolution no change required Product Version Target Version 2.0 Fixed in Version Summary 0003684: Change serial hashing algorithm Description Currently, serials are identified as MD5 hashes which are everything but user-friendly. A different (smaller) hashing algorithm such as 3DES could be used to turn the serials into smaller numbers. Tags No tags attached. The problem is, just making the serials smaller would increase the birthday problem. In my eyes, that doesn't make much sense atm. MD5 is a pretty, lets say, small hash, and even considered outdated since its just a 32 digit hash and prone to collisions and pseudo-collisions.
Up-to-date hashing algorithms would even create a longer serial. Also, I was wondering what serials have to be user-friendly for. The average administrator shouldn't even be able to see that serial, thats a security issue in my eyes. MAC can be changed in few minutes. Be much more effective and more versatile - make more than one serial number, which is based on different data of PC components, and multiple serials, each of which will be MD5 hash of any PC part - HDD, motherboard, processor, video card or something else. Thus, the server owners will not be able to obtain private information about player PC serials.
They will know just MD5 hashes of the data. Each scripter will be free to decide on what serial player should be punished.
Mta Sa Maps
Having a list of serials, scripter can build a logical system of punishments. Suppose we know the serial hashes of HDD, motherboard, processor and video card. Create a ban system, which bans all these parameters.
But at the entrance of each player, check if any of these serial in the blacklist. If this serial is in the blacklist, compare other player serials with those found in the ban record.
If more than 50% of the player serials match the those stored in the ban record, then it really came banned player. ALTERNATIVE METHOD Glue the overall serial from small hashes of PC components serials.
Short hashes may help. Final serial can be of the form: HHHHHHHHMMMMMMMMPPPPPPPPVVVVVVVV, where HHHHHHHH - hash of HDD serial, MMMMMMMM - hash of motherboard serial, and so on. Knowing the hash positions in this general glued serial, you can see exactly what the serial numbers changed by banned player. On this logic scripter can build its own punishment system.
Well the issue description says 'everything but user-friendly.' But I don't see anybody complaining about them, it's not like we ever have to type a serial out. Changing it would cause unnecessary confusion and work. We'd also need a function to convert old serials into new serials (serials that are stored in databases such as custom ban systems and account protection systems) and would that even be possible? If the old serial is a hash there would be no way of knowing the new serial without the client connecting first so that the new serial could be matched to the old one. A load of work for nothing.