starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 06:35:59 +03:00

[GH-ISSUE #1009] Is Google Drive Encryption working? #661

New issue

Closed

opened 2026-02-25 22:37:46 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:37:46 +03:00

Owner

Originally created by @ashutoshsaboo on GitHub (Dec 10, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1009

Describe the bug

Hi @marcelklehr , thanks for all your efforts with this! I'm new to Floccus, so I tried setting up GDrive sync with passphrase for encryption in settings. Point to note here is that, the first sync that I did was without a passphrase. After the first sync, I entered the encryption passphrase in settings, saved it, and did a push sync again. I'm able to see the entire bookmarks.xbel file in plaintext without any encryption. Is this expected? If not, how can I get the encrypted copy uploaded in GDrive?

I just re-installed the extension and auth with same google account again with passphrase from the very start - still the uploaded file was showing in plaintext in GDrive. Eventually I removed access to floccus altogether from google settings, re-installed app, fresh auth'd google with encryption from very start - after this the uploaded file was encrypted correctly in GDrive. So basically, looks like a bug with not enabling encryption at the start and then on enabling encryption later on - sync doesn't reflect updated file in GDrive?

To Reproduce

Steps to reproduce the behavior:

Install extension, setup GDrive sync without passphrase. Let first sync succeed successfully - verify bookmarks.xbel was correctly created in GDrive.
After first sync was successful, setup a passphrase in settings, save it. Do a sync again.
The same bookmarks.xbel file is updated in GDrive although it still is in plaintext and very easily readable from the web itself

Expected behavior

File should have been encrypted ideally before uploading to GDrive?

Screenshots

Desktop

MacOS, Brave, extension version is - v4.8.6

Server

GDrive

Note: Please write down the actual version numbers instead of writing 'latest'.

Debug log

It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser.

Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://cloud.marcelklehr.de/s/PCi3iLWrzdMZSmw

Debug log provided

Additional context

Add any other context about the problem here.

Originally created by @ashutoshsaboo on GitHub (Dec 10, 2021). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1009 ### Describe the bug Hi @marcelklehr , thanks for all your efforts with this! I'm new to Floccus, so I tried setting up GDrive sync with passphrase for encryption in settings. Point to note here is that, the first sync that I did was without a passphrase. After the first sync, I entered the encryption passphrase in settings, saved it, and did a push sync again. I'm able to see the entire `bookmarks.xbel` file in plaintext without any encryption. Is this expected? If not, how can I get the encrypted copy uploaded in GDrive? I just re-installed the extension and auth with same google account again with passphrase from the very start - still the uploaded file was showing in plaintext in GDrive. Eventually I removed access to floccus altogether from google settings, re-installed app, fresh auth'd google with encryption from very start - after this the uploaded file was encrypted correctly in GDrive. So basically, looks like a bug with not enabling encryption at the start and then on enabling encryption later on - sync doesn't reflect updated file in GDrive? ### To Reproduce Steps to reproduce the behavior: 1. Install extension, setup GDrive sync without passphrase. Let first sync succeed successfully - verify `bookmarks.xbel` was correctly created in GDrive. 2. After first sync was successful, setup a passphrase in settings, save it. Do a sync again. 3. The same `bookmarks.xbel` file is updated in GDrive although it still is in plaintext and very easily readable from the web itself ### Expected behavior File should have been encrypted ideally before uploading to GDrive? ### Screenshots NA ### Desktop MacOS, Brave, extension version is - v4.8.6 ### Server GDrive Note: Please write down the actual version numbers instead of writing 'latest'. ### Debug log It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser. Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://cloud.marcelklehr.de/s/PCi3iLWrzdMZSmw - [ ] Debug log provided ### Additional context Add any other context about the problem here.

kerem

2026-02-25 22:37:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:37:46 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 15, 2022):

Thanks for the report. The issue was that floccus didn't upload because nothing had changed in your bookmarks. This will be fixed in the next release.

@marcelklehr commented on GitHub (Mar 15, 2022): Thanks for the report. The issue was that floccus didn't upload because nothing had changed in your bookmarks. This will be fixed in the next release.

kerem commented

2026-02-25 22:37:47 +03:00

Author

Owner

@ashutoshsaboo commented on GitHub (Mar 15, 2022):

Thanks @marcelklehr ! 🚀

@ashutoshsaboo commented on GitHub (Mar 15, 2022): Thanks @marcelklehr ! 🚀

kerem commented

2026-02-25 22:37:47 +03:00

Author

Owner

@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.

@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.

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#661

No description provided.

Rows
Columns