• Welcome to Valhalla Legends Archive.
 

versioncheckex2 issue.

Started by fuzan, April 22, 2007, 05:51 AM

Previous topic - Next topic

fuzan

#15
Hmm, I just spotted an extra 'C2' byte that's immediately following the IX86ver's null terminator in the BNLS packet and not the S0x50. Furthermore, it seems as if that entire string is mangled. Perhaps this is it! Now to find out where it's coming from.

Skywing

In general, any "lockdown" version check challenge string which does not fit the size limitation of 16 bytes is unlikely to be valid.

Barabajagal

uhm.. no. Lockdown strings are 15, 16, or 17 bytes. There is no limitation.

rabbit

You're arguing with the only guy to have definitely reversed lockdown?  WTF are you smoking?
Grif: Yeah, and the people in the red states are mad because the people in the blue states are mean to them and want them to pay money for roads and schools instead of cool things like NASCAR and shotguns.  Also, there's something about ketchup in there.

tumeria

RealityRipple is obviously addled in the brain o_o;

Hdx

Hes arguing due to the fact that value strings of length 15-17 have been seen in the wild.
Also, from what ive seen, it dosen't care about the length of the value string, it only uses the 1st 16 bytes.
~Hdx

Proud host of the JBLS server www.JBLS.org.
JBLS.org Status:
JBLS/BNLS Server Status

Barabajagal

how can it use the first 16 if there's only 15?