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.

Sign up for GitHub

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

Jump to bottom

use schema version to decide decryption #177

Open

ginsburgnm opened this issue Jun 4, 2020 · 0 comments

Collaborator

ginsburgnm commented Jun 4, 2020

This is an issue with the way I did legacy schemas. I forgot there's a schema version marker, and just embedded a try except.

Due to this, there exists a side effect of passwords existing as schema version 2 even though the file states version 1. cleanup will be necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment