Just a shout out from the peanut gallery: Most of the use cases for ssh I have are not interactive, but there may be cases where being able to interact a la telnet would be useful. From my point of view, ssh is a tool used more like rsh/rexec than telnet, and I'd like to see that simplicity preserved. Not needing the authentication of user/password is a big part of the driver away from needing interactivity.
s -----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: Friday, February 21, 2003 8:51 AM To: [EMAIL PROTECTED] Subject: Re: SSH Tasks On Fri, 21 Feb 2003, Rob H. Anderson <[EMAIL PROTECTED]> wrote: > Can there be some flag that specifies interactivity? If there is a reason for it, sure. > <!-- Non-interactive --> > <ssh host="myhost" username="myname" password="mypass" > interactive="false" > command="cd /usr/local/bin ; rm -rf product ; tar zxf product.tar.gz" > /> Would this (implementation-wise) be different from <ssh host="myhost" username="myname" password="mypass"> <write>cd /usr/local/bin ; rm -rf product ; tar zxf product.tar.gz</write> </ssh> ? Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
