Hello Elan, Please fill both issue in Bugzilla (http://bugzilla.ximian.com/). I will look at them once I finished something else I have in mind.
> (1) The Mono symmetric key cypto providers have CanReuseTransform == > false, whereas .NET defines them to be true. This wouldn't have been > that much of a problem, except that this code: AFAIK most cryptography classes can be reused. However this isn't tested in the NUnit tests. That's why CanReuseTransform is returning false for all classes. This will need to be fixed to (a) match MS implementation and (b) for performance issues. It _was_ a known (but forgotten) issue. > (2) In creating a CryptoStream to compute an MD5 hash, the .NET code was > finishing up by calling: > > stream.FlushFinalBlock(); > stream.Close(); Can you add (in Bugzilla) some code which exhibit this behavior (works on MS, fails on Mono). I will fix it and add the code to NUnit. A last request. Could you tell me which are the cryptographic classes you used in your applications ? I'm curious about what's currently being used (and what may still hide monstuous bugs ;-). Thanks for the reporting the issues. Sebastien Pouliot Security Architect, Motus Technologies, http://www.motus.com/ work: [EMAIL PROTECTED] home: [EMAIL PROTECTED] _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
