From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre7: are security issues solved?
Date: Thu, 24 Jul 2003 11:11:34 +0200 [thread overview]
Message-ID: <87u19cffw9.fsf@deneb.enyo.de> (raw)
In-Reply-To: <20030723033505.145db6b8.davem@redhat.com> (David S. Miller's message of "Wed, 23 Jul 2003 03:35:05 -0700")
"David S. Miller" <davem@redhat.com> writes:
> If I know your password is 7 characters I have a smaller
> space of passwords to search to just brute-force it.
This is not the real problem, IMHO.
If the counter is public, you can read it repeatedly to measure the
intervals between keypresses. If you take pair-wise timing into
account, you can narrow the search space considerably.
There's a detailed paper about the issue:
<http://www.ece.cmu.edu/~dawnsong/papers/ssh-timing.pdf>
(Even if the title says SSH, it applies to the public counter scenario
as well.)
next prev parent reply other threads:[~2003-07-24 8:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 20:40 2.4.22-pre7: are security issues solved? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 12:56 John Bradford
2003-07-23 13:10 ` root
2003-07-23 14:08 John Bradford
2003-07-23 15:46 ` Aschwin Marsman
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=87u19cffw9.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.