1997-01-07 - Re: Double crypt strength

Header Data

From: Rick Osborne <osborne@gateway.grumman.com>
To: toto@sk.sympatico.ca
Message Hash: eec429a6c74912848fd55ed17f3136cf2da5984c8a61e7d47438a360754e6381
Message ID: <3.0.32.19970107090728.00a14310@gateway.grumman.com>
Reply To: N/A
UTC Datetime: 1997-01-07 14:08:33 UTC
Raw Date: Tue, 7 Jan 1997 06:08:33 -0800 (PST)

Raw message

From: Rick Osborne <osborne@gateway.grumman.com>
Date: Tue, 7 Jan 1997 06:08:33 -0800 (PST)
To: toto@sk.sympatico.ca
Subject: Re: Double crypt strength
Message-ID: <3.0.32.19970107090728.00a14310@gateway.grumman.com>
MIME-Version: 1.0
Content-Type: text/plain


At 04:33 PM 1/6/97 -0800, Toto wrote:
>  Pardon my ignorance, but I seem to be missing something here.
>  If you use an encryption as your password, do you not need to 'store'
>it somewhere in order to use it in the future (to 'pass' it to the
>decryption program)?

I was thinking something as simple as running crypt and then the next thing
you do is run passwd.  That way, the encrypted string will probably still
be right there on the screen (assuming your passwd util doesn't clear the
screen first).  Granted, it still means that you have to remember a
pseudo-random string, but the string is always one step away if you used a
logical password/phrase to generate it.

Sorry, I guess I wasn't too clear on that (fingers can't keep up with the
mind and all that...)

-Rick


Rick Osborne / osborne@gateway.grumman.com / Northrop Grumman Corporation
-------------------------------------------------------------------------
"And when exactly did all this happen?"
'When we rewrote the dictionary.' 






Thread