From: root@mauve.demon.co.uk
To: john@grabjohn.com (John Bradford)
Cc: davem@redhat.com, herbert@gondor.apana.org.au,
a.marsman@aYniK.com, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre7: are security issues solved?
Date: Wed, 23 Jul 2003 14:10:07 +0100 (BST) [thread overview]
Message-ID: <200307231310.OAA30193@mauve.demon.co.uk> (raw)
In-Reply-To: <200307231256.h6NCuEqX001509@81-2-122-30.bradfords.org.uk> from "John Bradford" at Jul 23, 2003 01:56:14 PM
>
> > > If I know your password is 7 characters I have a smaller
> > > space of passwords to search to just brute-force it.
> >
> > It's much smaller if you didn't know that it was at most 7 characters
> > long. However, if you did know the upper bound, or you were just
> > brute forcing all passwords starting from 1 character, then the
> > difference is relatively minor. This is because
<snip>
> One time passwords are much more secure.
Nope.
Changing password to a password of similar complexity every 10 seconds
doesn't make it much less likely to be guessed than a static password.
It may mean you can't guess it again, but you generally don't want
an attacker to even log in once.
One-time passwords, using a key generator may be better for other
reasons for example, more entropy than "31137" or other passwords that
users might pick, or be able to remember.
next prev parent reply other threads:[~2003-07-23 12:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 12:56 2.4.22-pre7: are security issues solved? John Bradford
2003-07-23 13:10 ` root [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 14:08 John Bradford
2003-07-23 15:46 ` Aschwin Marsman
2003-07-21 20:40 Aschwin Marsman
2003-07-22 7:04 ` Marc-Christian Petersen
2003-07-22 15:02 ` Aschwin Marsman
2003-07-22 15:07 ` Marc-Christian Petersen
2003-07-22 17:01 ` Marcelo Tosatti
2003-07-23 9:56 ` Herbert Xu
2003-07-23 10:35 ` David S. Miller
2003-07-23 10:39 ` Herbert Xu
2003-07-23 10:48 ` David S. Miller
2003-07-23 10:47 ` Herbert Xu
2003-07-23 10:50 ` David S. Miller
2003-07-23 10:59 ` Herbert Xu
2003-07-23 20:16 ` Aurelien Jarno
2003-07-23 20:23 ` Alan Cox
2003-07-23 17:47 ` David Wagner
2003-07-23 11:57 ` Ville Herva
2003-07-23 17:50 ` David Wagner
2003-07-24 9:11 ` Florian Weimer
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=200307231310.OAA30193@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--cc=a.marsman@aYniK.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
/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).