<div class="moz-text-flowed" style="font-family: -moz-fixed">H. Willstrand wrote: > On Sat, Jan 9, 2010 at 2:32 AM, Bill Davidsen <davidsen@xxxxxxx> wrote: >> I am using the "command=" feature heavily as part of a backup system, which >> allows me to run commands on a remote server without allowing general >> function. I give the public key for a functionality to the server, add to >> authorized_keys, and can closely control the users. The key is chosen by use >> of the "-i" option to ssh. >> >> All of this has been working nicely for several years. >> >> However, it seems that ssh offers the default key *first* to the server, >> rather than the one specified on the command line. That's so bizarre I spent >> time checking that it really happened before asking here. >> >> So the question is, how can I get ssh to offer the key I give it in the >> command line first? Preferably as the only key offered, actually, but >> definitely before the default key, which on several machines drops me into >> another application. >> >> Is there some clever means or option I missed? >> > > Have you tried the -F option instead? > No, if I saw a config option to use the key the command line provides first I would put it in the system config file. Is there an option I missed? Having an option file for each key would seem a roundabout way to do things. Or have I missed your point? The issue is that I need different keys depending on what I'm doing, and the man page seems to say that the -i key will be used instead of the default, which is just what I need. Enlightenment invited? ;-) -- Bill Davidsen <davidsen@xxxxxxx> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot </div> -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
