Change Location of Encrypted Logs #71
Labels
No Label
accessibility
beginner-friendly
bug
code
critical
cygwin
documentation
duplicate
enhancement
error reporting
external
help wanted
infrastructure
invalid
investigate
language-spec
logs
lti
mac
maybe
qtype:bigbox
qtype:checkoff
qtype:expression
qtype:fileupload
qtype:multiexpression
qtype:multiplechoice
qtype:number
qtype:pythoncode
qtype:pythonic
qtype:pythonliteral
qtype:richtext
qtype:smallbox
question
question types
sandbox
security
ui/ux
wontfix
wsl
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: catsoop/catsoop#71
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
When logs are encrypted (at least according to our current scheme), they spread out and create a lot of files. It might make sense to store those logs in locations analogous to what we're currently using for lockfiles, instead of the current scheme.
We should maybe also switch both to use SHA3-512 for hashing instead of blake2 (and probably also do the same for uploaded files as well).