Mr. Riedel:
I think publishing the code (even if partially completed) will help
stimulate people to evaluate what direction it is going in, and what is
being worked on. In addition, perhaps, maybe, you will have to do a little
less work if someone actually goes and fixes a bug for you! Absent the
possibility of an ego the size of Mars (just kidding you don't seem
egotistical), I am sure you would appreciate the help!
Very Respectfully,
Stuart Blake Tener, IT3, USNR-R, N3GWG
VTU 1904G (Volunteer Training Unit)
stuart@xxxxxxxxxxx
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 1:59 PM
-----Original Message-----
From: Herbert Valerio Riedel [mailto:hvr@xxxxxxxxxx]
Sent: Monday, July 09, 2001 1:30 PM
To: Jari Ruusu
Cc: Dale Amon; IT3 Stuart B. Tener, USNR-R; linux-crypto@xxxxxxxxxxxx
Subject: Re: Announce loop-AES-v1.3b file crypto package
On Mon, 9 Jul 2001, Jari Ruusu wrote:
> Dale Amon wrote:
> > On Sun, Jul 08, 2001 at 06:39:16PM -0700, IT3 Stuart B. Tener, USNR-R
wrote:
> > > a) It installed flawlessly (though I did install the standard Linus
version
> > > of 2.4.6 kernel first)
> > > b) I created a loop back device with it, and in fact was able to
mkreiserfs
> > > on the device, mount it, and write data to it with crypto above the
> > > mkreiserfs
> > >
> >
> > Likewise, I have been using the 2.4.3 international patch
> > and running multiple machines with reiserfs on top of a
> > crypto loopback on top of a raw raid1 set for over 4 months
> > and have had no problem.
> >
> > I have applied the international patches and built kernels
> > for a large number of machines, from laptops to desktop to
> > servers, all without pain or bother.
> >
> > I have had exactly zero trouble with the international
> > patches except for the cases where they seriously lagged
> > mainstream kernel release.
>
> patch-int-2.4.6.bz2 available from HVR's web site is still the same time
> bomb waiting to explode as patch-int-2.4.3.1.bz2.
>
> Have you actually audited that code?
>
> I have audited some of it. Conclusion: BROKEN
...do you mind sharing your thoughts with us? :-)
but please, don't tell me again, to give up on the crypto API... ;-)
since I'm quite determined to fix all problems, it would be usefull to
have a definite list of them...
btw, the non-reentrant part has been almost fixed... but it's not
released yet.
if you are refering to the IV overflow, that's going to be addressed as
well rsn...
as to the patch-int vs cryptoapi, the patch-int-2.4.6.bz2 actually nothing
more than a patch-int-2.4.3.1 applied against a 2.4.6...
so they are both the same...
greetings,
--
Herbert Valerio Riedel / Phone: (EUROPE) +43-1-58801-18840
Email: hvr@xxxxxxxxxx / Finger hvr@xxxxxxx for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748 5F65 4981 E064 883F 4142
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
