-
Notifications
You must be signed in to change notification settings - Fork 462
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
Clearing clipboard after timeout #2746
Comments
@hluk thanks for this app. the klipper's bugs were boring me. @Massimo-B Good question? |
There is Clear Clipboard After Interval, but it won't work with password managers, because CopyQ in the recent versions completely ignores clipboard content with passwords/secrets. I will try to modify CopyQ so it lets you react on data from password managers. |
Allows running scripts and automatic commands even if clipboard data was copied from a clipboard manager or an internal data format (`application/x-copyq-*`) changed. Fixes #2746
Allows running scripts even if clipboard data was copied from a clipboard manager or an internal data format (`application/x-copyq-*`) changed. Fixes #2746
Allows running scripts even if clipboard data was copied from a clipboard manager or an internal data format (`application/x-copyq-*`) changed. Fixes #2746
Thanks, could you provide a short hint how to use this new feature? |
See README.md for details on how to add the command. |
Oh, BTW, I did not release the fix for in CopyQ yet. But if you are on Windows, you can use development build: https://ci.appveyor.com/project/hluk/copyq/builds/50193991/artifacts |
I have no idea where to start to get the clipboard manager either ignore passwords from KeepassXC or delete them after a while. It seems that there is some standard to inform the clipboard manager about sensitive passwords. |
I know you have a scripting API and also a feature to blacklist applications.
But do you support some (default?) API that provides a way for password managers to clear the clipboard after some timeout, as mentioned in
keepassxreboot/keepassxc#9842
?
The text was updated successfully, but these errors were encountered: