Linux cryptographic layer development
 help / color / mirror / Atom feed
From: rsnel@cube.dyndns.org
To: linux-crypto@vger.kernel.org
Cc: christoph.sievers@gmail.com, herbert@gondor.apana.org.au
Subject: proposed XTS implementation
Date: Mon, 3 Sep 2007 23:53:13 +0200	[thread overview]
Message-ID: <20070903215313.GA3622@cube.dyndns.org> (raw)

Hello list (cc: Herbert, Christoph),

In my previous mail you will find a proposed patch to
implement XTS (a block cipher mode alike LRW, but unlike
LRW, no known security problems (LRW has problems encrypting
it's own key)). An email from Cristoph sparked my interest,
and the lrw.c file was a good starting point. You will find
that xts.c includes less weird functions than lrw.c.

xts.c is compilation tested as a module outside the kernel,
it 'hould work(tm).

Herbert: I need to instances of AES, did I do that correctly?

Greetings,

Rik.

-- 
Nothing is ever a total loss; it can always serve as a bad example.

             reply	other threads:[~2007-09-03 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 21:53 rsnel [this message]
2007-09-07  6:22 ` proposed XTS implementation Herbert Xu

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=20070903215313.GA3622@cube.dyndns.org \
    --to=rsnel@cube.dyndns.org \
    --cc=christoph.sievers@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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