Skip to content
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

ankisyncctl.py deluser does not delete the existing sessions in session.db, so the logged device can still sync even if its account has been deleted in auth.db #72

Open
HaujetZhao opened this issue Jul 4, 2020 · 0 comments

Comments

@HaujetZhao
Copy link

The auth.db stores all the accounts.

The session.db stores all the logged sessions.

When a device has logged in an account, next time it syncs, sync server won't use auth.db to authorize, the server will check the session.db to see if the session of this device has already build, and then the server will directly sync if the session exists.

Now the problem is, after deleting the account using ankisyncctl.py deluser, the device already logged can still sync, because the session data in the session.db still exists.

So I wish this can be fixed: when deleting a user, also delete the related sessions in session.db.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant