From owner-freebsd-questions Sun Mar 19 18:14:17 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sblake.comcen.com.au (sblake.comcen.com.au [203.23.236.144]) by hub.freebsd.org (Postfix) with ESMTP id 96EBF37B7FB for ; Sun, 19 Mar 2000 18:14:11 -0800 (PST) (envelope-from aunty@sblake.comcen.com.au) Received: (from aunty@localhost) by sblake.comcen.com.au (8.9.3/8.9.3) id NAA47655; Mon, 20 Mar 2000 13:18:04 +1100 (EST) (envelope-from aunty) Date: Mon, 20 Mar 2000 13:18:04 +1100 From: aunty To: Dan Nelson Cc: freebsd-questions@FreeBSD.ORG Subject: Re: password echo with remote sudo Message-ID: <20000320131804.B47022@comcen.com.au> References: <20000320120041.A47022@comcen.com.au> <20000319190548.A66481@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000319190548.A66481@dan.emsphone.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 19, 2000 at 07:05:48PM -0600, Dan Nelson wrote: > In the last episode (Mar 20), aunty said: > > > > We're trying to use a script which runs a sudo command on a remote > > linux box via ssh, and the sudo password keeps echoing to the screen > > even though the ssh password does not. > > Add a -t to the ssh commandline. When ssh is run with a command > argument, it does not allocate a pty on the remote end (on the > assumption that you're running this from a cron script and don't want > to waste a pty). No pty means no echoing; in fact, your local terminal > is echoing your characters at this point. Spot on, it works like a beauty now, thanks much! -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message