mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Fruhwirth Clemens <clemens@endorphin.org>,
	Paul Walker <paul@black-sun.demon.co.uk>,
	linux-kernel@vger.kernel.org, Bill Davidsen <davidsen@tmr.com>,
	linux-crypto@nl.linux.org, James Morris <jmorris@redhat.com>
Subject: Re: Announce loop-AES-v3.0b file/swap crypto package
Date: Tue, 18 Jan 2005 18:23:22 +0100	[thread overview]
Message-ID: <20050118172322.GH8747@pclin040.win.tue.nl> (raw)
In-Reply-To: <41ED2CD4.B0502FD7@users.sourceforge.net>

On Tue, Jan 18, 2005 at 05:35:48PM +0200, Jari Ruusu wrote:
> Fruhwirth Clemens wrote:
> > Nothing about kernel crypto is backdoored. If Ruusu thinks different, he
> > should show me source code. Till then, treat it as FUD.
> 
> I have been submitting fix for this weakness to mainline mount (part of
> util-linux package) since 2001, about 2 or 3 times a year. Refusing to fix
> it for *years* counts as intentional backdoor.
> 
> You call it whatever you want. I call it backdoor.

Hi Jari,

Your crypto is good, your language is bad.

Clearly there is no intentional backdoor.
You do not gain any credibility by saying otherwise.

Next, confusing the kernel with util-linux is a strange trick.

Finally, in the time I maintained util-linux I have asked you
I don't know how often to come with a series of small clean
patches instead of a huge ugly all-or-nothing monolithic patch.
But you didnt.

Maybe you don't understand, but it does not suffice when code
is correct - it must also be maintainable.

Something rather similar is true for the kernel, I suspect.
A series of short clean patches would have solved all problems.

As it is, time may be running out - some years ago your stuff
was far superior to everything else. But alternative
approaches are being developed, and maybe loop-aes will soon
be some historic oddity.

Andries


  reply	other threads:[~2005-01-18 17:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 21:58 Jari Ruusu
2005-01-17  4:26 ` Bill Davidsen
2005-01-17  5:10   ` Willy Tarreau
2005-01-17 15:08   ` Jari Ruusu
2005-01-17 19:14     ` Fruhwirth Clemens
2005-01-17 19:29       ` Paul Walker
2005-01-17 21:04         ` Fruhwirth Clemens
2005-01-17 21:39           ` Paul Walker
2005-01-18 15:35           ` Jari Ruusu
2005-01-18 17:23             ` Andries Brouwer [this message]
2005-01-18 18:38               ` Venkat Manakkal
2005-01-19  0:18                 ` Dan Hollis
2005-01-19  0:46                   ` Kyle Moffett
2005-01-19 17:03                   ` Bill Davidsen
2005-01-19 17:57                     ` Fruhwirth Clemens
2005-01-19 21:24                       ` James Morris
2005-01-19 22:18                         ` Fruhwirth Clemens
2005-01-20 16:42                       ` Bill Davidsen
2005-01-17 21:26       ` markus reichelt
2005-01-17 23:11         ` Fruhwirth Clemens
2005-01-18  0:06           ` Daniel Harvey
2005-01-18 23:30             ` Peter_22
2005-01-18  9:49           ` jerome etienne
2005-01-18 15:36             ` Jari Ruusu
2005-01-20 22:38           ` markus reichelt
2005-01-21 18:29       ` Sytse Wielinga
2005-01-17 20:28     ` Andreas Jellinghaus
2005-01-17 21:38     ` Paul Walker

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=20050118172322.GH8747@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=clemens@endorphin.org \
    --cc=davidsen@tmr.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=jmorris@redhat.com \
    --cc=linux-crypto@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@black-sun.demon.co.uk \
    /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

all inboxes | Powered by JetHome®