Emmanuel Blot wrote:
I hadn't considered the session/auth tables until I read this. I do full dump
of the project DBs prior to archiving. Thankfully I haven't had to restore
one yet, but I assume I'd be opening up a security hole and a half by
restoring these tables?
I couldn't tell: I never considered the security issues up to now, and
I don't know enough about security matter to give any useful answer
;-)
It's not a Trac issue, really, just something admins might want to be wary of
when restoring dumps. This probably applies to any DB that stores auth cookies.
If I decided to deny access to user 'X' after some malicious damage was
caused, I could restore from a backup and delete their user account, but it
could still have a valid session cookie for user X that would grant them have
full privileges until it expired.
I'm using Basic auth myself, so the auth_cookie table is empty. Removing the
htpasswd entry would have the desired immediate effect. I suppose it would
only be an issue if the registration system is in use (or accountmanager
plugin), but I haven't used those so I can't confirm.
Cheers,
Manu
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
