ThreateningYeti VS x64dbg

With this new information, I was interested in seeing if this software is as air-tight as Respondus markets it to be. After all, with all these compromises in privacy, it must offer a secure testing environment, right? Well… Researching for “Lockdown Browser bypass tools” lead to me this archived project by TheateningYeti on GitHub. This software is one of many bypass tools authored with the sole purpose of rending Lockdown Browser useless. It should be noted that to avoid accusations of academic dishonesty I will solely be covering this out project, as an example of a bypass tool, as it is outdated and no longer effective. I will not be providing any existing tools nor will do I endorse the use of such software. This project has since been discontinued as, according to ThreateningYeti, “...cat and mouse game has gone too far to publicly release an open-source bypass.”. In other words, this project was not discounted due to it being impossible to create a bypass tool for Lockdown Browser, but rather because the work did not continue as, to ThreateningYeti, the rewards were not worth the effort. Why is this important then? This project is of vital importance as it demonstrates just how ineffective the Lockdown Browser can be and bypass tools are not the only way of mitigating this software either. The Linux and Unix Users Group at Virginia Tech states on their wiki that

I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person.

[1] https://remedybg.handmade.network/

[2] https://x64dbg.com/

I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version.

One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases

.exe is a complex format and not something you're going to extract raw instructions from using a hexdump. What you need is a "disassembler". For Windows I'd recommend x64dbg.

Patch the DayZServer_x64.exe, change "test al, al" to "cmp al, 2". i used x64dbg (https://x64dbg.com) a good video for the whole process: https://drive.google.com/file/d/1F1A0lpumREPXtVeoTMq1HiEnvaZp-NUU/view