This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Still missing things from the old times
It's now quite some time I am forced to use the extension version of 1P.
Although you tried to implement a lot of the old functionality, there is still one thing I am desperately missing from the "old" approach.
In the extension version of 1P it is impossible to do anything without unlocking it. This was not the same before. I have 1P setup to lock itself after some time for security reasons. So this makes it really troublesome to do certain things the way I used to:
- entering a page where a pw is required, I used to click on the 1P icon and could see if a pw is stored for that page. Clicking that entry, the pw was autofilled and submitted. If 1P was still locked, the unlock window popped up and after entering that master-pw "autofill and submitting" was automatically applied. This is different in the extension version of 1P. Although it is only one click more, compared to the old approach, this is really starting to totally annoy me.
- it is not even possible to start the 1P app without having unlocked the extension. Come on....
And now with the new development of 1P becoming Lion only, this is even getting worth, as my machines won't get Lion on them till all my production tools become Lion ready. And this could take some time in the audio business, believe me.
Will SL users get updates till the "old" functionality is restored, or is this finally the good-bye kick in my back? Which would be really sad, as I have used your tool with great pleasure for almost 4 years now....
Although you tried to implement a lot of the old functionality, there is still one thing I am desperately missing from the "old" approach.
In the extension version of 1P it is impossible to do anything without unlocking it. This was not the same before. I have 1P setup to lock itself after some time for security reasons. So this makes it really troublesome to do certain things the way I used to:
- entering a page where a pw is required, I used to click on the 1P icon and could see if a pw is stored for that page. Clicking that entry, the pw was autofilled and submitted. If 1P was still locked, the unlock window popped up and after entering that master-pw "autofill and submitting" was automatically applied. This is different in the extension version of 1P. Although it is only one click more, compared to the old approach, this is really starting to totally annoy me.
- it is not even possible to start the 1P app without having unlocked the extension. Come on....
And now with the new development of 1P becoming Lion only, this is even getting worth, as my machines won't get Lion on them till all my production tools become Lion ready. And this could take some time in the audio business, believe me.
Will SL users get updates till the "old" functionality is restored, or is this finally the good-bye kick in my back? Which would be really sad, as I have used your tool with great pleasure for almost 4 years now....
Flag
0
Comments
-
Hi there,
The change to a "must enter master password first" was based on feedback from other customers. It was felt that it would be more secure to have it that way. In addition, in the future, the entire data file will be encrypted and it will be impossible for 1Password to access your data without the Master Password to do the decryption. At the end of the day, 1Password is a security tool. Yes, we need to find a balance between usability and security, but in this case we opted to go the route of higher security.
I'm happy to say we do have more updates planned for the 3.8.x line. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />
I understand your need to wait for other companies but hope you understand we can't hold off improvements to our product because of hardware/software creators in the audio realm being laggards. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/wink.png' class='bbc_emoticon' alt=';)' />Flag 0
