make scp more script-capable

Alexander Kurz alexander.kurz at
Tue Jun 19 00:39:06 EST 2001

 here's a proposal of a new ssh/scp-feature:
 please implement a timeout with non-zero error-returncode on 
 "Are you sure you want to continue connecting (yes/no)?"

My situation:
 recently I have implemented a cronjob
 that is using scp. Due to organizational
 reasons, the hostname of the remote
 machine changed. The problem that came up
 at this point, is this the message came up:

akurz at dev157-34:~ > ssh someuser at
The authenticity of host 'someuser at' can't be
RSA key fingerprint is 00:12:4a:fc:33:80:71:70:4b:bb:e4:9d:16:c7:30:62.
Are you sure you want to continue connecting (yes/no)? 

BUT: i did not see the message, becaus i have
 discarded it via
 scp someuser at* . >/dev/null
 So the script hung whithout complaining.
 If there was some timeout-functionality,
 i could easily check scp's returncode and
 create a nice error-message

 regards, Alexander Kurz,   akur at

More information about the openssh-unix-dev mailing list