-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] still under development? #3
Comments
Yes, this is still under development. The main issues with the proxies are:
There's actually no open issues with the fork but I would like to make it compatible with multiple proxies. Now you can use only one at a time. The extension is always under development but it's already stable so it's safe to use. |
A new C++ version is now online. |
Thanks for the C++ version! Gonna try that aswell :) |
The only thing still missing from the C++ version is the timeout operation. So currently it's not perfect, but it will be :) So don't get furious if the popup gets stuck to the checking phase.. this only happens if KeePassXC is closed and no state can be received. This wil be fixed soon. |
The timeout operation is no longer needed (the browser extension handles the timeouts) so the proxy implementation is lot more simpler. I have already a working copy with the same proxy and KeePassXC with Unix Domain sockets. It is possible that these replace the plain UDP socket under Linux/Unix/macOS. |
That'll be great. Currently FF needs some time to kill the proxy and shuts itself down after ~3 seconds. |
Yes, I'm aware of those issues also. Sometimes the proxy process is not killed at all. Of course it doesn't take any CPU or anything but it's annoying at should not happen. |
Mhm...never happened to me though. Proxy is always killed for me. |
a refreshg question: |
@Cherkah I haven't had the time to update this repo for a while. |
Same question goes for the FF extension and the fork aswell.
The text was updated successfully, but these errors were encountered: