1994-07-05 - Re: Password Difficulties

Header Data

From: “Perry E. Metzger” <perry@imsi.com>
To: cypherpunks@toad.com
Message Hash: ddb07d1e609b167f762cc5236c24fb7f5e0352b4b60d63512dc73e761e86e735
Message ID: <9407051331.AA19522@snark.imsi.com>
Reply To: <199407020841.AA23083@world.std.com>
UTC Datetime: 1994-07-05 17:27:03 UTC
Raw Date: Tue, 5 Jul 94 10:27:03 PDT

Raw message

From: "Perry E. Metzger" <perry@imsi.com>
Date: Tue, 5 Jul 94 10:27:03 PDT
To: cypherpunks@toad.com
Subject: Re: Password Difficulties
In-Reply-To: <199407020841.AA23083@world.std.com>
Message-ID: <9407051331.AA19522@snark.imsi.com>
MIME-Version: 1.0
Content-Type: text/plain



Kent Borg says:
> Besides, your sample phrase might not have as many bits in it as you
> think.
> 
> >Rare steak tastes good when it is cooked over a wood fire. better
> >chicken. better than fish. good with worcestershire sauce.
> 
> 22 words, a good start.  But all will appear in a short dictionary
> list, 4 gramatical sentences, sentences with related meaning.

Were I using a sentence like that, I'd probably spice it up with low
probability words and the like, as in

"rare olliphant meat tastes good when cooked over a burning car. better
than oktopuss. not as good as republican. tasty with wasabi and chives."

Still fewer bits than I'd like, but you do better when things take an
unexpected turn mid-phrase.

Perry





Thread