mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #8] Password from floccus sync appears in nextcloud logs #9
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#9
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 @realitygaps on GitHub (Jan 13, 2017).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/8
Messages in logs include:
/index.php/apps/bookmarks/public/rest/v1/bookmark?user=USERNAME&password=PASSWORD
with nextcloud password in plain text.
@marcelklehr commented on GitHub (Jan 13, 2017):
Hi @realitygaps!
Thanks for reporting this. I'm afraid that's a flaw with the nextcloud bookmarks app, which is being addressed in the upcoming release, however.
@realitygaps commented on GitHub (Jan 13, 2017):
ah thanks for the information, ill wait for the update then.
also thanks for this extension :)
@marcelklehr commented on GitHub (May 14, 2017):
This is fixed now.
@9662 commented on GitHub (May 20, 2017):
Hello @marcelklehr, many thanks for your work on this project! 😊
Would that be in 0.10.0? I have that installed and it is still leaking the plaintext app password. Should I open a bug in the Nextcloud tracker?
@9662 commented on GitHub (May 20, 2017):
Never mind. Disabling and re-enabling the Bookmarks app in Nextcloud did it.
@github-actions[bot] commented on GitHub (Mar 21, 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.