On Wed, 3 Jun 2009, Aaron Fellin wrote:
> jason wrote:
>> I am running into a problem with a ssh-add functionality in nevada b115. I
>> had a script that would do the following:
>> ssh-add ${HOME}/.ssh/*.[rd]sa
>> In previous versions of nevada, this would run fine, yet for b115, the order
>> of files found via the ${HOME}/.ssh/*.[rd]sa is not kept. This presents
>> problems when ssh connections are made to other servers since the keys I want
>> presented first, are not getting presented first. This is confirmed when
>> doing
>> an "ssh-add -l".
>> Is there a way to control the key order so that the keys I want to have tried
>> first, are used. I thought that the order in which I added keys, would
>> translate to the order in which those keys are presented to the remote
> server,
>> yet it looks like this ordering is not kept. Upon multiple tries of the
>> "ssh-add ${HOME}/.ssh/*.[rd]sa" the results seem to vary. I have to keep
>> trying until I get the "ssh-add -l" to display the order I need.
>
> You can use {} to enforce order:
>
> *{r,d}sa* will expand to rsa, then dsa; the other way around is left as an
> exercise to the reader.
I also think the change was in a shell, or in a shell change, or
in something else, but not in SunSSH. We haven't changed anything
regarding this area for the last (at least) few builds.
J.
--
Jan Pechanec
_______________________________________________
opensolaris-discuss mailing list
[email protected]
