Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!uccba!uceng!ndcheg!iuvax!purdue!gatech!uflorida!rex!ukma!rutgers!cmcl2!adm!smoke!ibd!heilpern
From: heilpern@ibd.BRL.MIL (Mark A. Heilpern )
Newsgroups: comp.unix.wizards
Subject: Re: Password security - Another idea
Keywords: password security per-user password-modification
Message-ID: <240@ibd.BRL.MIL>
Date: 9 Jan 89 13:18:19 GMT
References: <228@sea375.UUCP> <4497@xenna.Encore.COM> <2271@pompeii.cs.swarthmore.edu> <4523@xenna.Encore.COM> <232@ibd.BRL.MIL> <669@brwa.inmos.co.uk>
Reply-To: heilpern@brl.arpa (Mark A. Heilpern (IBD) <heilpern>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 21

In article <669@brwa.inmos.co.uk> rob@inmos.co.uk (Robin Pickering) writes:
-->In article <232@ibd.BRL.MIL> heilpern@brl.arpa (Mark A. Heilpern (IBD) <heilpern>) writes:

-->>Suppose, among the standard dot files in the home directory, there was to be
-->>a new one: .case . The login program is to check this file,
-->
-->Why stop with case, why not specify a more general per-user password pre-
-->munging mechanism.  This seems quite an effective way to increase the
-->password search space to any party without access to the private munging
-->factor used.
-->
--> Rob Pickering

Rob, 
	You've won my approval!
			Mark

-- 
 |\/|         |
 |  |   _     |<
/    \_(_(_)\_/ \______