I'm using Key for Windows version 1.4.158 at work (same version at home and the latest android version on the go).
While everything works great between my home computer and my phone, I can't get my work station to synchronise. All my attempts fail immediately asking me to verify my network connectivity and the sync code.
And when I go to the "About" menu, I get a message saying "Server unreachable".
My browsers work fine though and I have no other network connectivity issue. I am behind a proxy though and there doesn't seem to be a way to define the proxy credentials in the application. Are there any plans to support this feature at some point in the future? I know several colleagues that have been considering getting this product but turned off by this exact reason.
Hello Mr FluffyTux,
Key should and does use proxy settings it derives from the system network settings. If they require typing in credentials, then we cannot react to that. You could try using internet explorer to browse, and inputting your credentials there to enable traffic through the proxy and after that trying to synch with Key. I would imagine that typing in credentials authenticates the whole computer, not just internet explorer to use the network.
Quote from QT docs "On Windows, this function will use the WinHTTP DLL functions. Despite its name, Microsoft suggests using it for all applications that require network connections, not just HTTP. This will respect the proxy settings set on the registry with the proxycfg.exe tool. If those settings are not found, this function will attempt to obtain Internet Explorer's settings and use them."
ps. let us know if you come up with a working method, I don't think supporting proxies that require authentication by credentials would be too high on our backlog.
Thanks for the replies and for checking up on me!
Unfortunately I haven't been able to make it work, I'm guessing you use a port that is blocked by my proxy...
I haven't had time to check though, but using IE instead of my usual browser before firing up the application didn't change a thing.
After a few months of syncing the passwords I need both at home and at work by hand, I've decided to have another look into this issue.
I've fired up WireShark to try and get some details about why it wouldn't go through and here are my findings.
I see the following requests:
- outbound: HTTP CONNECT avain.f-secure.com:443 HTTP/1.1
- inbound: HTTP HTTP/1.1 407 Proxy Authentication Required (text/html)
The details of the 407 are as follows:
HTTP/1.1 407 Proxy Authentication Required
Proxy-Authenticate: BASIC realm="AUTH_ADMIN"
Content-Type: text/html; charset=utf-8
According to the documentation regarding WinHTTP found on http://msdn.microsoft.com/en-us/library/windows/desktop/aa383144%28v=vs.85%29.aspx , I quote:
A typical WinHTTP application completes the following steps in order to handle authentication.
Thus, it is my undestanding that there should be a way for F-Secure KEY to handle this issue successfully.
I am looking forward to hearing back from you, even if it is to tell me that this will not (or cannot) be implemented.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link:
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support agents and get answers to your questions