From fnaumann@mail.cs.uni-magdeburg.de Tue Aug 31 22:48:00 2004 Subject: [MiNT] [Fwd: Re: XaAES.KM] From: Martin Tarenskeen Reply-To: m.tarenskeen@zonnet.nl To: MiNT Mailing List Content-Type: multipart/mixed; boundary="=-cNrcI5EQD+hzRU0HmXve" Message-Id: <1093982450.2341.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 31 Aug 2004 22:20:05 +0200 X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.27.0.6; VDF: 6.27.0.39; host: postbode02.zonnet.nl) Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: m.tarenskeen@zonnet.nl Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel --=-cNrcI5EQD+hzRU0HmXve Content-Type: text/plain Content-Transfer-Encoding: 7bit This was meant for the MiNT mailing list. That "reply-to" thing again ... --=-cNrcI5EQD+hzRU0HmXve Content-Disposition: inline Content-Description: Doorgestuurd bericht - Re: [MiNT] XaAES.KM Content-Type: message/rfc822 Subject: Re: [MiNT] XaAES.KM From: Martin Tarenskeen Reply-To: m.tarenskeen@zonnet.nl To: Henk Robbers In-Reply-To: <200408310134.46567.h.robbers@chello.nl> References: <200408310134.46567.h.robbers@chello.nl> Content-Type: text/plain Message-Id: <1093931764.2320.19.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 31 Aug 2004 07:56:04 +0200 Content-Transfer-Encoding: 7bit Op di 31-08-2004, om 01:34 schreef Henk Robbers: > Hi Frank and Ozk (and all that worked on MiNT/XaAES) > > I experienced a extremely exciting day today :-) > > I installed MiNT 1.16.0 using XaAES kernel module on my TT. > > I am very pleases. And I congratulate you with the result. > The combination gives a strong feeling of solidity, robustness, > reliability and usefullnes. > I always had the firm intention to make XaAES the de facto standard > for any AES development in the future. > Now that MiNT/XaAES has reached this state, that goal becomes really > in reach and feasable. > > So MiNT/XaAES developers: Dont be shy! Stand strong! > Anything new you add to XaAES from now on is as it should be. > Ignore any complaints about not being stanard. Anything you do > is standard by definition. > :-) > I already replaced my N_AES setup with XaAES in the time Henk was working on it. I have sent him many (Dutch!) bugreports in that period which he all fixed, making XaAES really stable and useful for me then already. Thanks again, Henk ! When I first installed the new MiNT 1.16.0 with xaaes.km I was first a bit disappointed because I had quite a few crashes. But the bugtracker website is watched carefully by the current developers and the current CVS version I'm using now is really good. So I agree with Henk: for me XaAES sets the new AES standard. -- Martin Tarenskeen --=-cNrcI5EQD+hzRU0HmXve--