Para usar estas extensões, você precisa instalar o Firefox.

Entrar
Ícone da extensão

Análises de KeePassXC-Browser

KeePassXC-Browser por KeePassXC Team

4,3 de 5 estrelas
5
509
4
92
3
43
2
22
1
73
Análise de Cangrejo
por Cangrejo, há 2 meses
Best password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored.
739 análises
  • por Usuário 18863959 do Firefox, há 10 horas
  • por Usuário 14868755 do Firefox, há 2 dias
    Not able to add connected database. Nothing happens when clicking the Connect Database button. Bazzite 43 (linux) NVIDIA edition, Firefox 149, KeePassXC 2.7.12
  • por Saturnus, há 10 dias
  • por Fokeu, há 20 dias
  • por Usuário 13156335 do Firefox, há 21 dias
    Works fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
  • por elsenfox, há 2 meses
  • por Usuário 19733088 do Firefox, há 2 meses
    Eigentlich gut, aber umständlich, funktioniert bei vielen Websites einfach mal gar nicht, das Felderkennungs-Tool zum Zuweisen ebenfalls nicht und kostet daher viel Zeit und Nerven in der Benutzung. Daher kann ich ebenso schnell und gut aus KeepassXC kopieren und einfügen und brauche mich nicht mit diesem AddOn herumschlagen; leider!
  • por John Hills, há 2 meses
    The addon randomly shows errors like "KeePassXC-Browser has encountered an error: Key exchange was not successful" which means absolutely nothing to the user and does not help solve the problem in any way. It is the same as showing a message "Error: There has been an error. You're unlucky, too bad for you."

    Resposta do desenvolvedor

    publicado há 2 meses
    GitHub already has an issue about this. In short, there's no way to get details from the API why the key exchange / connection fails. I suggest you take a look at the most common error threads and our Troubleshooting Guide at GitHub.
  • por Lani, há 3 meses
    It seems that the path for native-messaging-hosts is hardcoded.
    I want to move the file located at [~/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json] to [xdg-directory :: ~/.config/mozilla], but it fails.
    help me?
  • por Ethan, há 3 meses
    it doesn't work when the password is on another page after the email. it always puts the wrong password from another account without even asking which account. developers, add a dropdown to ask the user from which account to take the password, don't just put any random password from any random account in the database. changing any setting didn't fix this.

    Resposta do desenvolvedor

    publicado há 3 meses
    First of all, this shouldn't happen. There's already a dropdown selector when filling usernames or password from multiple accounts. Selector from the popup works as well. There are some settings that try to fill the password automatically for the selected username. Disabling those should help. If not, please file an issue to GitHub, thanks.
  • por A1, há 3 meses
  • por ProgramminCat, há 3 meses
  • por Xol, há 3 meses
  • por Usuário 16478816 do Firefox, há 3 meses
  • por Ryan Steed, há 4 meses
  • por Usuário 19642928 do Firefox, há 4 meses
  • por Enunciate_Veggie, há 4 meses
  • por collar_PL, há 4 meses
    Great plugin. Makes work much easier.
  • por Usuário 13447327 do Firefox, há 4 meses
  • por vihrom, há 4 meses
    very good brother
  • por SJoarder, há 4 meses
    : )
  • por Thrillhouse, há 4 meses
  • por Helkin, há 5 meses
    Great extension, love this on my Fedora 43 computer.

    I would have love to have this work on Bazitte with it’s firefox in a flatpak
  • por FartPie, há 5 meses
    Currently completely broken with more restrictive privacy configurations due to a bug (#2672) that was reported over two months ago and patched over a month ago - and still not released.

    I would have thought show stopping bugs would be worth a point release, but apparently not.

    Resposta do desenvolvedor

    publicado há 5 meses
    Dear FartPie (love the nick btw), we've been collecting a bunch of various fixes and new features for the release, and it will be published soon. The bug you mentioned was not really high-priority, and not affecting many people so it didn't require a separate hotfix release.