Post: Secure Tools against modded PS3Lib!
Options
02-12-2015, 07:46 AM
#1
Bch
Guest
Add this code inside your Form Load event.
Method 1: (Best Method)
Check the MD5 Hash of the PS3Lib to make sure it matches either 2.50, or 2.60.
Code
try
{
byte[] M250 = new byte[] { 0x7B, 0xE3, 0xDB, 0x9B, 0x76, 0x08, 0xCB, 0x05, 0xCC, 0xF5, 0x6C, 0x5C, 0x60, 0x6E, 0xBD, 0x60 };
byte[] M260 = new byte[] { 0xF0, 0xE0, 0x4E, 0xFE, 0x7B, 0x2A, 0xA4, 0x77, 0x11, 0x53, 0x59, 0x15, 0xE2, 0xB1, 0xA1, 0xAB };
byte[] MD5Result;
using (var md5 = MD5.Create())
{
MD5Result = md5.ComputeHash(File.ReadAllBytes(Directory.GetCurrentDirectory() + @"\PS3Lib.dll"));
string PsLib = ASCIIEncoding.ASCII.GetString(MD5Result);
string PsLib250 = ASCIIEncoding.ASCII.GetString(M250);
string PsLib260 = ASCIIEncoding.ASCII.GetString(M260);
if (PsLib != PsLib250 && PsLib != PsLib260)
{
Application.Exit();
}
}
}
catch
{
Application.Exit();
}
Method 2:
Check the file version (Modded Lib is 9.9.9.9) then automatically exit if it is not 4.3 or 4.4.
I'll write something up for this soon, you can always add both in too :p
The following 21 users say thank you to Bch for this useful post:
02-12-2015, 02:21 PM
#2
Red-EyeX32
AstroCFG
Originally posted by Beach
Theres a new modded ps3lib which can log all the bytes your write and read. To get around this issue there are several things you can do.
Add this code inside your Form Load event.
Method 1: (Best Method)
Check the MD5 Hash of the PS3Lib to make sure it matches either 2.50, or 2.60.
Code
Method 2:
Check the file version (Modded Lib is 9.9.9.9) then automatically exit if it is not 4.3 or 4.4.
I'll write something up for this soon, you can always add both in too :p
Add this code inside your Form Load event.
Method 1: (Best Method)
Check the MD5 Hash of the PS3Lib to make sure it matches either 2.50, or 2.60.
Code
try
{
byte[] M250 = new byte[] { 0x7B, 0xE3, 0xDB, 0x9B, 0x76, 0x08, 0xCB, 0x05, 0xCC, 0xF5, 0x6C, 0x5C, 0x60, 0x6E, 0xBD, 0x60 };
byte[] M260 = new byte[] { 0xF0, 0xE0, 0x4E, 0xFE, 0x7B, 0x2A, 0xA4, 0x77, 0x11, 0x53, 0x59, 0x15, 0xE2, 0xB1, 0xA1, 0xAB };
byte[] MD5Result;
using (var md5 = MD5.Create())
{
MD5Result = md5.ComputeHash(File.ReadAllBytes(Directory.GetCurrentDirectory() + @"\PS3Lib.dll"));
string PsLib = ASCIIEncoding.ASCII.GetString(MD5Result);
string PsLib250 = ASCIIEncoding.ASCII.GetString(M250);
string PsLib260 = ASCIIEncoding.ASCII.GetString(M260);
if (PsLib != PsLib250 && PsLib != PsLib260)
{
Application.Exit();
}
}
}
catch
{
Application.Exit();
}
Method 2:
Check the file version (Modded Lib is 9.9.9.9) then automatically exit if it is not 4.3 or 4.4.
I'll write something up for this soon, you can always add both in too :p
You can easily patch this :p
The following 2 users say thank you to Red-EyeX32 for this useful post:
02-12-2015, 02:24 PM
#4
Red-EyeX32
AstroCFG
02-12-2015, 05:00 PM
#6
TheSaltCracka
League Champion
The following 6 users say thank you to TheSaltCracka for this useful post:
02-12-2015, 10:58 PM
#7
FarSideX
I’m too L33T
MD5 checks don't work on dlls since you can just patch a dll to any MD5 you want. Version check is as stupid as the hacker that doesn't respond with the same version.
If you don't want to have your tool exposed through a hacked PS3Lib.dll don't use PS3Lib's dll, learn to code for yourself or embed PS3Lib as source rather than an external lib. Using PS3Lib.dll is fine for throwing together quick a tool or for noobs to coding, past that is it not required.
Besides hacked dlls are not needed since you can just use a network tool to see the traffic. There are ways to prevent that but they are way past the scope of this thread.
If you don't want to have your tool exposed through a hacked PS3Lib.dll don't use PS3Lib's dll, learn to code for yourself or embed PS3Lib as source rather than an external lib. Using PS3Lib.dll is fine for throwing together quick a tool or for noobs to coding, past that is it not required.
Besides hacked dlls are not needed since you can just use a network tool to see the traffic. There are ways to prevent that but they are way past the scope of this thread.
The following 2 users say thank you to FarSideX for this useful post:
02-13-2015, 04:04 AM
#9
FarSideX
I’m too L33T
Originally posted by Beach
I see many people slating this thread because they know better, yet not one of them as actually posted anything to make it better? If your going to slate it, atleast show a better method before hand, as that would actually be useful to people
Read my post, I did already.
As far as preventing logging network traffic that is as I already said beyond the scope of this thread and probably beyond the ability of those that rely on PS3Lib.dll.
02-13-2015, 08:02 AM
#10
Bch
Guest
Originally posted by FarSideX
Read my post, I did already.
As far as preventing logging network traffic that is as I already said beyond the scope of this thread and probably beyond the ability of those that rely on PS3Lib.dll.
As far as preventing logging network traffic that is as I already said beyond the scope of this thread and probably beyond the ability of those that rely on PS3Lib.dll.
Not really, you are on about embedding the ps3lib, meaning looking at the source, plus that means you need two versions for 2.50 and 2.60 and theres no real understanding of how this can be done
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
