As someone who’s worked for several years in higher ed IT and used Linux during my studies, this’ll only get you most of the way there. Unfortunately some proctoring software (Respondus Lockdown Browser comes to mind) can be incredibly invasive, and to my knowledge will refuses to run in a VM.
Instructors also have a tendency of not disclosing during registration whether or not they use these proctoring softwares.
I’m lucky enough that by the time I was all-in on Linux, I wasn’t taking courses that used that exam model, but it’s why I make sure that the helpdesk at my current institution offers loaner devices to students who either have computers incapable of running the proctoring software, or who simply don’t want that kind of software on their own machine. It’s a pain in the ass to work with, but apparently it’s enshrined in our faculty’s union contract.
I’ve heard of some methods to bypass it, but unfortunately to test them I’d need to run a real proctored exam, or have our academic technology group set up a “pentesting” one that I can abuse for this software we pay for a license to. Assuming that didn’t land us on Respondus’ bad side and jeapordize our license, it would at best be a waste of time and resources since we couldn’t guarantee students that it wouldn’t get patched or flag them for cheating in the future. The obvious answer is for us as an institution to use better software (or adopt better assessment methods) but software this invasive by nature is generally not going to be open to running on platforms like Linux. And use of proctoring software is unfortunately enshrined in our faculty’s contracts.
And yeah, on the individual level, students themselves can’t really toy with getting it to run in a VM without risking failing an exam. Shit sucks.
As someone who’s worked for several years in higher ed IT and used Linux during my studies, this’ll only get you most of the way there. Unfortunately some proctoring software (Respondus Lockdown Browser comes to mind) can be incredibly invasive, and to my knowledge will refuses to run in a VM.
Instructors also have a tendency of not disclosing during registration whether or not they use these proctoring softwares.
I’m lucky enough that by the time I was all-in on Linux, I wasn’t taking courses that used that exam model, but it’s why I make sure that the helpdesk at my current institution offers loaner devices to students who either have computers incapable of running the proctoring software, or who simply don’t want that kind of software on their own machine. It’s a pain in the ass to work with, but apparently it’s enshrined in our faculty’s union contract.
Kernel-level anti-cheat, it’s not just for gamers.
There are some fairly in depth setups to hide the fact that its a VM normally used for testing malware, I winder if those would fool it.
I’ve heard of some methods to bypass it, but unfortunately to test them I’d need to run a real proctored exam, or have our academic technology group set up a “pentesting” one that I can abuse for this software we pay for a license to. Assuming that didn’t land us on Respondus’ bad side and jeapordize our license, it would at best be a waste of time and resources since we couldn’t guarantee students that it wouldn’t get patched or flag them for cheating in the future. The obvious answer is for us as an institution to use better software (or adopt better assessment methods) but software this invasive by nature is generally not going to be open to running on platforms like Linux. And use of proctoring software is unfortunately enshrined in our faculty’s contracts.
And yeah, on the individual level, students themselves can’t really toy with getting it to run in a VM without risking failing an exam. Shit sucks.
Thankfully our uni forces us to use Linux at least in a form of WSL.
/Sigh
I’m writing a Lemmy comment, not my thesis. Sorry my casual and lazy word choice upset you for not being grammatically correct.