Repository navigation
way to sanitize passwords from history #163
ndwarshuis
started this conversation in
Ideas
Replies: 1 comment
|
Better idea, use a list of hashed passwords to filter out greenclip's history. General workflow
This has the advantage of not revealing any additional passwords in plain text (on the off chance that the database dump is not deleted after). Further, it also shouldn't be that hard to implement, since all greenclip needs to do is hash each entry and do a set difference. It also guarantees that passwords will be deleted without the additional overhead of maintaining application blacklists or relying on imperfect heuristics. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
It is currently very hard to avoid passwords ending up in the history file. Blacklisting applications can somewhat help except that many password managers operate within a web browser.
There should be a simple way to identify passwords since they often don't look like the rest of text one is likely copying (assuming a password manager with good random passwords obviously).
In greenclip, I can think of two ways to deal with this:
I'm guessing 1. will be quite hard since it would require adding lots of complexity to greenclip itself.
However, I don't know of a clean way to implement 2. given that the history file has binary entries in it that are difficult to parse. I'm aware one can print the history but as far as I can tell there is no way to do the reverse. One tractable solution might be an API for editing the history, which might also fix #155.
All reactions