| delorie.com/archives/browse.cgi | search |
| From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
| To: | <djgpp-workers AT delorie DOT com> |
| Subject: | Re: Status update (Smalltalk/Python) |
| Date: | Sun, 21 Jan 2001 14:10:40 +0100 |
| Message-ID: | <NEBBIOJNGMKPNOBKHCGHEEOBCAAA.tim.van.holder@pandora.be> |
| MIME-Version: | 1.0 |
| X-Priority: | 3 (Normal) |
| X-MSMail-Priority: | Normal |
| X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
| In-Reply-To: | <Pine.SUN.3.91.1010121144545.16311C-100000@is> |
| Importance: | Normal |
| X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
| X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id IAA26598 |
| 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 |
> 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? And what would be a good value? Maybe we could select one randomly from "secret", "password" and "god" :-) I'm open to suggestions...
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |