From owner-freebsd-current Thu Aug 3 4:26:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2CCE937B6FD for ; Thu, 3 Aug 2000 04:26:11 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA36582; Thu, 3 Aug 2000 13:26:02 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Loss of fetch(1) functionality with libfetch References: <00Aug3.142942est.115260@border.alcanet.com.au> From: Dag-Erling Smorgrav Date: 03 Aug 2000 13:26:01 +0200 In-Reply-To: Peter Jeremy's message of "Thu, 03 Aug 2000 14:28:44 +1000" Message-ID: Lines: 23 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: > Whilst the environment is somewhat safer than the command line, I'd > still prefer not to have passwords embedded in environment variables. Since ps(1) no longer allows users to view other users' processes' environment, I don't think it's a very big issue anymore. > Has this feature been deliberately left out, or is it just one of the > bits that you haven't gotten around to implementing yet? Would you > be interested in patches to implement it? Sure. The only clean way of doing this (that I can think of) would be to add an interface to libfetch for registering password-prompting callbacks. > On a related note, I noticed the following bug - though it has no > effect on the operation of libfetch in its current form. Correct, thanks. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message