This script should also do verify other variations in lock/PK strings:
Thanks,OLDoMiNiON wrote:- Client with DC++ tag, and random lock & pk strings
- Client w/ DC++ tag, and other non-dc++ lock & pk strings. e.g. too many "ABC"'s in pk.
- Cleint w/ DC++ tag, showing a client version different to that shown in the pk string
- Client w/ DC++ tag\NMDC, with blank lock or pk string
- Client w/ or without DC++ tag, which has a lock of all "A"'s, and a pk of all "B"'s
- Client w/ Incomplete DC++ or DC Gui tag
- Client w/o tag, with only one of either lock or pk
- Client w/o tag, with a pk string <> 16 chars in length
- Client w/o tag, with a lock string outside the min/max char length of a lock string. (whatever that is )
- Client w/o tag, with a static lock string (in NMDC it changes upon each new connection from client-client)
- Client w/o tag, with DC Gui lock and pk
- Client w/o tag, with DC++ lock and pk
[PT]Devilishly