보이스는 원래 구구버전 옛날 게임들 하나 둘씩 크랙하면서 후원금도 얻고 조용히 살고 있었는데, 갑자기 뜬금 하이퍼바이저가 나와서 얘도 급발진 한거죠. 데누보 뚫는거 자기 혼자였는데, 그냥 하이퍼바이저가 이슈 다 끌고 가니깐 난리가 난거임. 그래서 구구버전만 뚫는거 과감히 접고, 최신버전 뚫는데, 여기서 하이퍼바이저 덕분에 더 쉽게 뚫었죠. 보이스도 말하길 최신버전도 생각보다 크게 다르지 않네? 하면서 생각보다 쉽게 뚫었다고..
voice38이 하이퍼바이저 나오고 그 우회방법을 참고해서 크랙킹이 훨씬 빨라진건 팩트임..
You need to understand D to know why voices crack D game 1 by one (cause its a long process, similar to reading this long-a** explanation of mine).
A game (the exe) has instructions like when you equip a gun and the gun has ammo, when you left click, a bullet is fired (instruction). D takes the instruction of firing a gun (which is already a shit ton of code), and makes it confusing. How can it make confusing? It'll ask to perform math operations that lead to different roads (path). Problem is, only 1 of these paths is correct. So unless you solve the math, the bullet won't fire. Worse, the firing will crash you game. Poof, thats a lot right? CDX explained this in Injustice.2.Legendary.Edition-CODEX nfo. But do note, which instruction to wrap in D trigger or which code to sent to VM, is partly on dev's hand from what I read. So if dev wrap some important code (that is triggered a lot) inside a function that needs solving math, well welcome to micro shutter land.
Multiply it by 1000 and make every trigger (math function) unique. Well they say the wind in Vietnam sucked. Should spend a day in D-land. And that was just 1 part of the protection.
And if that wasn't enough, D runs some of the code inside its own virtual machine (google what is a virtual machine to know why it makes reversing so much harder). Basically takes the already confusing x86 assembly language and make it almost impossible to understand. Oh wait, Denuvo + VM protect? Welcome to Inception except here its neither fun nor directed by Nolan.
On top of that they got shit ton of checks like how much time a special instruction took to return a value. Cause that means some external tool (debugger) is eavesdropping on comms. CRASH.
What about you find and set all those instructions to return true regardless? CRASH (cause you touched code, which failed integrity check i.e. the code checks itself if it was modified, FK !!!).
Or you built a tool that 100% bypass (or call it crack if calling it a bypass hurts your ego) say AC Shadows. You can't simply put the exe of BL4 through it and expect it to get a working game. Yes some triggers might be found and fixed but chances are, depending on how D was implemented a hell lot more trigger got missed. Some dev may add triggers to saving your game, some to loading a new area, some to say when an NPC talks. And each one will have the multiple path (control flow obfuscation) I talked about. BTW, congrats you fixed 999/1k triggers? CRASH. Cause you failed to find and fix the trigger on special boss attack.
Do note you can fit an entire hello world program in KB or two of exe. So just think how much code must be in that 500MB exe (even if only half of the size is taken by D specific codes as nowadays UE5 exe are topping 150MB themselve). Its not humanly possible to decode that much garbage code by a human, realistically.
So what do voices/empress/cpy or basically any other group do is make their own software that find and pacifies those checks and triggers so when the game ask "hey is someone eavesdropping on how the code is running?", it replies "No, everything is fine ????" (without the emoji). Then voices test the game if he missed any hidden/new check by running the game in an AMD/Nvidia hardware. Cause D may add code that only gets triggered on those hardware while no checks were added when referencing say Intel hardware.
In short, if you ask me I feel voices or crack group spend more time creating tools than fixing things by hand. If you want to know what happens if you try to patch the triggers by hand, check 0xZeOn comments on Dead Space Remake on cs rin website. You'll know exactly what I mean.
Edit: Copied his line from his post in rin.
Denuvo is focused on New Game + Load SaveGame.
Tested on AMD Zen 3, i5-1334U, Windows 11 25H2.
Windows 10 not supported.
Randomize is killing me, There are a lot of Hw/Environment checks spawning randomly, not patched = crash.
Load savegame can take long times (black screen) probably caused by one of my +3000 patches.
Now you may ask, if you can't touch the exe or do anything without crashing the game, how the F do voices and others crack D? Well, voices get a legitimate copy of the game, use a hypervisor or some custom tool to hide his custom/semi-custom debugger from Denuvo, find what instructions are being intercepted by Windows or when D is calling home, make a list of those points and work backwards from there. Its way more difficult than how easy I made it sound. So yes, there is a reason voices isn't throwing out games left and right cause D is like an ever evolving virus. You can only cut so many heads before it mutates.
voices get a legitimate copy of the game, use a hypervisor or some custom tool to hide his custom/semi-custom debugger from Denuvo
이 부분을 보면 voice38이 정품게임의 데이터를 구한뒤 하이퍼바이저나 툴을 이용해 데누보를 우회하는 크랙킹을 한다는 이야기임.. 이미 레딧쪽에서 하이퍼바이저 나온뒤 그우회법에 힌트를 얻어서 빠르게 크래킹한다고 계속 이야기가 나왔었음..
호랑이내비
tgfwehe
하리하리
Seankim
다만이공
울트라후니
바하레퀴엠
zmfkd1
이마자토
하이퍼바이저크랙이 '먼저' 나오게되면서...
목조리좌 시작부터 과거 데누보 게임 크랙을 시작으로 유명해진 케이스죠
You need to understand D to know why voices crack D game 1 by one (cause its a long process, similar to reading this long-a** explanation of mine).
A game (the exe) has instructions like when you equip a gun and the gun has ammo, when you left click, a bullet is fired (instruction). D takes the instruction of firing a gun (which is already a shit ton of code), and makes it confusing. How can it make confusing? It'll ask to perform math operations that lead to different roads (path). Problem is, only 1 of these paths is correct. So unless you solve the math, the bullet won't fire. Worse, the firing will crash you game. Poof, thats a lot right? CDX explained this in Injustice.2.Legendary.Edition-CODEX nfo. But do note, which instruction to wrap in D trigger or which code to sent to VM, is partly on dev's hand from what I read. So if dev wrap some important code (that is triggered a lot) inside a function that needs solving math, well welcome to micro shutter land.
Multiply it by 1000 and make every trigger (math function) unique. Well they say the wind in Vietnam sucked. Should spend a day in D-land. And that was just 1 part of the protection.
And if that wasn't enough, D runs some of the code inside its own virtual machine (google what is a virtual machine to know why it makes reversing so much harder). Basically takes the already confusing x86 assembly language and make it almost impossible to understand. Oh wait, Denuvo + VM protect? Welcome to Inception except here its neither fun nor directed by Nolan.
On top of that they got shit ton of checks like how much time a special instruction took to return a value. Cause that means some external tool (debugger) is eavesdropping on comms. CRASH.
What about you find and set all those instructions to return true regardless? CRASH (cause you touched code, which failed integrity check i.e. the code checks itself if it was modified, FK !!!).
Or you built a tool that 100% bypass (or call it crack if calling it a bypass hurts your ego) say AC Shadows. You can't simply put the exe of BL4 through it and expect it to get a working game. Yes some triggers might be found and fixed but chances are, depending on how D was implemented a hell lot more trigger got missed. Some dev may add triggers to saving your game, some to loading a new area, some to say when an NPC talks. And each one will have the multiple path (control flow obfuscation) I talked about. BTW, congrats you fixed 999/1k triggers? CRASH. Cause you failed to find and fix the trigger on special boss attack.
Do note you can fit an entire hello world program in KB or two of exe. So just think how much code must be in that 500MB exe (even if only half of the size is taken by D specific codes as nowadays UE5 exe are topping 150MB themselve). Its not humanly possible to decode that much garbage code by a human, realistically.
So what do voices/empress/cpy or basically any other group do is make their own software that find and pacifies those checks and triggers so when the game ask "hey is someone eavesdropping on how the code is running?", it replies "No, everything is fine ????" (without the emoji). Then voices test the game if he missed any hidden/new check by running the game in an AMD/Nvidia hardware. Cause D may add code that only gets triggered on those hardware while no checks were added when referencing say Intel hardware.
In short, if you ask me I feel voices or crack group spend more time creating tools than fixing things by hand. If you want to know what happens if you try to patch the triggers by hand, check 0xZeOn comments on Dead Space Remake on cs rin website. You'll know exactly what I mean.
Edit: Copied his line from his post in rin.
Denuvo is focused on New Game + Load SaveGame.
Tested on AMD Zen 3, i5-1334U, Windows 11 25H2.
Windows 10 not supported.
Randomize is killing me, There are a lot of Hw/Environment checks spawning randomly, not patched = crash.
Load savegame can take long times (black screen) probably caused by one of my +3000 patches.
Now you may ask, if you can't touch the exe or do anything without crashing the game, how the F do voices and others crack D? Well, voices get a legitimate copy of the game, use a hypervisor or some custom tool to hide his custom/semi-custom debugger from Denuvo, find what instructions are being intercepted by Windows or when D is calling home, make a list of those points and work backwards from there. Its way more difficult than how easy I made it sound. So yes, there is a reason voices isn't throwing out games left and right cause D is like an ever evolving virus. You can only cut so many heads before it mutates.
데누보 뚫기 어렵다 수작업으로 할수 있는 영역이 아니다
보이스도 아마 수작업이 아닌 툴을 만들어서 그걸로 뚤고 있을것이다 하는 목소리좌가 쓴것도 아닌 그냥 합리적인 수긍은 되지만 검증없는 카더라 내용인데
HV랑 무슨 상관이 있는 내용이죠?
이 부분을 보면 voice38이 정품게임의 데이터를 구한뒤 하이퍼바이저나 툴을 이용해 데누보를 우회하는 크랙킹을 한다는 이야기임.. 이미 레딧쪽에서 하이퍼바이저 나온뒤 그우회법에 힌트를 얻어서 빠르게 크래킹한다고 계속 이야기가 나왔었음..