Loading Profile...
multiple public-key identities
For ssh public-key authentication I have multiple identity files defined in ~/.ssh/config and that allows other apps like Terminal.app ssh login and Transmit to successfully connect using my second identity file. I recently started using Meerkat to setup ssh tunnel when Colloquy launches, and with an account that uses non-default Identity the Meerkat account must be configured with the location of the id_rsa private key.
Although other apps work with alternate ssh Identities, ExpanDrive fails after two authentication attempts as if it is ignoring my ~/.ssh/config file.
Yes I left the password blank and yes ExpanDrive works fine connecting to ssh servers that rely on my primary ssh Identity. The problem only happens with ssh sessions that use alternate private/public key pairs that are defined in my ~/.ssh/config file.
Although other apps work with alternate ssh Identities, ExpanDrive fails after two authentication attempts as if it is ignoring my ~/.ssh/config file.
Yes I left the password blank and yes ExpanDrive works fine connecting to ssh servers that rely on my primary ssh Identity. The problem only happens with ssh sessions that use alternate private/public key pairs that are defined in my ~/.ssh/config file.
I’m frustrated
4
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?HI Brian. ExpanDrive does not use OpenSSH, and so not all .ssh/config options are currently supported. Can you describe a little more explicitly what your set up is, and the behavior you’d like to see in ExpanDrive?
-
Inappropriate?Jon, today I can use sshfs to mount any remote filesystem accessible via ssh/sftp. I have several identities, each identity has a unique private/public key pair. There is a set of identities that are defined in ~/.ssh/config and they tried in order for any app the uses OS X ssh app. In addition I can specify an identity directly on the command-line when using the bundled ssh:
ssh -i ~/.ssh/brian/client1/id_rsa
All my current apps -- Terminal/OpenSSH, Transmit, MacFuse/SSHFS, Meerkat, etc. -- are capable of using alternative identities. Terminal, Transmit and Meerkat all use /usr/bin/ssh and the first two respect ~/.ssh/config and require no special tweaking to connect a session. Meerkat requires specifying the private key location such that it issues the proper "-i filepath" command-line option to ssh (although it doesn't need to and I've notified the developer). From running "ps ax" it appears that sshfs uses its own "sshfs-static-10.5" app to initiate the ssh session and I'm guessing that app is just a recompiled OpenSSH or equivalent because I can mount drives of remote filesystems that use alternate identities defined in ~/.ssh/config.
In summary I'm asking that ExpanDrive behave like other ssh/sftp client and support multiple identities. Currently ExpanDrive understands a primary identity that is defined in ~/.ssh but it does not support alternate identities specified either in i) (ok) ExpanDrive config, or ii) (better) in the user's ~/.ssh/config.
Really you don't need my explanation, from Mac OS X type "man ssh_config" and review description and then search for IdentityFile keyword for details how users can setup and seamlessly use multiple public key identities.
Obviously this is a complete show-stopper and I'll continue using sshfs. -
EMPLOYEE
