keepasshttp
keepasshttp copied to clipboard
pfn
This project are dead ?
Hi Perry,
This project are very cool plugin for keepass, but, no activity from 2017, many issue pending, many pull request pending ! You need help to maintain ? I think many people her while be ok to aid you to maintain !
there are forks that are more recent.. but not many also put the actual compiled file :(
i've seen effectivly different patch with pr... but no inclusion... why i'm intergogate about project freeze... if perry not abel to maintain while be interesting to transfert the maintenance to any person that can continue to maintaine... or make a fork, generaly is preferable to transfert the maintenance to group of people...
I think it is safe to say this repo is dead. Keepass2 itself seems to be on life support - even though KeePassXC does not cover all features.
Happy to help!
@mcarbonneaux
if perry not abel to maintain while be interesting to transfert the maintenance to any person
Given that perry doesn't go MIA (still contributing to other projects occasionally), I see it an indicator that perry actually wants others to actively migrate to other solutions instead of sticking to keepasshttp. I have described some possible migration paths here, and there could be other ways I haven't covered as well.
@baradhili
Keepass2 itself seems to be on life support
Nah, KeePass2 is still the pioneer in this area, implementing new crypto algo and stuff, and its plugin ecosystem isn't surpassable for now. KeePassXC is playing the catch up game, though in terms of UX and other basic integration it became superior.
@abelcheung keepasshttp is a good product is why i aswered if the project is dead !
i've not seen KeePassNatMsg ! is very interesting solution ! the usage of Native Messaging is very interesting, but there no risk of suppresion of the native messaging ?
Because chrome are removing the chrome apps that are related to...
https://developer.chrome.com/docs/apps/nativeMessaging/
Is not very clear that native messaging while be removed for extension to....
Nope, Google only retires Chrome Apps. KeePassXC-Browser is an extension and won't be affected.
is there any good replacement except these forks?
KeePassXC browser - chrome / firefox browser plugin is working fine with original keepass and replace perfectly keepasshttp!
in fact is beter solution because he use native messaging and is more normalised way of communicating between the os and the browser.
KeePassXC browser plugin are browser plugin and is bad named in fact (is developped by the keepassxc fork team is why is named like that)... ok is quiet confusing but in fact is more Keepass NatMessaging browser plugin.... in fact is not specific to XC version...
in fact it's work with original keepass thank to KeePassNatMsg plugin ... that implement the way of communicating between KeepassXC Browser and KeepassXC but with original keepass...
is there any good replacement except these forks?
KeePassXC browser - chrome / firefox browser plugin is working fine with original keepass and replace perfectly keepasshttp!
in fact is beter solution because he use native messaging and is more normalised way of communicating between the os and the browser.
KeePassXC browser plugin are browser plugin and is bad named in fact (is developped by the keepassxc fork team is why is named like that)... ok is quiet confusing but in fact is more Keepass NatMessaging browser plugin.... in fact is not specific to XC version...
in fact it's work with original keepass thank to KeePassNatMsg plugin ... that implement the way of communicating between KeepassXC Browser and KeepassXC but with original keepass...
Thanks for suggesting the new replacement plugin, I try to use it at home without any problem, but when I try to use them in office, AD group policy block the KeePassNatMsg-proxy.exe running from appdata folder, so I need to either asking for modify group policy to give exception or discuss with owner of KeePassNatMsg to download the proxy program to Keepass plugin folder.
@mcarbonneaux, I followed your instructions and found that KeepassHTTP and KeepassNatmsg plugins are similar only in appearance, while the latter deprives Keepass of portability by polluting the Windows registry and planting the file keepassnatmsg-proxy.exe to the current user's profile. This is not good at all.
I expressed my concerns to the developer.
i think the registry key you speak about are related to how browser launche native messaging process... i'm not sure that can be done without... https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging
seem somme other are talking about that on keepassxc : https://github.com/keepassxreboot/keepassxc/issues/1817
seem to be related on how the browser register there native plugin... on portable version...
@mcarbonneaux, after 2 weeks of intensive testing of 3 ways to enter credentials via KeepassHTTP, KeepassRPC and KeepassNatMsg, I ditched them in favor of the native Auto-Type via a keyboard shortcut enhanced by WebAutoType. Phew, what a relief!
@mcarbonneaux, after 2 weeks of intensive testing of 3 ways to enter credentials via KeepassHTTP, KeepassRPC and KeepassNatMsg, I ditched them in favor of the native Auto-Type via a keyboard shortcut enhanced by WebAutoType. Phew, what a relief!
it is great you tested all those projects. webautotype is good to hear about because i wondered why only titles, but not URLs worked. However, it is not nearly as secure as keeform and the others you tested because autoType transfers passwords using the clipboard, so other apps that read the clipboard could pull down passwords. The others use direct methods that other processes would have difficulty intercepting.
However, it is not nearly as secure as keeform and the others you tested because autoType transfers passwords using the clipboard
It's secure enough when Two-Channel Auto-Type Obfuscation is activated.