logging into pirate Client

[shadowman123]

Well i Tried to log on The Pirate Client But what happened is the login bar got freezed at middle of Bar So what does this means ? and how can i Make it logging into this Client ?

[JobvdH]

You need the new game keys and tje new password encryption.
Goodluck with that because it ain't public.

[shadowman123]

Originally Posted by JobvdH

You need the new game keys and tje new password encryption.
Goodluck with that because it ain't public.

Cryptography pass ? i guess if the Cryptography was Wrong it wouldnt even start loading and simply would say "Server maintaince or Network Congested" or what ?

[JobvdH]

Ofcourse not if your ports are open it attempts to connect no mather if the cryptographers are wrong or not.

[Kiyono]

The login cryptography stayed the same which is why the bar starts, the game cryptography is what changed and that's why you get stuck.

[shadowman123]

Originally Posted by Kiyono

The login cryptography stayed the same which is why the bar starts, the game cryptography is what changed and that's why you get stuck.

So what u mean is that the Auzorization packet is still the same but what i understood that game cryptography has changed so thats Require knowing its Password and its keys Am i Right ?

[JobvdH]

Auth packets has nothing to do with login encryption

[shadowman123]

So what does it do Exactly

[Spirited]

Originally Posted by JobvdH

Auth packets has nothing to do with login encryption

Yah, they do. Packets being sent to the server / client (auth or game) can be used for encryption. Packet 1059 (the key packet) was is used in 5172 - 5532 to set the key for the password cipher. Exchange also uses packets to exchange public keys and prepare the game cipher.

[JobvdH]

Originally Posted by Fаng

Yah, they do. Packets being sent to the server / client (auth or game) can be used for encryption. Packet 1059 (the key packet) was is used in 5172 - 5532 to set the key for the password cipher. Exchange also uses packets to exchange public keys and prepare the game cipher.

What I ment was that in this situation it won't help to change packets, you'll need the keys.

[Spirited]

Originally Posted by JobvdH

What I ment was that in this situation it won't help to change packets, you'll need the keys.

Well... yes... the keys did change... but uhm... so did the cipher.

[JobvdH]

Yes, I do agree with that point.

[-impulse-]

You wasn't able to connect beacause the authenthincation sequence changed. If you manage to generate packets alike you will be able to get to the game server, obviously not with client's password. Whatever packets you send, the client will always send different things in the auth seq. As for the game crypto, it suffered some change on how the public key is handled. Almost all people that have an it, well most people who know how to code a server... Ask around maybe you get lucky.

[_DreadNought_]

nevermind.

[Spirited]

Originally Posted by _DreadNought_

(this might be the old auth sequence or the new one)
I thought it was something like:
Auth:
1060
1100
1052

Game:
1051
1001
1052
10010

1051 in the game cipher? o.O
I don't think it's ever been like that.
1059 --> client
1060 --> server
1055 --> client
1100 --> server
1052 --> server
was the account server's sequence until recently.

Then the game client went along the lines of...
1052 --> server
1004 --> client (ANSWER_OK)
1006 --> client
10010:74 --> server
10010:74 --> client
etc.

And nah. Your cipher edit is all wrong o.o