You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you've finished up with creating and modyfing the handin.py file it's probably best to add a layer of obfuscation. Essentially it means to make the code unreadable to users. Python has a built in compiler to byte-code: python -OO -m py_compile handin.py
This produces a .pyo file that contains byte-code, and where docstrings are removed, etc. You can rename the .pyo file with a .py extension, and handin.py runs like your program but does not contain your source code. This is likely enough to deter any students that get their hands on the handin.py file from figuring out how to break the system.
However this isn't 100% safe, https://github.com/Mysterie/uncompyle2 is a tool that can recover lots of the code and names so this should just be the first safety net.
Could you point me to where the application runs grading?
The text was updated successfully, but these errors were encountered:
handin-system-ul/script_download_server.py
Line 190 in f9c42df
Once you've finished up with creating and modyfing the handin.py file it's probably best to add a layer of obfuscation. Essentially it means to make the code unreadable to users. Python has a built in compiler to byte-code:
python -OO -m py_compile handin.py
This produces a .pyo file that contains byte-code, and where docstrings are removed, etc. You can rename the .pyo file with a .py extension, and handin.py runs like your program but does not contain your source code. This is likely enough to deter any students that get their hands on the handin.py file from figuring out how to break the system.
However this isn't 100% safe, https://github.com/Mysterie/uncompyle2 is a tool that can recover lots of the code and names so this should just be the first safety net.
Could you point me to where the application runs grading?
The text was updated successfully, but these errors were encountered: