(migration) Config: Security for passwords #13
Labels
No labels
bug
critical
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
kir68k/lattice#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current implementation is storing both the account and e2ee key passwords as plaintext. I don't really like that...
I'll look at this after adding token caching (maybe later today).
The config rn only serves to skip prompts at the start, but room selection and verification still require input. Room selection could be added directly to the config, but verification will be only done once as a part of #16 with some sort of database or store for secrets. I think the password here could be removed and passed from that store, or be a path to where the password is.
For Linux desktops I know Secret Service exists, so a crate like oo7 could help, but I have to think about servers and Windows as well.
Config: Security for passwordsto (migration) Config: Security for passwords