Int pk password

Hi all, last update GMs change password config.pk. Anyone have new password?

Thx

Im trying to crack it but it takes ages with bruteforce :P If anyone got a more easy solution would be very appreciated ... hopefully someone comes up before my CPU burns out. Else i will post here as soon as i get it. Im at PW lenght of 8 now and Y6VD.... is the entry point if you wanna help set it at length of 10-12 or something like that and let me know.

Quote:

Originally Posted by PsyoO Im trying to crack it but it takes ages with bruteforce :P If anyone got a more easy solution would be very appreciated ... hopefully someone comes up before my CPU burns out. Else i will post here as soon as i get it. Im at PW lenght of 8 now and Y6VD.... is the entry point if you wanna help set it at length of 10-12 or something like that and let me know.

I quest its not only the password they change, so even you got the password still wont work.

But its better that way :D no more annoying mocker cd hack.

Quote:

Originally Posted by valzzz40 I quest its not only the password they change, so even you got the password still wont work. But its better that way :D no more annoying mocker cd hack.

U know that skills cd is stored on the server and compared so its not related to .pk bugs at all xD ?

Quote:

Originally Posted by valzzz40 I quest its not only the password they change, so even you got the password still wont work. But its better that way :D no more annoying mocker cd hack.

And did u get the pw yet or anything related to say its not just the pw ? All i can think of is they change the key on encryption aswell but that still wouldnt be a big hold, i doubt they change the whole system as they are always cheap with updates and thats a big change already.

Quote:

Originally Posted by PsyoO U know that skills cd is stored on the server and compared so its not related to .pk bugs at all xD ? And did u get the pw yet or anything related to say its not just the pw ? All i can think of is they change the key on encryption aswell but that still wouldnt be a big hold, i doubt they change the whole system as they are always cheap with updates and thats a big change already.

I have no knowledge of cracking password... but someone did and he said that they changed also AES so that's the only thing that i can say.

Been at it today as well myself and to prevent your CPU from having a meltdown at brute forcing: GP6Gn8#Nrr9P6

Credits go to Borsti and Mahatma also! :)

Woot thx a lot! :)

It would take thousand of years to brute force a password with 13 alpha-numeric characters. [Only registered and activated users can see links. Click Here To Register...] on an non quantum computer.
For sure 6, 7 and 8 is possible with high key per second rate.

Borsti and Mahatma reversed the pass out of the engine.

Quote:

Originally Posted by Daywalker747 It would take thousand of years to brute force a password with 13 alpha-numeric characters. [Only registered and activated users can see links. Click Here To Register...] on an non quantum computer. For sure 6, 7 and 8 is possible with high key per second rate. Borsti and Mahatma reversed the pass out of the engine.

Im aware of that and i was running it with max length of 14 and just custom charset, to be specific i used A-Z 0-9 and # cause i thought they would use the same sheme again, and it would end up with 255 days on the tool i used.

So i tryed spread it out on 3 PCs that would cut it down already to a more nearby date and was going to ask some mates to help on it to get there faster.

But yea things never come easy and they changed the sheme so i would been ending up with all this wasting lots of time and power for nothing cause they took small letters in and change the length :p

So i want to send a thanks again to Mahatma, Borsti and ILikeItEasy, prevent me from this waste.

And thx to you aswell that calc helps me to think twice before struggle with bruteforce next time :)

it's actually funny and sad how you can come arround those "korean tricks" :d

Quote:

Originally Posted by PsyoO Im aware of that and i was running it with max length of 14 and just custom charset, to be specific i used A-Z 0-9 and # cause i thought they would use the same sheme again, and it would end up with 255 days on the tool i used. So i tryed spread it out on 3 PCs that would cut it down already to a more nearby date and was going to ask some mates to help on it to get there faster. But yea things never come easy and they changed the sheme so i would been ending up with all this wasting lots of time and power for nothing cause they took small letters in and change the length :p So i want to send a thanks again to Mahatma, Borsti and ILikeItEasy, prevent me from this waste. And thx to you aswell that calc helps me to think twice before struggle with bruteforce next time :)

That's how we did it!
BorSti, Mahatma and me split up the possible pw's and all started bruteforcing with our super computers :)

Well, to be honost. I XOR'd the pw from engine myself by hand. Didn't even use a PC for it :pimp:

thx for pw. Now PKED not support new encrypt :/