by Julian Fitzell (Developer) on Sept. 22, 2017 · permalink

Best would be to raise a bug on https://github.com/jfitzell/mozilla-keychain

If you're not comfortable sharing the logs there, you can email them to me (first initial and last name at gmail.com)

Would also be good to know if this is with every site or only (a) certain one(s)

- Julian

by Julian Fitzell (Developer) on Sept. 8, 2017 · permalink

Best would be to raise a bug on https://github.com/jfitzell/mozilla-keychain or if you're not comfortable sharing the logs there, email them to me (first initial and last name at gmail.com)

Thanks for the pointer about clearing passwords on shutdown... looks like that functionality was removed in FF42. I've closed the relevant bug on github and will update the notes on the extension page.

by Julian Fitzell (Developer) on July 19, 2017 · permalink

Yes, I still can't understand why FF doesn't support it natively. The extension should "just work" but there are lots of moving pieces controlled by Mozilla and Apple so when it fails it can be hard to work out why.

You can try turning on debug logging as explained on the add-on page and see if that highlights the problem. I'm afraid I don't have much time to spend on this these days but if the problem isn't clear, email the logs to me and I'll see if I can spot it easily.

by Julian Fitzell (Developer) on May 23, 2017 · permalink

It should use your keychain search path, which should be the same order as the list you see in the top left pane in Keychain Access (you could confirm by running "security list-keychains" in the console)

There are two undocumented preferences, which I use mainly for testing:
extensions.macos-keychain.search-path - a colon-separated list of keychain paths to search for passwords (overriding the system search path)
extensions.macos-keychain.write-file - the path to the keychain where passwords should be stored

You can set both of these by going to "about:config" in Firefox

The problem is that the Local Items keychain used by iCloud isn't stored as a keychain file and doesn't seem to show up explicitly in the search path, so this may not give you exactly what you want. But it might let you find a workable solution.

by Julian Fitzell (Developer) on June 15, 2016 · permalink

Well spotted - not related to multi-process though as far as I can see. Seems LoginManager has changed and is now calling searchLogins() which I never implemented.

Probably not too hard to do so – if anyone has time and wants to fix and submit a pull request on github that would be terrific. Not sure when I'll have time to get to it at the moment unfortunately....

In the meantime, I've marked as only compatible up to 48.* for now.

by Julian Fitzell (Developer) on Feb. 15, 2016 · permalink

I sort of agree but, I'm only replacing the password saving mechanism – it's Firefox that chooses to show you the passwords it reads from the password database.

Safari's also not offering much protection, to be honest. If you've allowed a browser access to a particular password and your keychain is unlocked, someone with control of your computer could simply go to the website in question, allow the password to be filled, and then copy the value from the password field (possibly using JavaScript if necessary).

Basically, if you want to keep a password secure from someone with physical access to your computer, you shouldn't store it in an unlocked keychain.

by Julian Fitzell (Developer) on July 5, 2015 · permalink

Sorry you're having trouble; why do you think this extension is the cause of the problems you are seeing? It doesn't do anything to the toolbar, so I don't know why it would be impacting that. I'm also using FF 39.0 myself right now and all seems normal.

If you haven't already, please try disabling extensions one at a time to confirm which is causing the problem. If it really is this one, then please enable debug logging as explained on the extension info page and send me the full logs by email.