If you are using ssh 2.x you might want to look at BatchMode option:
ssh -o BatchMode yes user@host 'command'
this is assuming you are using public keys and not passwords in your scripts.
also if you have strick hostkey checking on then the default answer to new
hostkeys will be no.
You could put this in ~/.ssh2/ssh2_config also.
Previously, Barden, Tino wrote:
> I know that I can not be sure about the identity of the server, but anyway I
> have to do it in this way.
> The 'StrictHostKeyChecking' Flag is set to no, so the hostkey will be
> received without asking for a confirmation. This works fine when I'm logged
> in on the server, but my problem is when I'm not logged in (via cgi-script).
> Then I have no controlling tty and the ssh-command fails.
>
> regards
> Tino
>
> -----Ursprüngliche Nachricht-----
> Von: Markus Friedl [mailto:[EMAIL PROTECTED]]
> Gesendet am: Dienstag, 20. Februar 2001 15:33
> An: Barden, Tino
> Cc: [EMAIL PROTECTED]
> Betreff: Re: tty problem
>
>
> if you don't know the hostkey in advance, and if you don't
> verify the fingerprint then you cannot be sure about
> the identity of the server.
>
> however, several SSH protocol implementations support
> the 'StrictHostKeyChecking' keyword (e.g. SSH-1.2.x
> or OpenSSH).
--
Jesse Nelson X U M A <build-to-order e-business> X .~.
Senior 160 Pine Street, 2nd Floor U /V\
Engineer San Francisco, CA 94111 M // \\
tel: 415.777.9988 I /( )\
http://www.xuma.com X ^`~'^
PGP Key fingerprint = 9DE9 4C9F 014D F68E 893D 097E 079D 5FF3 9614 3E86
One can search the brain with a microscope and not find the
mind, and can search the stars with a telescope and not find God.
-- J. Gustav White
