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

A method to specify that a sensitive entry should not go to the history #31

Closed
zefr0x opened this issue Oct 17, 2022 · 1 comment
Closed

Comments

@zefr0x
Copy link

zefr0x commented Oct 17, 2022

Some times we need to copy sensitive data like when using a password manager. In those cases we need a standard way to tell Clipcat that this entry should not go to the history.
Turning off clipcatd temporary or deleting the entry manualy is not a sulotion.

The best way to do that is using mime-type.
The clipborad holds a mime-type along with the content in order to differentiate between contents data types like text, images or videos...

For example the Klipper clipborad manager uses x-kde-passwordManagerHint as implemented here. And the KeePassXC password manager is making use of that here: keepassxreboot/keepassxc#1969

Refs:

@xrelkd
Copy link
Owner

xrelkd commented Dec 6, 2023

Thanks for the proposal.
The pull request #170, #139 might solve this issue.
Sensitive content could be detected by clipcatd now.
The hint such as x-kde-passwordManagerHint could be passed from configuration watcher.sensitive_x11_atoms. clipcatd ignores the clip once one of the X11 atoms listed in sensitive_x11_atoms is matched, the sensitive contents are ignored, they will not be shown on the list, history, log message.

The new features will be introduced in the next release.

@xrelkd xrelkd closed this as completed Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants