Skip to content
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

Open
snwflake opened this issue Sep 25, 2017 · 10 comments
Open

[Question] still under development? #3

snwflake opened this issue Sep 25, 2017 · 10 comments

Comments

@snwflake
Copy link

Same question goes for the FF extension and the fork aswell.

@snwflake snwflake changed the title still under development? [Question] still under development? Sep 25, 2017
@varjolintu
Copy link
Owner

Yes, this is still under development. The main issues with the proxies are:

  1. Rust version and Firefox don't get along, I don't know why
  2. Python version cannot be hidden from the Dock with macOS

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.

@varjolintu
Copy link
Owner

A new C++ version is now online.

@snwflake
Copy link
Author

Thanks for the C++ version! Gonna try that aswell :)

@varjolintu
Copy link
Owner

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.

@varjolintu
Copy link
Owner

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.

@snwflake
Copy link
Author

That'll be great. Currently FF needs some time to kill the proxy and shuts itself down after ~3 seconds.

@varjolintu
Copy link
Owner

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.

@snwflake
Copy link
Author

Mhm...never happened to me though. Proxy is always killed for me.

@Cherkah
Copy link

Cherkah commented Apr 13, 2019

a refreshg question:
still under development?
thx

@varjolintu
Copy link
Owner

@Cherkah I haven't had the time to update this repo for a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants