X-Spam-Check-By: sourceware.org
Message-ID: <61f6f4390512061158o5a2ef71by6e1a419c8e6499b3@mail.gmail.com>
Date: Tue, 6 Dec 2005 14:58:15 -0500
From: Jim Drash <jim DOT drash AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: encoding scripts (so that user can't see passwords easily)?
In-Reply-To: <4395E827.4070804@wpkg.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <4392D119 DOT 7080409 AT wpkg DOT org> 	 <20051204173646 DOT GA28855 AT trixie DOT casa DOT cgf DOT cx> 	 <deca9ec80512042242h44317cexf2878291acddcc8a AT mail DOT gmail DOT com> 	 <7ff9c2a10512060949l72e9693bv251e0d46c36ea0e0 AT mail DOT gmail DOT com> 	 <4395E827 DOT 4070804 AT wpkg DOT org>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jB6JwN2V003006

Don't put the user names or passwords in the script put them in a file
only readable by SYSTEM


On 12/6/05, Tomasz Chmielewski <mangoo AT wpkg DOT org> wrote:
> Svend Sorensen schrieb:
> > On 12/4/05, nidhog <nidhog AT gmail DOT com> wrote:
> >
> >>On 12/4/05, Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com> wrote:
> >>
> >>>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?
> >>
> >>instead of storing them plaintext, why don't you try encoding them via
> >>cryptographic hashes - md5, sha1, tiger and the like.
> >
> >
> > How is the script going to get the plaintext password if all it has is
> > a one way hash?
>
> I don't really care, perhaps it won't be any one way hash anyway.
>
> It is to be a measure to prevent an accidental viewing of
> usernames/passwords rather than some "military grade" tool which takes
> 100 years to break on a supercomputer.
>
>
> --
> Tomek
> http://wpkg.org
> WPKG - software deployment and upgrades with Samba
>
> --
> 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/
>
>

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