• Welcome to Valhalla Legends Archive.
 
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Hdx

#1
1) What is that gif really?
And 2) this is good. Does it change anything? No, but yay!
#2
As on the PvPGN (I assume) forum, this is not tech support for there products. As they are unrelated to this website at all.
#3
http://en.wikipedia.org/wiki/RSA
As I said in my old post its been a while, and again, it's been a while.
But it's 128-byte(1024-bit) not 128-bit.
N is the modulus which is agreed upon before hand, so is K. (In the image bellow, K is d)

QuoteDecryption:

Alice can recover m from c by using her private key exponent d by the following computation:

Given m, she can recover the original message M by reversing the padding scheme.
(In practice, there are more efficient methods of calculating cd using the pre computed values above.)
The 0xBB's are used to pad the message up to a 128 byte boundary. So basically after decryption the signature looks like this:
11223344BBBBBBBBBBBB......etc where 11223344 is the server's IP.
So the reason you are failing is because the Game is seeing:
3FF1530CBBBBBBBB.... When its expecting:
7F000001BBBBBBBB....

Anyways, if you're thinking of generating a fake signature, STOP NOW it uses a 1024-bit private key, which you will NEVER be able to figure out.
So your best bet is to remove the check itself from the client. This is actually rather simple, just look for the Modulus (N) in the game's files. (I think it's in Game.dll) track it around to where it's used, and then make that function 'return true;' You'l have to do your own checkrevision, but thats really simple these days.



#4
You can't without modifying the client. And I doubt anyone has the locations you'd need to change on hand.
Also it'd only work on modified clients, so its.. useless.
#5
From the sounds of it he may be working on a PvPGN server. And wants to change the text that shows up when he sends an announcement.
#7
printf("\n%d.%d.%d.%d\n", buffer[17], buffer[18], buffer[19], buffer[20]);
   241.83.18.23
3f  f1 53 12
63.241.83.18
Seems obvious where the bug is to me..
#8
(unsigned byte)buffer[17]; should work.
#9
-15 as a byte in binary is 11110001
241 as a byte in binary is 11110001
It's just a problem with signed vs unsigned.
#10
-15 = F1
Figure it out from there! (Hint: What does F1 =?)
#11
You forgot to call recv()
You created the buffer, but you never filled it with anything.
#12
Its another obvious error.
Follow your flow of code, see what variables are being set to what...
Also, quit double posting, theres an edit button for a reason.
#13
Yes
#14
I don't have one I can readily link. But you should be able to find iago's. Somewhere on his site: http://www.skullsecurity.org/wiki/
#15
I don't think that would actually fix it.
I think it's an issue with your bnls_send parameters.