The part that I need now that i'm dependent on 1Password is the dropbox-based syncronization. In other words, it would be easier to just type `ssh ` than opening 1Password to find the entry.
Part of me thinks SSH has already solved this issue by using keys to avoid passwords. Part of me wants to have an SSH Account item that will open Terminal when clicked and run the appropriate command, but I'm not sure how useful this would be. While this would work, 1Password was not designed to be the best Application Launcher and I think you can find better You would then rely on the OS X Keychain to login. The alternative could be allowing Transmit to store the passwords in the OS X Keychain, which works well, and then have 1P simply launches Transmit for you. 1Password could open Transmit when you click the item, but then what? Do we need to write a Transmit Extension to fill your password? That would be a huge development effort to support all applications!
Where I get stuck is what do we do after we open the appropriate application? For example, let's say my FTP client is Transmit. We could add this to the Accounts section, however, so this is not a show stopper. We always thought of Logins as "Web Logins" and I'd like to keep it that way. This could be a great idea but I'm not exactly sure how it would work. filling in the correct fields in the URI with the appropriate user and password info.
#INTERARCHY APP MAC OS X#
It would be nice if 1P respected the service part of the URI and used the correct Mac OS X lookup to find the correct application (like Terminal for Telnet, and Interarchy for FTP). In particular, I have a number of Unix accounts that I use with Telnet and/or SSH, plus the innumerable FTP and SFTP servers. Now that I'm completely and thoroughly dependent on 1P, I'd like to use it to store *other* passwords that I need on a daily (hourly) basis.
0 kommentar(er)
