Mr. Hollis: I think you misread what I said I am offering a workaround. However, I would love to see all these issues resolved. I am simply saying that these issues are not justification to say it is "broken" as Mr. Ruusu does, and that it can be usable in many circumstances. Sure, with bugs, certain configurations do not work, and resolving the bugs is best. 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 6:04 PM -----Original Message----- From: Dan Hollis [mailto:goemon@xxxxxxxxx] Sent: Monday, July 09, 2001 5:54 PM To: IT3 Stuart B. Tener, USNR-R Cc: Jari Ruusu; Dale Amon; linux-crypto@xxxxxxxxxxxx Subject: RE: Announce loop-AES-v1.3b file crypto package On Mon, 9 Jul 2001, IT3 Stuart B. Tener, USNR-R wrote: > Well, that is a separate story and completely different from what > you mentioned. You presented a personal issue you needed assistance with and > I tried to help you out. Now you are angry because IO provided a solution, > and it does not meet your broadest imaginable needs. Im not angry at all, im just pointing out that your solution is not a solution at all -- it is a microsoft "solution", or more like a dilbert-style "solution". Current i-patch is not totally broken but it *is* extremely flawed. No amount of billgates-style handwaving and "mkfs workarounds" will make the current bugs simply evaporate. Only a discussion of the current bugs and examination of the code will fix things. Sticking your head in the sand and pretending the bugs (dont exist|will magically disappear) wont help the situation. -Dan Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
