Date: Sun, 21 Jan 2001 15:12:19 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Status update (Smalltalk/Python)
In-Reply-To: <NEBBIOJNGMKPNOBKHCGHEEOBCAAA.tim.van.holder@pandora.be>
Message-ID: <Pine.SUN.3.91.1010121151028.16311H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 21 Jan 2001, Tim Van Holder wrote:

> > I wonder: isn't this dangerous?  Won't we get problems with some 
> > over-zealous programs that might not like empty passwords?
> > 
> > (Also, a non-empty password might be less dull ;-)
> Wasn't sure what to use for a value though; would apps expect
> crypt()'ed values or plaintext?

Could people who can access Unix and GNU/Linux boxes please look what 
they do?

> And what would be a good value? Maybe we could select one randomly
> from "secret", "password" and "god" :-)
> I'm open to suggestions...

I suggest to start a contest for the best password.

Let me begin with a suggestion:

	"Don't panic!"

(That should go well with the UID and GID or 42.)