From: Mike Johnson second login <exabyte!gedora!mikej2@uunet.uu.net>
To: gedora!uunet!asu.edu!Ben.Goren@uunet.uu.net
Message Hash: a2bbe26f9c93f27a2c2fc418d03a57bc1b795f50bd601e9684c3a145c6a84c85
Message ID: <Pine.3.89.9407131001.A11584-0100000@gedora>
Reply To: <aa489e5f0202101e958d@[129.219.97.131]>
UTC Datetime: 1994-07-13 16:50:14 UTC
Raw Date: Wed, 13 Jul 94 09:50:14 PDT
From: Mike Johnson second login <exabyte!gedora!mikej2@uunet.uu.net>
Date: Wed, 13 Jul 94 09:50:14 PDT
To: gedora!uunet!asu.edu!Ben.Goren@uunet.uu.net
Subject: Re: Security for under a buck fifty
In-Reply-To: <aa489e5f0202101e958d@[129.219.97.131]>
Message-ID: <Pine.3.89.9407131001.A11584-0100000@gedora>
MIME-Version: 1.0
Content-Type: text/plain
On Tue, 12 Jul 1994 uunet!asu.edu!Ben.Goren@gedora wrote:
> ...
> The tradeoff is between number of characters needed (length of passphrase)
> and diversity of character set. I'd probably have better luck with the
> mnemonic if I didn't have to fit in a whole string of %*$@!, but that
> should probably be a user setting.
Good point. I prefer the )*&^$!(~ stuff in there, but some may not.
> ...
> Another possibility: have a dictionary of different parts of speech and
> assemble them in order. For a short example, each passphrase could be in an
> order such as:
>
> Article adjective modifier noun verb article adjective modifier noun.
Good idea.
> Umph. I think I need to start making time to write code, if I want to see
> this work.
Go for it!
Return to July 1994
Return to “Mike Johnson second login <exabyte!gedora!mikej2@uunet.uu.net>”