ssh key autologin fails

[netvipe]

We're using ciscocmd in combination with ssh-key based autologin.
It turns out that ciscocmd fails to detect the next valid line if ssh key authentication in combination with a predefined ssh username is being used.

We have therefore enhanced ciscocmd to detect a possible prompt even before the first waitprompt call.

Modifications are as follows:

--- /data/shared/install/ciscocmd
+++ /usr/local/bin/ciscocmd
@@ -496,7 +496,7 @@
        }


-       catch { expect -re  "(assword)|(ser(name)?)|(yes/no)" }
+       catch { expect -re  "(assword)|(ser(name)?)|(yes/no)|(> *$)" }
         if { [ catch { set loginbuf "$expect_out(0,string)" } ] } {
         #       if { [ catch { set loginbuf "$expect_out(2,string)" } ] } {
        #               set loginbuf "$expect_out(3,string)"
@@ -532,6 +532,9 @@
                                varcheck "password" 1
                                send  "$password\r"
                                }
+               "> "            {
+                               varcheck "password" 0
+                               }
                default         {
                                exit
                                }

Maybe you would like to included that for the official version.

[alvarezp]

Interesting case. I guess a user could also be directly dropped in to enable level 15, so the prompt could also end in a hash sign (#) instead of a greater-than sign (>).

[alvarezp]

Additionally, what happens with your solution if the host is not added to the host key list and thus you get the following prompt?

RSA key fingerprint is 00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff.
Are you sure you want to continue connecting (yes/no)?

[netvipe]

You are right. I've added the hash sign to the pattern def. It just makes sense.
The "yes/no" handling is still covered since the "fix" only takes care of connections that are auto connected due to specific ssh policies. The original features are still working as intended.

[tpo]

@netvipe - would be nice if you could fork ciscocmd-cosi and publish your tree, so others could pull from it.