Beyond simply adding an auto-clear timer (covered in a related issue), there's no user education at all in handleCopy (app/auth/create.tsx) about clipboard as an attack surface — other apps with clipboard-read permission (increasingly restricted by OS but still relevant, and fully unrestricted on many Android builds/MDM-managed corporate devices) can read what's copied. This is lower severity for a public key than a secret, but the copy pattern here is precedent for whatever copies a secret/mnemonic later.
Definition of done:
- User-facing microcopy warning shown on first copy action (dismissible, not nagging every time)
- Documented as a required pattern for any future "copy secret/mnemonic" feature, escalated beyond just a warning (e.g. combined with the auto-clear timer, non-negotiable there)
- No regression to the copy UX for the common, lower-risk public-key case
Before opening a PR for this issue, read CONTRIBUTING.md.
This is not a starter-issue. The Definition of done above is the full
acceptance criteria, not a subset to sample from — a PR that addresses part
of it is an unfinished issue, not a smaller one. Your PR must include, in
the PR description itself:
PRs missing these will be sent back before review, not reviewed and rejected — please do this up front.
Beyond simply adding an auto-clear timer (covered in a related issue), there's no user education at all in
handleCopy(app/auth/create.tsx) about clipboard as an attack surface — other apps with clipboard-read permission (increasingly restricted by OS but still relevant, and fully unrestricted on many Android builds/MDM-managed corporate devices) can read what's copied. This is lower severity for a public key than a secret, but the copy pattern here is precedent for whatever copies a secret/mnemonic later.Definition of done:
Before opening a PR for this issue, read CONTRIBUTING.md.
This is not a starter-issue. The Definition of done above is the full
acceptance criteria, not a subset to sample from — a PR that addresses part
of it is an unfinished issue, not a smaller one. Your PR must include, in
the PR description itself:
PRs missing these will be sent back before review, not reviewed and rejected — please do this up front.