Skip to content

[pass] [FR] Allow overriding file "schema" to allow for different pass file layouts #213

@mrmalachai

Description

@mrmalachai

Extension name

pass

Description

The pass password store uses a flat-file user-formatted layout, allowing for any number of "acceptable" configurations. Some users (like myself) currently have hundreds - even thousands - of passwords stored already with a scheme that they depend on daily. Re-tooling the entire database when that many password files exist is exhausting - bordering on impossible. Please allow an option to define some sort of schema for these files to allow for different use cases.

For example, my password store files are laid out thusly:

password
username
http://web.site-goes-he.re
otpauth://otp-url

Anything below line 4 is generally a space-separated line of backup codes. If one of the lines isn't used, it's left blank unless it's the last line. This is only one example. key: value is another common method, but didn't fit my use case. Files named [username].gpg with first line being password is also common. Some way of specifying these special cases could be very helpful as well.

Steps to reproduce

No response

Vicinae version

v0.20.7

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions