at https://github.com/keepassxreboot/keepassxc/blob/develop/README.md
KeePassHTTP support for use with PassIFox in Mozilla Firefox, chromeIPass in Google Chrome or Chromium and passafari in Safari.
its better for firefox user.
github
releases
I don't understand what you are asking for
I'm guessing ydf is suggesting that the KeePassXC README recommend that Firefox users use keepasshttp-connector rather than (or in addition to) PassIFox.
From the current KeePassXC README:
KeePassHTTP support for use with PassIFox in Mozilla Firefox, chromeIPass in Google Chrome or Chromium and passafari in Safari.
I don't know much about keepasshttp-connector so I can't say whether this a good idea. I'm just attempting to clarify the issue/ request.
I think he mean to replace PassIFox/ChromeIPass in our website in favor of the new maintained fork KeePassHTTP Connector.
This can be a good idea since the first aren't maintained actively anymore, but the latter isn't available in any store (Firefox/Chrome) so I don't feel to make any changes to the website
And note that we are working on our custom plugin KeePassXC-browser
The plugin is now available at AMO and Chrome Web Store.
Do we plan to keep HTTP support? @droidmonkey
Yes there should be a deprecation period before we shut it down completely.
This is fixed in the website now https://keepassxc.org/project
Fixed also in the readme (will be visible after the 2.2.2 upmerge)
Currently KeePassHTTP-Connector is offline from Mozilla addon store. https://github.com/smorks/keepasshttp-connector/issues/34
Consider using Keywi
KeePassHTTP-Connector is back on AMO : https://addons.mozilla.org/fr/firefox/addon/keepasshttp-connector/
Nice!
Most helpful comment
The plugin is now available at AMO and Chrome Web Store.