This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Long delay when entering incorrect master password in extensions [RESOLVED in 1.0.9.293]
Hey guys,
It seems the design of the extension is a bit frustrating at first unlock after an extended period of inactivity. The extension sits on the main screen after typing in the master password and says 'Initialiazing', then 'Syncing... x', counting up to approximately 17s or so. Any chance you could fix this design? It's a pain to sit and wait for the extension to do its thing. Isn't there a way to init on Firefox startup?
It seems the design of the extension is a bit frustrating at first unlock after an extended period of inactivity. The extension sits on the main screen after typing in the master password and says 'Initialiazing', then 'Syncing... x', counting up to approximately 17s or so. Any chance you could fix this design? It's a pain to sit and wait for the extension to do its thing. Isn't there a way to init on Firefox startup?
Flag
0
Comments
-
I'll check next time.... It appears to say 'Incorrect Password' every time I see it happen, but it could just be that I can't type my master password every morning. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/tongue.png' class='bbc_emoticon' alt=':P' />Flag 0
-
Hm. Even if the agent is not running, it should not make any difference. Authentication for the extension happens within the extension. It sounds like you just didn't enter the correct master password. Are you abel to consistently reproduce the problem? Could you give me a list of the steps so I can try to duplicate it here?
Thanks in advance!Flag 0 -
The only steps I can work out are:[list=1]
[*]Leave computer running overnight.
[*]Open up browser.
[*]Try to unlock.
[*]Syncing for approximately 17s
[*]Master Password fail
[/list]
Restarting the browser (i.e. not waiting overnight) does not seem to make a difference...
Cheers,Flag 0 -
1Password manages a data exchange between itself and the browser extensions through “WebSockets”. This allows for Agile1pAgent.exe and the extension to communicate with each other while still respecting the sandboxing rules enforced by web browsers. Although these appear as network connections they are [b]limited to your local machine[/b] on IP address 127.0.0.1 (localhost). They neither accept nor provide information to any process not on the machine. These localhost connections are also [b]encrypted and authenticated[/b]. The ports used for these local machine connections are 6258, 10191, 14821, 24861, 25007, 38151, 46360, 49801, 55730 and 59483.
You can monitor the network traffic yourself if you are curious.
If you are still having trouble, could you please email us your Diagnostics Report? If you have an email client installed, you can send the report more easily by selecting [b]Help > Diagnostics Report > E-mail to Agile[/b]. If you don't have a desktop email client, you can select [b]Help > Diagnostics Report > Export to File[/b]. Then open your webmail, create a new message to support AT agilebits.com, and just upload the exported file as an attachment to that message.
Please include a link to this thread in your email message so that we can "connect the dots" when we see your message in our inbox.Flag 0 -
Khad,
I've been playing with it some more, and it looks like it's due to an incorrect master password entry. If I make sure I type it correctly, it works. Additionally, if I make a mistake, I can hit Escape to cancel the operation, and try again with the right password to unlock it almost immediately.
I believe there is still a bug when the password is wrong that takes approximately 17s (on my machine) to time out.
Cheers,Flag 0 -
Thanks for the additional info, kop48! I guess my fingers are so used to inputting my master password they can do it with their eyes closed. I am able to reproduce the issue (17s timeout when entering wrong MP). I'll update the info we have for this so we can resolve this in an update.Flag 0
-
That is expected and working as designed. It does actually take a moment to initialize and unlock (or determine that unlocking will not be possible). It is less noticeable when entering the correct master password since it actually unlocks. It's a psychological thing. It feels longer when it doesn't do what you wanted it to do at the end of the momentary pause. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />Flag 0