Please note that you can subscribe to the individual forums. A subscription for news only covers the news.
Am I correct to assume that page 41 of the manual Preventing Cheating is now outdated after the move to html reports?
There are some details that I would like left out of the report file (or the file to be encrypted) specifically a code that gets generated. Is there anyway to achieve that?
You are partly right. It is not completely correct, as it does not mention that the password command will create an encrypted zip file. But the main content is still correct. I will correct it.
Apart from using Restrict=1, there is no way to leave anything out of the report.
Sven
Ah I missed the point about the script also needing to be encrypted in order todo the password protection.
Assuming there is no way to change an unencrypted to encrypted without looking the status file, I just need to decide if I care about the status file history before I start over!
With a readable script, there is not much point in having a password. 😉
You need to delete the status file to change from an unencrypted to an encrypted script.
Sven
