pfn / passifox

Extensions to allow Chrome and Firefox (4.0+) to auto form-fill passwords from KeePass (requires KeePassHttp)
GNU General Public License v3.0
908 stars 186 forks source link

Support of Firefox Quantum #660

Closed kepicorp closed 4 years ago

kepicorp commented 6 years ago

Hi Everyone,

Is there any plan to support firefox quantum in the near future? It's about to be release as the standard FF in a month or so. I would happy to contribute.

Cheers,

maxbbender commented 6 years ago

+1

linyubin commented 6 years ago

+1

jgottfried commented 6 years ago

https://github.com/smorks/keepasshttp-connector

Owyn commented 6 years ago

Quantum went stable and was auto-updated to for users

jgottfried commented 6 years ago

Yes, and quantum removed the API that passIFox was built on. There won't be an update for Quantum. pfn has stated that they are no longer interested in maintaining this extension. So there haven't been any code change to this repository for 8 months. This has been known for months, too. People worked on compatibility with multi-process Firefox and Quantum (more importantly WebExtensions). See bug #595

Unfortunately there was no reply by the maintainer of this repository to hand over the reigns of the project so it was done under a new name, see my link above.

kepicorp commented 6 years ago

Thanks for your answer

MatrixFr commented 6 years ago

what alternative solution now?! :'(

taurus-forever commented 6 years ago

As pointed here https://github.com/pfn/passifox/pull/595#issuecomment-344444250, you can use "keepasshttp-connector" from https://addons.mozilla.org/en-US/firefox/addon/keepasshttp-connector/

unalignedcoder commented 6 years ago

keepasshttp-connector is a port of chromeIPass, which works out of the box on Quantum.
The two extensions are identical. The problem with both is, they cannot handle the two-step login with Google. What's worse, the keyboard shortcut that is supposed to help to load the username is conflicting with the "merge windows" command which in Quantum (who knows why) cannot be remapped. This seems like a tiny change (map the fill-in command to a different set of keystrokes) and yet neither mantainer of the two extension has bothered to correct it. It doesn't look good.