From owner-freebsd-questions Sun Mar 19 17: 6: 5 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id EEDB837B837 for ; Sun, 19 Mar 2000 17:06:02 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id TAA69531; Sun, 19 Mar 2000 19:05:48 -0600 (CST) (envelope-from dan) Date: Sun, 19 Mar 2000 19:05:48 -0600 From: Dan Nelson To: aunty Cc: freebsd-questions@FreeBSD.ORG Subject: Re: password echo with remote sudo Message-ID: <20000319190548.A66481@dan.emsphone.com> References: <20000320120041.A47022@comcen.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.5i In-Reply-To: <20000320120041.A47022@comcen.com.au>; from "aunty" on Mon Mar 20 12:00:41 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message