mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1059] Passwords are not decrypted in UI after enter passphrase, when open options before entering security passphrase #702
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#702
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/1059
Which version of floccus are you using?
Floccus extension for firefox
Sync method
{"label"=>"Google Drive"}
Which browser are you using?
Librewolf
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
Today when I checked the flocxus extension settings, I discovered that my passphrase had changed.
It became a sequence of like 30 random caracters like "H6Klm9y3OU0lhZ6jKL....."
I dont know if in consequence the syncing stopped or no, I just saw that my passphrase was replaced by that.
Expected Behavior
I should have found my original passphrase the one I choosed.
To Reproduce
I dont know if yiu would be able to rzproduce it.
I just went to check the settings and discivered that. The extension was installed and set up 2 days ago.
Is it a bug or are you trying to implement some encryption to the passphrase ?
Or is it revealing some encryption process that should be hidden ?
Debug log provided
@marcelklehr commented on GitHub (Mar 5, 2022):
It could be some bug associated with credential protection (Unlock passphrase). Did you set that up as well?
@pinpontitit commented on GitHub (Mar 5, 2022):
Hi
No, credential protection wasn't set up, and still isnt set up.
Today I went to check and my passphrase is back to normal.
@marcelklehr commented on GitHub (Mar 5, 2022):
Then let's wait for it to reappear to pin point what's happening.
@pinpontitit commented on GitHub (Mar 14, 2022):
Hi
So it happened again.
You're right it must be related with the Credential Lock function.
When I opened my browser, a tab with Floccus settings was open (maybe from previous session). On top of the settings was the pop-up asking for my Credentials and I could see behind it that my passphrase was looking pretty long (which I like because like this no one can see the length of my true passphrase).
After entering my credentials, the popup disappeared, and I could see that my passphrase was still very long. And by clicking in the Eye icon, to reveal it, I discovered that the passphrase was a series of random caracters.
After closing the tab, and opening the Floccus settings again, my passphrase was back to normal.
So it means that after unlocking my credentials, Floccus didnt changed the encrypted passphrase to my normal passphrase automatically. I had to close and open again Floccus settings.
Its not a big issue, maybe not an issue at all, but I wanted you to know.
@marcelklehr commented on GitHub (Mar 15, 2022):
Ah, yes, that's an edge case I hadn't considered. I'll see what I can do. :)
@pinpontitit commented on GitHub (May 22, 2022):
Now that the passphrase isn't showing anymore I think I can close this issue.
@github-actions[bot] commented on GitHub (May 23, 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.