X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: encoding scripts (so that user can't see passwords easily)?
Date: Wed, 7 Dec 2005 16:24:13 -0500
Message-ID: <94BF3137C62D3E4CAED7E97F876585F0D0393E@pauex2ku08.agere.com>
From: "Williams, Gerald S \(Jerry\)" <gsw@agere.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jB7LOVS8018252

Ehud Karni wrote:
> [I think this discussion is off topic for cygwin]

Agreed, which is why I didn't elucidate earlier. If I
were inclined to do something like your second script
and override normal passphrase security, I'd probably
use another mechanism (maybe an environment variable?)
to avoid the passphrase appearing in the process list.
But as we both said, this discussion is really OT for
this list.

gsw


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/