mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1060] stop showing the passphrase in clear plain text #703
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#703
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pinpontitit on GitHub (Mar 5, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1060
Describe the feature you'd like to request
Everytime I check my extension settings or the Android app, my cherish and very secret passphrase appears to me in plain, not encrypted, text.
Its always a choc when I see it like this non hidden.
Describe the solution you'd like
You should force asterisque caracter, like this nobody is able to read it over my shoulder.
Describe alternatives you've considered
You could also decide to completely hide it.
I mean we have to choose it to encrypt the backup but we don't need to see it everyday.
So when we set up the backup we could write this passphrase and then it doesnt appear anymore.
If we lose it, we lose it
@marcelklehr commented on GitHub (Mar 5, 2022):
This appears to be a bug. Passwords should be hidden by default, but there should be a button allowing to view the password. Can you open a bug report instead?
@github-actions[bot] commented on GitHub (Mar 20, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.