Skip to content

fix: last 2.0.0 security items and public docs - #42

Merged
pasichDev merged 5 commits into
mainfrom
release/2.0.0-finish
Sep 25, 2026
Merged

pasichDev merged 5 commits into
mainfrom
release/2.0.0-finish

Conversation

@pasichDev

Copy link
Copy Markdown
Owner

What

  • PIN kept in a wiped CharArray on the PIN change screen, in the settings checks and in backup re-authentication.
  • One biometric prompt at a time on the lock screen and the settings switch. A prompt lost to activity recreation no longer leaves the fingerprint button stuck.
  • New tests:
    • Back on the lock screen;
    • recreation during a prompt;
    • FLAG_SECURE after onCreate and after recreation;
    • a scan that fails on share intents, notifications, alarms or clipboard writes outside SensitiveClip.
  • Every public document brought in line with 2.0.0: README, SECURITY, PRIVACY, CONTRIBUTING, CHANGELOG (dated 2026-09-25), architecture notes, the bug report template and LICENSE years.
  • Merges the Dependabot CI bumps from main.

Why

These are the last open items before tagging v2.0.0 and making the repository public.

Testing

  • spotlessApply detekt testFdroidDebugUnitTest assembleFdroidDebug assembleFdroidRelease: 972 tests, 0 failures.
  • A clean clone builds assembleFdroidDebug without any secrets.

Not verified: the biometric changes on a device; they are covered by Robolectric tests only.

References

Closes #7, #9, #13, #15, #16, #17, #21, #25 (already closed with notes).

- The PIN is a wiped CharArray on the PIN change screen, in the settings
  checks and in backup re-authentication (#21)
- One biometric prompt at a time on the lock screen and the settings
  switch; a prompt lost to activity recreation no longer leaves the
  fingerprint button stuck, and a late answer is dropped (#7, #13)
- Tests: Back on the lock screen, recreation during a prompt, FLAG_SECURE
  after onCreate and recreation, and a scan that fails on share intents,
  notifications, alarms or clipboard writes outside SensitiveClip
  (#13, #15, #16)
- Docs: the auto-lock delay in SECURITY.md, the FAQ, the store listing
  and README (#9); note links documented as a deliberate exception (#25);
  biometric toggle policy; README crypto overview brought up to date
README, SECURITY, PRIVACY, CONTRIBUTING, the architecture notes and the
bug report template now match the shipped app: auto-lock delay,
Keystore-bound PIN, the danger-zone erase, the permissions actually
requested, and where Ko-fi appears. CHANGELOG 2.0.0 is written for the
public and dated 2026-09-25.
Selected text can be copied too, and every copy is marked sensitive and
cleared after about a minute.
The focused block drew a 2 dp primary frame. The caret marks focus now;
the block padding is unchanged, so text does not move.
@github-actions

Copy link
Copy Markdown

Coverage (core/security)

Overall Project 68.54% 🍏
File Coverage
SeedPhraseManager.kt 93.42% 🍏

@pasichDev
pasichDev merged commit 703f559 into main Sep 25, 2026
1 check passed
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

Successfully merging this pull request may close these issues.

[Beta blocker][Security] Require re-authentication before changing biometric security settings

1 participant