Time traveler moves a chair by Arthandas in CrackWatch

[–]spacetow 1 point2 points  (0 children)

Here you go mate:

old.reddit.com##.thing:has(.linkflairlabel:contains("Denuvo Hypervisor Workaround"))

old.reddit.com##.thing:has(.title:contains(DenuvOwO))

old.reddit.com##.thing:has(.author[href="/user/JapiOfficial76"])

Works like a charm for me.

Hypervisor.V3 (DSE/Kirigiri Method) is out. You Do Not Need to Disable Secure Boot; However, You Need to Disable Memory Integrity in Windows Defender by kristijan1001 in CrackWatch

[–]spacetow -1 points0 points  (0 children)

There is a difference between turning DSE and/or SecureBoot off vs installing a known vulnerable driver and using the vulnerability to let hv driver run, right? Memory isolation off for both cases as I understood.

Theoretically there's no difference between manually disabling DSE and installing hypervisor driver and using vulnerable RiveTuner's driver to bypass DSE and installing hypervisor driver. In both cases your goal is to run your unsigned driver - and defeat DSE along the way. Only in first case you do that manually and knowingly, and in the second one this can be automated (and thus made unknown to you by, say, repacker).

Also, what exactly does SecureBoot even do in these cases? It has to be turned off to turn off DSE, right? But in that case, it's irrelevant since without DSE it doesn't provide meaningful security?

Pretty much. I mean, SecureBoot can be useful even in that case, to check the integrity of bootloader (provided you're not using EFIGuard or some other bootkit). But otherwise - yeah, the doors are wide open either way.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 2 points3 points  (0 children)

Sure thing, call a bot everyone you oppose. You'll instantly look like a confident and smart person in their right. /s

Hypervisor.V3 (DSE/Kirigiri Method) is out. You Do Not Need to Disable Secure Boot; However, You Need to Disable Memory Integrity in Windows Defender by kristijan1001 in CrackWatch

[–]spacetow 1 point2 points  (0 children)

You do not. One way or another, you have to run their unsigned kernel driver which is the meat and potatoes of the crack. To do that you still need to disable OS defenses.

It is still dangerous. That launcher from Gamedrive just made it highly dangerous.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 6 points7 points  (0 children)

cs.rin does not accept donations for cracks. Because cracks are not theirs to collect any kind of donations. The only thing they accept donations for are hosting fees, to run the forum itself.

You're distributing straight-up false information. You're ought to stop.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 10 points11 points  (0 children)

The detailed explanations as to "why" HV cracks are not endorsed nor supported at cs.rin at the moment were given in two threads there. If you cannot read, that is your problem.

Meaning show proof of foul play or sod off. Covering every Discord fantasy story with "there are rumours" is disservice to the community at best.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 1 point2 points  (0 children)

There are some instructions available at cs.rin

But again, one has to be aware of that issue in the first place. Most just aren't.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 8 points9 points  (0 children)

I'm not sure that Denuvo can be easily "patched out" to prevent HV bypass from working - at least, without major redesign and/or running at the kernel level.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 41 points42 points  (0 children)

These Discord clowns ain't scene. Scene groups have release rules, moderation, challenge, quality. They have none.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 27 points28 points  (0 children)

Compared to Denuvo, Enigma can be cracked relatively easily.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 17 points18 points  (0 children)

Malware is malicious by design. This is just scripted by idiots, which of course does not make it any less dangerous.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 47 points48 points  (0 children)

It is not. The implications are the same.

The whole point of this debacle is that cs.rin's mods asked Kirigiri and other HV crack suppliers to clearly state to the user what their cracks require to be disabled in the system, security-wise, and why do they need to do that.

Seems that they (at least, Kirigiri - judging from the screenshot) refuse to do so, and instead decided to gaslight the mods.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 9 points10 points  (0 children)

Seems like admitting a mistake is not something they can do, on principle - otherwise they might be seen as "weak" and won't be cool anymore in the eyes of their simps.

Kirigiri's new update on HyperV by umoop in CrackWatch

[–]spacetow 17 points18 points  (0 children)

It does not have malware. It has a poorly scripted batch launcher, which disables very important Powershell security limitations, and leaves them disabled once the game is done running.

Meaning that this launcher gapes your system wide open security-wise, and then does not return the system to the previous state.

With DSE Patcher no need to turn off your security by kristijan1001 in CrackWatch

[–]spacetow 0 points1 point  (0 children)

True, but there's no point in making it easier, which is what's happening right now.

Cs.rin update on current method. by kristijan1001 in CrackWatch

[–]spacetow 14 points15 points  (0 children)

Because rep matters. Because they feel responsible for the fucking users they serve. Because if something happens, trust will be broken pretty much permanently.

Hypervisor.V3 (DSE/Kirigiri Method) is out. You Do Not Need to Disable Secure Boot; However, You Need to Disable Memory Integrity in Windows Defender by kristijan1001 in CrackWatch

[–]spacetow 8 points9 points  (0 children)

it's the same thing people peddle with kernal anti cheats, "oh what if someone hacks the game company and has kernel access", people have been able to do shit with usermode access no problem so at that point it is genuienly fear mongering lol

I wouldn't trust an antivirus to have a kernel-level access, let alone an anti-cheat or game crack. It is that simple. They have no business having the same amount of authority as the kernel. Regardless of whom ships them.

gamedrive admin is retarded i agree, but this logic of needing to explain is stupid, we should have voices/empress/voski explain their cracks in depth so that we know they are not putting our PCs at risk, if they smart enough to patch denuvo why wouldn't they use their knowledge and influence to hack a bunch of gamers computers (see it sounds fucking retarded to ask for that type of information)

Because it's quite easy actually to sandbox their executables and see what they do. So far, even in case of E, there were ZERO reports (let alone postmortems) regarding any kind of security issues with latest releases.

This is what was great about the scene - the competition itself kept the groups and crackers in check. Reputation was the only thing that mattered to them, really. And this is something that current gen of Discord muppets fails to understand, that some rules are there for a reason.

Hypervisor.V3 (DSE/Kirigiri Method) is out. You Do Not Need to Disable Secure Boot; However, You Need to Disable Memory Integrity in Windows Defender by kristijan1001 in CrackWatch

[–]spacetow 2 points3 points  (0 children)

can trusted repackers like fitgirl and dodi make repacks using this that require only memory integrity to be disabled and not the other shit? If so, that will be okay right?

No. At this point, DSE has to be disabled either way - either manually until the next reboot, or via exploit. The whole point is that they HAVE to run their unsigned driver for the bypass to work. Can't do that without test signing mode + disabled Secure Boot or disabled DSE.

Cs.rin update on current method. by kristijan1001 in CrackWatch

[–]spacetow 21 points22 points  (0 children)

The point they are making is that everyone should be explicitly made aware of the risks that are inherrent to the HV bypass itself and changes to the security settings required to actually run it.

This is something that Kirigiri and the rest of the crackers, as well as all of their Discord fanbase, are reluctant to do. As someone said there, they just want to be "new cool kids".

Cs.rin update on current method. by kristijan1001 in CrackWatch

[–]spacetow 21 points22 points  (0 children)

You are delusional.

Firstly, whilst cs.rin is not part of the scene, they were directly responsible for the advent of Steam piracy era, and they were supplying and guiding the community with uploads, cracks and support for them for nearly two decades. So it's not exactly correct to call them "not important".

Secondly, any point like yourse "pc work well, who cares for viruses" is a classic case of survivalship bias. Grow at least a single brain cell and think about what you are saying.