public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Lloyd <lloyd@randombit.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mlock(1)
Date: Mon, 4 Oct 2004 08:21:20 -0400	[thread overview]
Message-ID: <20041004122120.GG664@acm.jhu.edu> (raw)
In-Reply-To: <20040930174244.GL22008@dualathlon.random>

On Thu, Sep 30, 2004 at 07:42:44PM +0200, Andrea Arcangeli wrote:
> > 
> > Actually, better solution probably is to encrypt 32-bit zero.
> > 
> > Then, you have 1:2^32 probability of accepting wrong password, still
> > if you try to brute-force it, you'll find many possible passwords.
> 
> this is just the first step an attacker needs to rule out all the
> impossible passwords and extend the crack to the other known bits. I
> don't think it's secure. My suggestion OTOH sounds completely secure
> (though much harder to implement).

PGP actually uses a similiar techinique (80 bits of randomness, with bytes 9+10
being repeats of 7+8) to check for bad decrypts. With 16 bits of checksum, the
attacker only is able to eliminate about (2^16-1)/2^16 of the keys, which seems
like a lot, but only reduces the keylength by 16 bits. If you're using
reasonably sized keys (>=128 bits) that's not a problem because the remaining
keyspace is still much larger than the set of likely passphrases (even quite
good passphrases rarely get over 80 or 90 bits of entropy).

-Jack

  parent reply	other threads:[~2004-10-04 12:21 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 19:57 mlock(1) Jeff Garzik
2004-09-24 20:15 ` mlock(1) Neil Horman
2004-09-24 20:21   ` mlock(1) Neil Horman
2004-09-24 20:31   ` mlock(1) Lee Revell
2004-09-24 20:33     ` mlock(1) Jeff Garzik
2004-09-24 20:39       ` mlock(1) Lee Revell
2004-09-24 20:22 ` mlock(1) Chris Wright
2004-09-24 20:41   ` mlock(1) Chris Friesen
2004-09-24 20:46     ` mlock(1) Chris Wright
2004-09-24 20:54       ` mlock(1) Chris Friesen
2004-09-24 20:59         ` mlock(1) Chris Wright
2004-09-24 22:48     ` mlock(1) Ryan Cumming
2004-09-24 21:07   ` mlock(1) Alan Cox
2004-09-24 22:19     ` mlock(1) Chris Wright
2004-09-24 22:30       ` mlock(1) Jeff Garzik
2004-09-24 23:08         ` mlock(1) Chris Wright
2004-09-24 22:59     ` mlock(1) Andrea Arcangeli
2004-09-24 23:46       ` mlock(1) Nigel Cunningham
2004-09-25  1:07         ` mlock(1) Andrea Arcangeli
2004-09-25  1:21           ` mlock(1) David Lang
2004-09-25  1:30             ` mlock(1) Andrea Arcangeli
2004-09-25  1:46               ` mlock(1) Valdis.Kletnieks
2004-09-25  2:15                 ` mlock(1) Andrea Arcangeli
2004-09-25  2:46                   ` mlock(1) Valdis.Kletnieks
2004-09-25  2:58                     ` mlock(1) Andrea Arcangeli
2004-09-25  3:29                       ` mlock(1) Valdis.Kletnieks
2004-09-25  4:07                         ` mlock(1) Andrea Arcangeli
2004-09-25  4:52                           ` mlock(1) Valdis.Kletnieks
2004-09-25 17:15                         ` mlock(1) Andy Lutomirski
2004-09-25  2:33                 ` mlock(1) Bernd Eckenfels
2004-09-25  1:27           ` mlock(1) Andrea Arcangeli
2004-09-28 22:03             ` mlock(1) Robert White
2004-09-28 22:15               ` mlock(1) Andrea Arcangeli
2004-09-28 23:26                 ` mlock(1) Robert White
2004-09-29  1:16                   ` mlock(1) Jon Masters
2004-09-29  1:23                     ` mlock(1) Alan Cox
2004-09-29  3:46                     ` mlock(1) Robert White
2004-09-29 12:34                       ` mlock(1) Jon Masters
2004-09-29 15:57                       ` mlock(1) Lee Revell
2004-09-29 22:56                         ` mlock(1) Paul Jackson
2004-09-25 12:21           ` mlock(1) Nigel Cunningham
2004-09-25 14:53             ` mlock(1) Andrea Arcangeli
2004-09-28  8:48               ` mlock(1) Pavel Machek
2004-09-30 17:42                 ` mlock(1) Andrea Arcangeli
2004-09-30 18:54                   ` mlock(1) Pavel Machek
2004-09-30 19:17                     ` mlock(1) Andrea Arcangeli
2004-09-30 19:52                       ` mlock(1) Pavel Machek
2004-10-04 12:21                   ` Jack Lloyd [this message]
2004-09-24 23:59       ` mlock(1) Bernd Eckenfels
2004-09-25  0:25         ` mlock(1) Nigel Cunningham
2004-09-25  1:18           ` mlock(1) Andrea Arcangeli
2004-09-27  6:16             ` mlock(1) Stefan Seyfried
2004-09-27 10:32               ` mlock(1) Nigel Cunningham
2004-09-27 14:29                 ` mlock(1) Andrea Arcangeli
2004-09-27 20:32                   ` mlock(1) Wolfgang Walter
2004-09-27 14:16               ` mlock(1) Andrea Arcangeli
2004-09-27 13:31                 ` mlock(1) Alan Cox
2004-09-29  1:48                   ` mlock(1) Andrea Arcangeli
2004-09-27 14:34                 ` mlock(1) Stefan Seyfried
2004-09-27 15:07                   ` mlock(1) Andrea Arcangeli
2004-09-27 15:25                     ` mlock(1) Stefan Seyfried
2004-09-27 15:38                       ` mlock(1) Andrea Arcangeli
2004-09-30 13:04                     ` mlock(1) Pavel Machek
2004-09-27 22:22                 ` mlock(1) Nigel Cunningham
2004-09-27 22:43                   ` mlock(1) Andrea Arcangeli
2004-09-28 22:03                     ` mlock(1) Nigel Cunningham
2004-09-24 20:24 ` mlock(1) Chris Friesen
2004-09-24 21:17 ` mlock(1) Andrew Morton
2004-09-25  0:26   ` mlock(1) Chris Wright
2004-09-25  1:28     ` mlock(1) Andrew Morton
2004-09-25  1:33       ` mlock(1) Chris Wright

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=20041004122120.GG664@acm.jhu.edu \
    --to=lloyd@randombit.net \
    --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