Clippy and KeePass

Open
#5 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
desktop, security

Research direction

The issue names no files, tests, or entry points. Start by inspecting how clippy handles clipboard contents and whether it can detect KeePass or other running applications; the desired blocking behavior and security implications need to be agreed before implementation. Done would require a documented decision, an implemented safeguard, and tests covering the KeePass interaction.

Written by the indexing model from the issue text.

Description

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.

Dominant language
C
Stars
145
Forks
15
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EsotericSoftware/clippy

All issues in EsotericSoftware/clippy

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.