another HackShield bypass method

[retarded jas161]

Originally Posted by Englishnessness

Still works perfectly fine if you don't try to multiclient. Shouldn't be too hard to get multiclienting working perfectly either, if any difficulty would even be present at all, although that's just a guess. There are plenty of other ways to multiclient also.

yes, but those ways are memory wasteful. qq.

[Ayamin]

Multiclient is still possible

Just other things that take more work to figure out \o/

[Englishnessness]

Originally Posted by retarded jas161

yes, but those ways are memory wasteful. qq.

Only some of them~

[fate351228]

someone should just update a dinput8.dll
most likely that seems to be the problem

[retarded jas161]

Originally Posted by fate351228

someone should just update a dinput8.dll
most likely that seems to be the problem

y dun u

[Yiting]

Since hackshield added the identifier for each connection, it should be not possible multi-clienting again by this method...

 Spoiler

if you can keep the first packet for each connection, then repeat it to HSLaunch before every hackshield request sent, so the identifier will be reassigned in every request, and multi-clienting will work again.

[xunyi]

Originally Posted by Yiting

Since hackshield added the identifier for each connection, it should be not possible multi-clienting again by this method...

 Spoiler

if you can keep the first packet for each connection, then repeat it to HSLaunch before every hackshield request sent, so the identifier will be reassigned in every request, and multi-clienting will work again.

lol sad....

[RiF_]

Originally Posted by Yiting

according to my previous post, this dinput8 will detect the hackshield bootstrap message and spawn it in every subrequest. enjoy it~

VirusTotal result:

 Spoiler

SHA256: 844f1cff23ebc9ac132a35189a65b97f1a17459ef130c9db48 c2ee8c32521376
File name: dinput8.dll
Detection ratio: 1 / 42
Analysis date: 2012-07-20 05:00:31 UTC

Thanks Guys

[Blade3575]

Originally Posted by Yiting

according to my previous post, this dinput8 will detect the hackshield bootstrap message and spawn it in every subrequest. enjoy it~

VirusTotal result:

 Spoiler

SHA256: 844f1cff23ebc9ac132a35189a65b97f1a17459ef130c9db48 c2ee8c32521376
File name: dinput8.dll
Detection ratio: 1 / 42
Analysis date: 2012-07-20 05:00:31 UTC

Seems to work. Thank you very much, Yiting.

[step29]

Does not work with r251 JP Client [the Classic!]

[xunyi]

Originally Posted by Yiting

according to my previous post, this dinput8 will detect the hackshield bootstrap message and spawn it in every subrequest. enjoy it~

VirusTotal result:

 Spoiler

SHA256: 844f1cff23ebc9ac132a35189a65b97f1a17459ef130c9db48 c2ee8c32521376
File name: dinput8.dll
Detection ratio: 1 / 42
Analysis date: 2012-07-20 05:00:31 UTC

thank you Yiting

[chaoticoracle225]

only problem is if you cc on one of the clients it crashes lol, but still gj

[desterpot]

Yitzing, it says Error occured during initialization. Code 1 blah blah blah. I try letting the hshield update and then put crackshield back on but it doesnt work

[jimpatrick]

Originally Posted by Yiting

according to my previous post, this dinput8 will detect the hackshield bootstrap message and spawn it in every subrequest. enjoy it~

VirusTotal result:

 Spoiler

SHA256: 844f1cff23ebc9ac132a35189a65b97f1a17459ef130c9db48 c2ee8c32521376
File name: dinput8.dll
Detection ratio: 1 / 42
Analysis date: 2012-07-20 05:00:31 UTC

thanks dude,now i can fish again

[desterpot]

Originally Posted by Yiting

Since hackshield added the identifier for each connection, it should be not possible multi-clienting again by this method...

 Spoiler

if you can keep the first packet for each connection, then repeat it to HSLaunch before every hackshield request sent, so the identifier will be reassigned in every request, and multi-clienting will work again.

Yiting, I try the crackshield with Vindictus and it doesnt work. Its says Error occured during initialization. Code 1.........