Warning banner for individual 2FA entry exports
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, java
- Domain
- authentication, mobile-dev, security
Research direction
Start by reading the implementation and behavior referenced by issue #132 for plaintext full exports, then trace the "Transfer Entries" flow. Done means individual 2FA entry exports trigger a persistent warning banner that remains visible for a few days, with behavior appropriate for the app's security model.
Written by the indexing model from the issue text.
Description
When the "Transfer Entries" feature is used, it would be useful it a persistent warning banner shows for a few days, similar to #132 which triggers on full exports in plaintext.
It's unavoidable to sometimes provide access to your phone (customs, police etc). In those cases you'd want to know if individual 2FA codes were exported.
I realise the Aegis app requires authentication to access it and locks with the phone. This feature would account for scenarios where users might not opt into encrypting the vault.
- Dominant language
- Java
- Stars
- 13.1k
- Forks
- 589
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from beemdevelopment/Aegis
-
proposal
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
beemdevelopment/Aegis#1840 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
beemdevelopment/Aegis#1837 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
beemdevelopment/Aegis#1824 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
beemdevelopment/Aegis#1823 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
beemdevelopment/Aegis#1675 · 4 comments ·
All issues in beemdevelopment/Aegis
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
HL7/fhir-ig-publisher#1375 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Flaky: a relaunched catch-up replay can still report catching up right after its marker is written Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
johanhaleby/occurrent#1134 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/jeo-maven-plugin#1811 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100