All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: fvw@var.cx, linux-kernel@vger.kernel.org
Cc: Andries.Brouwer@cwi.nl, linux-crypto@nl.linux.org
Subject: Re: 2.6.0-test2+Util-linux/cryptoapi
Date: Thu, 31 Jul 2003 11:41:25 +0200 (MEST)	[thread overview]
Message-ID: <UTC200307310941.h6V9fP204094.aeb@smtp.cwi.nl> (raw)

> First of all, in util-linux 2.12 the keybits option is gone
> I wanted to have losetup/mount hash the passphrase

The patches I got were maximal, too much junk.
So I went for a minimal version instead.

It is usable (when the kernel part is stable, which it isn't today)
but mount/losetup may well acquire a few options before it is
conveniently usable.

(I do not read crypto lists, and see only a very small fraction of
what passes by on lk, so if you want to influence util-linux
an explicit cc is a good idea.)

> has the encryption setup changed again since 2.4.x with hvr's
> testing cryptoapi stuff?

cryptoloop as it went in is essentially hvr's.

Andries

             reply	other threads:[~2003-07-31  9:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31  9:41 Andries.Brouwer [this message]
2003-08-01 18:45 ` 2.6.0-test2+Util-linux/cryptoapi Ben Slusky
2003-08-13 14:42 ` 2.6.0-test2+Util-linux/cryptoapi Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 16:42 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-08-01 21:00 2.6.0-test2+Util-linux/cryptoapi Andries.Brouwer
2003-07-31  3:45 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren
2003-07-31  4:39 ` 2.6.0-test2+Util-linux/cryptoapi James Morris
2003-07-31  5:04   ` 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren
2003-07-31  5:20     ` 2.6.0-test2+Util-linux/cryptoapi James Morris
2003-07-31 16:37       ` 2.6.0-test2+Util-linux/cryptoapi Frank v Waveren

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=UTC200307310941.h6V9fP204094.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=fvw@var.cx \
    --cc=linux-crypto@nl.linux.org \
    --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.