-
Notifications
You must be signed in to change notification settings - Fork 71
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
temp directory contents not cleaned up on logout #20
Comments
Thinking about this more do we really want to do this? It's been handy throughout the years to have the files live on while testing out doors, etc. WTDY? Original comment by: wwiv |
it's a security issue. Since the files are not cleaned up, a different user can get access to information left behind by the previous user. It's generally just drop files, but what if there are other files in the temp directory that have something more sensitive? Original comment by: granitepenguin |
ok, I looked a bit closer, and everything except for the drop files are deleted on exit (by design). I'm not saying the design is right but it purposely leaves the drop files. Here's the code: while (bFound) {
} Original comment by: wwiv |
This was fixed in r1386 Original comment by: wwiv |
Original comment by: wwiv |
Build: r1099
Operating System: Linux
What Happened: drop files in temp directory do not get cleaned up on logout. They get updated when a door is accessed, which means it's possible for the wrong user's data to exist in a node's temp dir
What was expected: temp files are removed when a user's session ends.
Original comment by: granitepenguin
The text was updated successfully, but these errors were encountered: