ROBLOX-Reverse-Engineering/RRE-Site
ROBLOX-Reverse-Engineering
/
RRE-Site
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases Wiki Activity

Add additional info about the topic.

This commit is contained in:
Raymond 2023-01-30 21:16:04 -05:00 committed by GitHub
parent 9d4478815d
commit 0daaa8d5b1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/Common Issues/RakNet Removal of Authorization.md
View File

@ -3,8 +3,11 @@ Guide created by Raymond, with lots of help by Yakov
<hr> <hr>
We're jumping around a function inside of RakPeer.cpp. This was made for users who are having trouble connecting to their `RCCService` due to invalid RakNet keys.<br>
Note that this method is more secure than setting the FFlag, but it *could* cause issues down the line (*client incompatibility, so on*) This is *technically* more secure than setting the FFlag, but it *could* cause issues down the line (you'll probably be fine.)
We're jumping around a function inside of RakPeer.cpp,<br>
essentially we're just guiding the program around the code that'll check if it's a valid key and shooting right towards the `return true`.
Pattern used: `6A016A088D45` (This was created from a 2017L build, it may have been changed in newer builds, but that's unlikely.) Pattern used: `6A016A088D45` (This was created from a 2017L build, it may have been changed in newer builds, but that's unlikely.)
@ -17,4 +20,5 @@ Instructions to modify, starting from the first `nop` above the `push 1 & push 8
2. First `jne`, should be the **same instruction** as the `je` we just changed *(make sure the address to jump is modified too.)*<br> 2. First `jne`, should be the **same instruction** as the `je` we just changed *(make sure the address to jump is modified too.)*<br>
3. And the first `jne` above the `nop`, of which was mentioned earlier. 3. And the first `jne` above the `nop`, of which was mentioned earlier.
Save the patches, and try launching RCC. It should be able to connect without having to authorize your client passwords. Save the patches, and try launching RCC.<br>
It should be able to connect without having to authorize your client passwords.