Skip to content
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.

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

Clippy and KeePass #5

Open
XOCODE-OP opened this issue Sep 18, 2016 · 3 comments
Open

Clippy and KeePass #5

XOCODE-OP opened this issue Sep 18, 2016 · 3 comments

Comments

@XOCODE-OP
Copy link

I use KeePass to manage passwords.
KeePass automatically copies a password into your clipboard and removes it after a short while.
Now obviously you can see where there is a security issue when running clippy at the same time.
Of course you could just manually disable clippy, but I would wish there was some sort of feature for this, maybe to block the copy to clippy db if KeePass is running or similar.

@NathanSweet
Copy link
Member

The easiest thing to do is to use shift+ctrl+delete to delete entries from the Clippy popup. That is easier than closing, copy/pasting, and reopening Clippy, but if you forget after copying a password then yes, your password would be forever stored in Clippy which you may not be comfortable with.

I don't use KeePass but it probably isn't super hard to hack Clippy to avoid storing the clipboard contents based on whatever criteria makes sense for KeePass.

@XOCODE-OP
Copy link
Author

Yea I do that actually.
Just the thought that my password is on screen for a second is... Well its ironic when you use a password manager, lets just say :P

Yea like... if application name is KeePass, then dont store, kinda thing.

@NathanSweet
Copy link
Member

You'd need to determine exactly what makes sense for avoiding storage of the clipboard contents. Maybe checking the active window title is enough. If so, something generic and configurable like that could be added.

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

No branches or pull requests

2 participants