Is it possible to lock the repy application files to prevent modification?

[SemicolonExpected]

It's come to my attention that the RePy application files are mutable due to a student injecting stuff into the repy.py file as one of their attack cases.

While that is a good attack, I do think it might be good to have a method of preventing that as depending on how it was done it could corrupt the build. While this student cleaned up after themselves and provided a script to sanitize the repy.py file others might not have the foresight and it might create problems.

[JustinCappos]

This is a good observation. Usually one does not place the user directory / user code in the same directory as the repy source code. I'd recommend we make the instructions for running repy clearer so that that sort of use case is not common for students using the framework.

[SemicolonExpected]

I think the repy.py file itself has to be in the directory at least due to the fact that the command we run is repy.py restrictions.default encasementlib.r2py <referencemonitor> <attack>

[JustinCappos]

We should be encouraging them to use the --cwd flag to set the current directory. I think we left this out to make it easier for the students to run the code and understand what is happening.

…

On Thu, Nov 19, 2020 at 8:01 AM Victoria Zhong ***@***.***> wrote: I think the repy.py file itself has to be in the directory at least due to the fact that the command we run is repy.py restrictions.default encasementlib.r2py <referencemonitor> <attack> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGROD2WXGWBEF2VU4Q35ETSQRN7BANCNFSM4T2VFQPA> .