Remove legacy signons.sqlite files and references
Categories
(Toolkit :: Password Manager, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox120 | --- | fixed |
People
(Reporter: Paolo, Assigned: vitaspiros, Mentored)
References
Details
(Keywords: good-first-bug, privacy, Whiteboard: [passwords:tech-debt] [lang=js])
Attachments
(1 file, 2 obsolete files)
Bug 853549 introduces the new "logins.json" file for storing Login Manager data, replacing the legacy "signons.sqlite" file. This SQLite file is kept around and may still be used in case the profile is downgraded. In a similar way to bug 925101 for the legacy "signons.txt" file, the SQLite file should be deleted after it has not been used for some time. Note that there might be similarly named files in case a backup was made because of a corrupted database, and these might be deleted as well. This should not happen on Android, where the SQLite file is still used.
Updated•8 years ago
|
Updated•8 years ago
|
Comment hidden (obsolete) |
Updated•6 years ago
|
Updated•6 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Type: defect → task
This is a defect since we're leaving stale data in profiles.
Updated•5 years ago
|
Comment hidden (obsolete) |
Comment 4•3 years ago
|
||
I tlooks like this code doesn't exist anymore, there's still a couple references to signons.sqlite that should be removed:
https://searchfox.org/mozilla-central/search?q=signons.sqlite&path=&case=false®exp=false
Comment 5•3 years ago
|
||
(In reply to Marco Bonardo [:mak] from comment #4)
I tlooks like this code doesn't exist anymore, there's still a couple references to signons.sqlite that should be removed:
https://searchfox.org/mozilla-central/search?q=signons.sqlite&path=&case=false®exp=false
See comment 2. The main focus of this bug is deleting the leftover signons.sqlite files in the profile directory of users.
Comment 7•3 years ago
|
||
Yes, it's available. there's a few references to remove in comment 4, and you should write a UI Migration function to remove leftover files from the profiles.
See for example how migration 119 was implemented https://searchfox.org/mozilla-central/rev/2e3b0483e31abffe0b4374480a34c6d23f5186ea/browser/components/BrowserGlue.jsm#3300,3303,3931
Feel free to Request Info from me using the checkbox below if you have questions, or just ask on Phabricator once you submit a patch.
Hi, I have a few queries. How current UI versions are determined? Up to which UI version, these signons.sqlite files are required.
Thank you.
Comment 10•3 years ago
|
||
Updated•3 years ago
|
Comment 11•3 years ago
•
|
||
(In reply to Riya from comment #9)
Hi, I have a few queries. How current UI versions are determined? Up to which UI version, these signons.sqlite files are required.
Thank you.
UI version is just an increasing number, when a new profile is created the version number is bumped to the current one, and no migration runs because it assumes it's up-to-date being a new profile. Old versions on upgrade will instead run all the migrations from their version number to the current one. Migrations run only once per profile. A new Firefox version can have multiple ui migrations or none, there's no relatione between the Firefox version number and the migration version.
Comment 12•2 years ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Comment 13•2 years ago
|
||
(In reply to Marco Bonardo [:mak] from comment #7)
Yes, it's available. there's a few references to remove in comment 4, and you should write a UI Migration function to remove leftover files from the profiles.
See for example how migration 119 was implemented https://searchfox.org/mozilla-central/rev/2e3b0483e31abffe0b4374480a34c6d23f5186ea/browser/components/BrowserGlue.jsm#3300,3303,3931
Feel free to Request Info from me using the checkbox below if you have questions, or just ask on Phabricator once you submit a patch.
is this still open? if so can i get assigned the isssue?
Updated•2 years ago
|
Comment 14•2 years ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 15•1 year ago
|
||
Hello, I would like to take this over if possible!
Comment 16•1 year ago
|
||
Feel free to attach a patch when you have it, there is an old one that can be used as a starting point
Comment 17•1 year ago
|
||
Hello Marco,
I got the basic removals done, but I was unable to find browser/components/BrowserGlue.jsm. Am I missing something? I am fairly new, so I may be missing the obvious.
Thank you! :)
Comment 18•1 year ago
|
||
(In reply to Ivan from comment #17)
Hello Marco,
I got the basic removals done, but I was unable to find browser/components/BrowserGlue.jsm. Am I missing something? I am fairly new, so I may be missing the obvious.
Thank you! :)
Also, I have built and run everything successfully. Just FYI.
Comment 19•1 year ago
|
||
(In reply to Ivan from comment #17)
Hello Marco,
I got the basic removals done, but I was unable to find browser/components/BrowserGlue.jsm. Am I missing something? I am fairly new, so I may be missing the obvious.
Many .jsm files are in the process of being renamed to .sys.mjs https://searchfox.org/mozilla-central/source/browser/components/BrowserGlue.sys.mjs
Comment 20•1 year ago
|
||
Updated•1 year ago
|
Comment 21•11 months ago
|
||
Hello Marco,
I attempted to apply the corrections that you suggested, but my local version ends at UI_VERSION < 121, but you mention us being on version 137 (one I am adding). How do I update my local build to reflect the latest update? I have looked, but can't find information about it.
Thanks!
Comment 22•11 months ago
•
|
||
(In reply to Ivan from comment #21)
Hello Marco,
I attempted to apply the corrections that you suggested, but my local version ends at UI_VERSION < 121, but you mention us being on version 137 (one I am adding). How do I update my local build to reflect the latest update? I have looked, but can't find information about it.
You can find some documentation at https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/firefoxworkflow.html and https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/workflows.html#
To summarize, you must hg pull central
to update your local tree to the latest version, then you can use hg wip
to visually check the tree situation. you should see both the central
head and your revision. Then you must hg rebase -s <your_revision> -d central
to rebase your revision on top of mozilla-central. You may have to merge some changes. Then just hg update <your_revision>
, make changes, and hg amend
to merge changes into the revision.
Comment 23•9 months ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 24•7 months ago
|
||
Depends on D189346
Updated•7 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Comment 25•7 months ago
|
||
Pushed by mak77@bonardo.net: https://hg.mozilla.org/integration/autoland/rev/11b3d438788a Removed signons.sqlite references r=mak,credential-management-reviewers,dimi
Comment 26•7 months ago
|
||
bugherder |
Description
•