[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-crypto
Subject:    RE: Announce loop-AES-v1.3b file crypto package
From:       "IT3 Stuart B. Tener, USNR-R" <stuart () bh90210 ! net>
Date:       2001-07-09 23:31:00
[Download RAW message or body]

Mr. Ruusu:

        Let us stay focused on bugs, and not latency issues. After all, I am
running a laptop with no other users (but me) on it, so performance is not
going to sway the bulk of crypto users whom are individuals unless the
performance hit is grossly unacceptable, obviously not if no one has
mentioned it yet.

        Are you arguing that my issuing an mkfs with the proper block size,
the I-patch would still be a time bomb?

        Well, I do hope that Mr. Riedel (nor Mr. Kjeldaas) is not ignoring
your work, and I do hope that you would be willing to help them integrate it
within if they were trying to do so.

        I am sure Mr. Riedel and Mr. Kjeldaas will respond soon, and I do
hope they are willing to accept your assistance in such an integration and
bug resolution process.

        Now on the issue of "fatware" as you note, I disagree predicated
more on a philosophical issue, that the integration of crypto into the
kernel will be cause for more people to leverage it across a greater number
of applications. I also do not "just want" loop aes I want it all. Crypto
for PPP, Crypto for logon passwords, Crypto for whatever.


Very Respectfully,

Stuart Blake Tener, IT3, USNR-R, N3GWG
VTU 1904G (Volunteer Training Unit)
stuart@bh90210.net
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's
free!)

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.

Monday, July 09, 2001 4:24 PM

-----Original Message-----
From: root@Misty.com [mailto:root@Misty.com]On Behalf Of Jari Ruusu
Sent: Monday, July 09, 2001 2:39 PM
To: stuart@bh90210.net
Cc: Dale Amon; linux-crypto@nl.linux.org
Subject: Re: Announce loop-AES-v1.3b file crypto package

"IT3 Stuart B. Tener, USNR-R" wrote:
> Mr. Ruusu:
>
>         You keep claiming that the I-patch is broken, but in reality, it
is
> only broken with regard to SMP users. I would venture to guess that you
are
> speaking about a very minute community of users whom are thus attempting
to
> use Crypto patches on SMP boxes, however I do appreciate your desire to
warn
> that community of potential hazards.

Wrong. The block size thing is a time bomb. Just follow the links I posted
earlier. Non-re-entrant ciphers also means that cryptoapi kills the
scheduling latency of high priority realtime tasks on UP.

>         Nevertheless, it does seem that you have almost a tone of
arrogance
> or religious divergence to using the I-patch / crypto API. Mr. Riedel has
> indicated on several occasions his desire to access and service the
"BROKEN"
> (as you state) code sections in an effort to subvert the bugs you
proclaim.
> Do you have some commercial interest in simply continuing to rant and rave
> about these bugs, or you have a true desire to assist in a team effort to
> effectuate a solution? Granted I appreciate that your free time is your
free
> and you can do as you wish with it, but I am saddened by seeing several
> technical experts having such trouble to work together.

If Mr. Riedel ignores stuff that I send to him, that can hardly be my fault.

And regarding assisting int. crypto patch development, Mr. Kjeldaas said
"no" to my improvements and fixes to int. crypto patch. So, I built a better
one.

I don't have any commercial intrests on loop-AES.

>         My final suggestion and conclusion is that if you and Mr. Riedel
> could work out your personal and philosophical differences and
cooperatively
> work to resolve the I-patch issues you would be doing a grand service to a
> fair community of people. Why not take the advantages of your AES Loop
> software, and blend it into the I-patch while working to resolve current
> I-patch issues as well. I personally will go so far as to say thank you
(in
> advance) and well after you would complete such an effort.

See my previous comment.

Mr Tener, why don't you audit both loop-AES and int. crypto patch. You will
soon realize meaning of fatware, and that it just does not belong in kernel.

Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>


Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/

[prev in list] [next in list] [prev in thread] [next in thread]