Printable View
I don't hate myself, I just hate having to repeat myself. Totally different thing.
If someone says "I can do it" or "I've done it" then it means "ner ner na ner ner, you can't fix it, I'm better than you", because if they where going to tell us, they would have done so while they where going to the effort of making a post. There's no point encouraging their playground antics by saying "awww, go on, tell us, pleeeeeaase... MOM! Brian won't let me play with his stuff!". ;)Spoiler:
for fix this erros, "20 20 20 20 " u can do two things, all afther the server recive the package.
1) see if in package have same "20" value and fill it.
2) count the number of character in the package and .... fill it =D
the most dificult is , how you will do that... well, a simple kernel function works fine here. but, keep in you mind ... you need to do a fast way to fix, becouse the package recive is a way to cause a delay in server.
theres another way to fix...
chage the 'port/package' of you server (6E 4e ... ) but, if anyone gets this info ... you will down again.
@bob this is good for u ?? (@off)( tnks for that client )
Hex code 0x20 is usually a space character, no? (character 32 decimal) So they just padding, and you could use something like the classic BASIC TRIM$ command / function.
What I was suggesting was, if the buffer should be a fixed length buffer, just make sure the last character in the buffer is always filled with a null. That's very fast and efficient.
If there is a valid terminator before, this wont hurt. If not, it will cure. No logic or testing is required, see?
You'd have to perform this operation after all decryption and decompression, and before any further processing. Ofc.