Skip to content

use schema version to decide decryption #177

Description

@ginsburgnm

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions