Difference between revisions of "Convert password storage to a SQLite database"
(→Project News) |
(→Project Details) |
||
| Line 14: | Line 14: | ||
== Project Details == | == Project Details == | ||
| + | Currently firefox currently writes usernames and passwords to a file in the users profile (signon2.txt). Instead of this, it will be written and read from a sqlite database. I've looked at some of the c++ source code for interacting with a sqlite db and it seems simple enough. But, firefox uses a unified storage system called mozstorage that to my understanding already handles db interactions. I'll have to look into this. Also, I'll have to look into the patches already released for this assignment. | ||
| + | |||
| + | Tentatively my release schedule looks something like this: | ||
| + | |||
| + | v0.1<br/> | ||
| + | Have the tables set up in the db (possibly create the db or use an existing one). <br/> | ||
| + | v0.2<br/> | ||
| + | Start having data written to the db in conjunction with the file read writes. I don't see a need to strip out the current code.<br/> | ||
| + | v0.3<br/> | ||
| + | Continue with the read/writting to the db.<br/> | ||
== Project News == | == Project News == | ||
Revision as of 12:28, 1 October 2007
Contents
Project Name
Convert password storage to a SQLite database
Project Description
Currently, Firefox stores logins in a text file in the user's profile (signons2.txt). The format is simple, but inflexible. Storage of other browser data, such as cookies and form history, has steadily been moving towards using SQLite-backed databases so moving password storage to the same kind of storage would be good. Some work was started in bug 288040.
Project Leader(s)
Project Contributor(s)
Project Details
Currently firefox currently writes usernames and passwords to a file in the users profile (signon2.txt). Instead of this, it will be written and read from a sqlite database. I've looked at some of the c++ source code for interacting with a sqlite db and it seems simple enough. But, firefox uses a unified storage system called mozstorage that to my understanding already handles db interactions. I'll have to look into this. Also, I'll have to look into the patches already released for this assignment.
Tentatively my release schedule looks something like this:
v0.1
Have the tables set up in the db (possibly create the db or use an existing one).
v0.2
Start having data written to the db in conjunction with the file read writes. I don't see a need to strip out the current code.
v0.3
Continue with the read/writting to the db.
