-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create an "exam proctoring mode" #1919
Comments
My thoughts:
Proposal 1: Create a file extension Proposal 2: Put some meta data in a distributed directory to let the client know that it's a exam, to warn the student before opening, and then lock down access to anything outside that directory for the duration of the exam. Proposal 1 is super clean to me but Proposal 2 seems more general and matches how Assignments and Handouts work. |
For genuine security, this will also require either:
I think (1) is basically impossibly hard -- the security problems are likely insurmountable. So (2) has to be the way to go, and will be easier after the k8s rewrite (when ephemeral projects will be easier to implement). |
I'm confused what you mean by this. I think locking them out of certain things via the client should be sufficient.. |
If you can execute code in a worksheet than you have 100% full read/write access to absolutely anything in that project. There is no possible way to restrict that. It's the underlying OS security model. |
Oh, you mean they could do something like parse old homework from within the exam worksheet? |
Yes. |
Are there any updates on this issue? This seems even more relevant these days, and I could & would certainly use this. |
Unfortunately, there has been no further work on this issue. |
#7110 is a fresh follow up with some proposals. |
In the “exam proctor mode”, you can lock SMC into only one worksheet that can be opened.
This is to focus the students and also to avoid cheating on exams, e.g., where the student just opens up their old files and copy code in.
Requested by instructors regularly.
The text was updated successfully, but these errors were encountered: