9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] offered without comment or judgement
Date: Tue, 29 Jun 2010 14:41:21 -0400	[thread overview]
Message-ID: <AANLkTimBvFiV09MQcUpKRZoExcHcVPUn1oFngEHXOnRv@mail.gmail.com> (raw)
In-Reply-To: <f1af614af35a2f189337e2c876ab9353@quintile.net>

2010/6/29 Steve Simon <steve@quintile.net>:
>> But you can do at least as good as these forms of ID. PKI requires
>> knowledge of some sort of passkey. (I just worry about identification
>> for people who are not smart enough to pick a good key. Which,
>> unfortunately, is also most people.
>
> My understanding is a passkey just needs sufficent entropy in order to be strong.

Sure. But you can still brute-force a 4-character passkey in a
reasonably short time.

> This can be a few characters drawn from a larger characterset - your password must
> be no more than 16 chars and must contain upper and lower case numbers and punctuation.
>
> Alternatively it could be a long string made up of a restricted character set - your
> pass phrase can consist of any text characters but must not contain long repitations
> and be of at least 200 characters long (say).

This works, but tends to be easy to get out of people or figure out
about people if you know a bit about them.

> Thus a passphrase may be a quote from your favorite movie, a lyric or the like. This
> can then be hashed into a higher entropy string (is this statement true?) used for
> authentication.
>
> I don't understand why modern security systems have an upper limit on passphrase length.

Because people can't remember passwords, and companies don't like
employing full-time password changers.

--dho

> (waits for people who know better to tell him he is dumb).
>
> -Steve
>
>



  reply	other threads:[~2010-06-29 18:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 22:32 ron minnich
2010-06-28 23:10 ` Ethan Grammatikidis
2010-06-29  2:28 ` Wes Kussmaul
2010-06-29  2:46   ` Stanley Lieber
2010-06-29 17:13     ` Wes Kussmaul
2010-06-29 17:27       ` Devon H. O'Dell
2010-06-29 18:30         ` Steve Simon
2010-06-29 18:41           ` Devon H. O'Dell [this message]
2010-06-29 18:57             ` erik quanstrom
2010-06-29 19:13               ` Devon H. O'Dell
2010-06-29 19:32                 ` erik quanstrom
2010-06-29 20:00                   ` Devon H. O'Dell
2010-06-30 11:28                     ` erik quanstrom
2010-06-30 15:22                       ` Wes Kussmaul
2010-06-30 16:22                       ` Devon H. O'Dell
2010-06-29 20:09                 ` Wes Kussmaul
2010-06-29 21:34                   ` Steve Simon
2010-06-29 19:19         ` Wes Kussmaul
2010-06-29  3:46   ` erik quanstrom
2010-06-29  8:07 ` Akshat Kumar
2010-06-29  9:14   ` hiro
2010-06-29  9:17     ` erik quanstrom
2010-06-29 19:59     ` ron minnich
2010-06-29 13:43 ` Gabriel Díaz
2010-06-29 16:54   ` hiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimBvFiV09MQcUpKRZoExcHcVPUn1oFngEHXOnRv@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).