Jump to content
Aleos

Packet Obfuscation Support

Recommended Posts

enabled by default @[email protected]

I should rediff all my test clients

 

 


eh, add a note aleos, since it's enabled by default, if user change the packetver under 20110817, or just make if below that ver, undef the PACKET_OBFUSCATION.

Link to comment
Share on other sites

This is awesome! Thank you Aleos, and everyone else who helped to make this feature possible for rA, finally.

 

PS: Wow. I will need to re-diff my 2012 / 2013 clients  /omg

Link to comment
Share on other sites

nice i've waiting for this my salute to the developers of this WPE Free rAthena !  /no1


EDIT: if my client has a broken keys will this Packet obfuscation still work?
         My client is 2013-12-23 and seems on this link CLICK ME  2013-12-23 is broken?

Edited by Yonko
Link to comment
Share on other sites

Finally the update that ive been waiting for :D

 

So whats next on rAthena?

maybe you should try to implement this also from herc...

 
But anyways Great Work rA team :P
Link to comment
Share on other sites

Hello,

Thanks for the update but i'm unable to disable the feature by commenting out #define PACKET_OBFUSCATION. in src/conf/core.h I've recompiled the sources of course. Any idea on how to truly disable it ?

Link to comment
Share on other sites

 

if my client has a broken keys will this Packet obfuscation still work?

Diff your client with your own custom keys and change the server side keys too

 

How to have that custom packet keys? Is it random? How to generate my own custom packet keys?

@topic: Finally! good work rAthena developers :)

Link to comment
Share on other sites

 

 

if my client has a broken keys will this Packet obfuscation still work?

Diff your client with your own custom keys and change the server side keys too

 

How to have that custom packet keys? Is it random? How to generate my own custom packet keys?

@topic: Finally! good work rAthena developers :)

 

 

Use NEMO to diff ur client, and...

Do NOT select:

  • Disable Packet Encryption (Recommended)

Select:

  • Packet First Key Encryption, and following ur 1st key
  • Packet Second Key Encryption, and following ur 2nd key
  • Packet Third Key Encryption, and following ur 3rd key
  • Then make sure put your custom keys on db/[import/]packet_db.txt, in packet_keys_use: <key1>,<key2>,<key3>
  • Upvote 1
Link to comment
Share on other sites

One Question : because i am using 2013 - 12 - 23 client and the keys are broken.

  • I did not patch packet first key encryption and the rest of it that's fine right?
Link to comment
Share on other sites

Hello,

Thanks for the update but i'm unable to disable the feature by commenting out #define PACKET_OBFUSCATION. in src/conf/core.h I've recompiled the sources of course. Any idea on how to truly disable it ?

Commenting that line out and then recompiling your server will disable the feature.

 

With this, the Maya Purple Filter doesn't work ?

This is meant to stop the spamming of packets sent to the client. There are some checks server-side for Maya Purple hacks but I haven't really tested it on the client to know if it's still working or not.

 

One Question : because i am using 2013 - 12 - 23 client and the keys are broken.

  • I did not patch packet first key encryption and the rest of it that's fine right?

If you don't use your own keys then eventually the default keys on the client aren't sent as encrypted anymore.

Link to comment
Share on other sites

One Question : because i am using 2013 - 12 - 23 client and the keys are broken.

  • I did not patch packet first key encryption and the rest of it that's fine right?

 

broken?

Here I'm using 2013-12-23c with default keys, diffed by NEMO.

post-5421-0-50898500-1426523095_thumb.png

 

well, if u're using NEMO, it might tell "Second Packet Key is copy of Third for this date - change Third one instead", just comment the lines on NEMO's /Patches/PacketEncryptionKeys.qs (note: idk the side effect :P)

	//Duplicate Check
	switch(keyindex) {
		case 0:
			if (keyaddrs[2] == keyaddrs[0]) {
				return "First Packet Key is copy of Third for this date - change Third one instead";
			}
			if (keyaddrs[1] == keyaddrs[0]) {
				return "First Packet Key is copy of Second for this date - change Second one instead";
			}
			break;
		case 1:
			if (keyaddrs[2] == keyaddrs[1]) {
				return "Second Packet Key is copy of Third for this date - change Third one instead";
			}
			break;
	}
Link to comment
Share on other sites

 

One Question : because i am using 2013 - 12 - 23 client and the keys are broken.

  • I did not patch packet first key encryption and the rest of it that's fine right?

 

broken?

Here I'm using 2013-12-23c with default keys, diffed by NEMO.

attachicon.gifScreenshot_18.png

 

well, if u're using NEMO, it might tell "Second Packet Key is copy of Third for this date - change Third one instead", just comment the lines on NEMO's /Patches/PacketEncryptionKeys.qs (note: idk the side effect :P)

	//Duplicate Check
	switch(keyindex) {
		case 0:
			if (keyaddrs[2] == keyaddrs[0]) {
				return "First Packet Key is copy of Third for this date - change Third one instead";
			}
			if (keyaddrs[1] == keyaddrs[0]) {
				return "First Packet Key is copy of Second for this date - change Second one instead";
			}
			break;
		case 1:
			if (keyaddrs[2] == keyaddrs[1]) {
				return "Second Packet Key is copy of Third for this date - change Third one instead";
			}
			break;
	}

 

Oh so if i still use the default packet keys its okay? because what i did is i changed the default keys of the client im using.

Link to comment
Share on other sites

	//Duplicate Check
	switch(keyindex) {
		case 0:
			if (keyaddrs[2] == keyaddrs[0]) {
				return "First Packet Key is copy of Third for this date - change Third one instead";
			}
			if (keyaddrs[1] == keyaddrs[0]) {
				return "First Packet Key is copy of Second for this date - change Second one instead";
			}
			break;
		case 1:
			if (keyaddrs[2] == keyaddrs[1]) {
				return "Second Packet Key is copy of Third for this date - change Third one instead";
			}
			break;
	}

I think those line aren't needed, because actually a same key can be used to make it to work /hmm

Try to put "0x87654321" on all 3 keys ;)

Link to comment
Share on other sites

 

How to have that custom packet keys? Is it random? How to generate my own custom packet keys?

Use this free tool to generate your own custom keys /no1

 

 

ls6opF.jpg

 

new custome key work 1 key 

Edited by indybigza
Link to comment
Share on other sites

 

 

 

if my client has a broken keys will this Packet obfuscation still work?

Diff your client with your own custom keys and change the server side keys too

 

How to have that custom packet keys? Is it random? How to generate my own custom packet keys?

@topic: Finally! good work rAthena developers :)

 

 

Use NEMO to diff ur client, and...

Do NOT select:

  • Disable Packet Encryption (Recommended)

Select:

  • Packet First Key Encryption, and following ur 1st key
  • Packet Second Key Encryption, and following ur 2nd key
  • Packet Third Key Encryption, and following ur 3rd key
  • Then make sure put your custom keys on db/[import/]packet_db.txt, in packet_keys_use: <key1>,<key2>,<key3>

 

 

 

 

How to have that custom packet keys? Is it random? How to generate my own custom packet keys?

Use this free tool to generate your own custom keys /no1

 

Thank you so much for this.

Very much appreciated  /no1

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.