[GH-ISSUE #1398] Encryption not active when set up during account creation #920

Closed
opened 2026-02-25 22:38:28 +03:00 by kerem · 3 comments
Owner

Originally created by @eljoest on GitHub (Jun 8, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1398

Which version of floccus are you using?

4.19.1 (F-Droid)

Sync method

Google Drive

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Android 11 (OnePlus)

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

After the initial setup of the account including an encryption password, I discovered that the file saved to Google Drive was not encrypted.

The configured password was exported (in plain text) when I chose to export the account settings just before checking the upload file.

Afterwards I discovered that the "Passphrase" section in the settings showed an add button. After adding the password again through this button, the uploaded file is encrypted.

Expected Behavior

Encryption configured during account setup is active at once.

To Reproduce

  • On a fresh install
  • create a new account with Google Drive sync
  • leave all settings at their defaults
  • enter an encryption password
  • complete the account creation
  • add some bookmarks
  • export the settings to confirm the encryption password is present
  • force sync
  • check google drive file

Debug log provided

  • I have provided a debug log file
Originally created by @eljoest on GitHub (Jun 8, 2023). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1398 ### Which version of floccus are you using? 4.19.1 (F-Droid) ### Sync method Google Drive ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Android 11 (OnePlus) ### 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 After the initial setup of the account including an encryption password, I discovered that the file saved to Google Drive was not encrypted. The configured password was exported (in plain text) when I chose to export the account settings just before checking the upload file. Afterwards I discovered that the "Passphrase" section in the settings showed an add button. After adding the password again through this button, the uploaded file is encrypted. ### Expected Behavior Encryption configured during account setup is active at once. ### To Reproduce * On a fresh install * create a new account with Google Drive sync * leave all settings at their defaults * enter an encryption password * complete the account creation * add some bookmarks * export the settings to confirm the encryption password is present * force sync * check google drive file ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:28 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Jun 8, 2023):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

<!-- gh-comment-id:1581990847 --> @github-actions[bot] commented on GitHub (Jun 8, 2023): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. I'm Marcel and I created floccus and have been maintaining it ever since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. Note also that GitHub is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. I look forward to working with you on this issue Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Dec 5, 2023):

Confirmed also for browser usage.

<!-- gh-comment-id:1841317120 --> @marcelklehr commented on GitHub (Dec 5, 2023): Confirmed also for browser usage.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 6, 2024):

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.

<!-- gh-comment-id:2521812971 --> @github-actions[bot] commented on GitHub (Dec 6, 2024): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#920
No description provided.