Date: Sun, 4 Dec 2005 12:36:46 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: encoding scripts (so that user can't see passwords easily)?
Message-ID: <20051204173646.GA28855@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <4392D119.7080409@wpkg.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4392D119.7080409@wpkg.org>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sun, Dec 04, 2005 at 12:20:57PM +0100, Tomasz Chmielewski wrote:
>I have a little open-source project, which eases Windows administration 
>a bit.
>
>In some of the scripts, I use usernames and passwords (to get to a 
>password-protected network share etc.).
>Because they are scripts, username and password is in plain.
>
>Although the script files are only readable by SYSTEM and 
>Administrators, if a disk is stolen, someone could easily get the 
>passwords by doing simple "grep -r password ./*".
>
>Do you know some tool which could "encode" scripts?
>
>One of such "similar" tools is Microsoft Script Encoder, but perhaps 
>it's licensing wouldn't allow me to distribute it along with my files.
>
>That's actually how I discovered Cygwin - I had to replace srvany.exe, 
>(which I couldn't distribute), and I found cygrunsrv :)

Just to be sure: you do realize that you can't distribute cygrunsrv
without also including the sources to cygrunsrv and cygwin1.dll
(assuming that you're including that file), right?  This is a GPL
project.
--
Christopher Faylor			spammer? ->	aaaspam@sourceware.org
Cygwin Co-Project Leader				aaaspam@duffek.com
TimeSys, Inc.

--
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/