https://bugzilla.novell.com/show_bug.cgi?id=371695
User [EMAIL PROTECTED] added comment https://bugzilla.novell.com/show_bug.cgi?id=371695#c2 Sebastien Pouliot <[EMAIL PROTECTED]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|System.Security |CORLIB Resolution| |WONTFIX --- Comment #2 from Sebastien Pouliot <[EMAIL PROTECTED]> 2008-05-20 13:37:18 MST --- This is a known issue. MS framework provides managed and unmanaged algorithms that use different backends (ICryptoAPITransform for the later) and have some, minor, differences. Mono has a single one (all managed implementation) so all algorithms behave identically. Also note that this property exists because it needs to be checked. Ignoring it, because it looks static, will cause problems if you change the algorithm, or the algorithm implementation, being used (including keeping the same algorithm) [1]. Sadly the framework design, even we using CryptoStream, does not shield the developers from making this check. [1] E.g. if you call Rijndael.Create() instead of new RijndaelManaged (which is the recommended pattern) you can't be sure what implementation you'll receive (since the end-user machine.config could override what you expect to be available). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
