Hi, > It may (or may not) be a MemoryStream issue. The current CryptoStream > implementation is very rudimentary - it was able to run some samples from MS > but it's still far from complete. It's also one of the few crypto class that > still doesn't have any unit tests.
I assume it is because MemoryStream.Close() resets its internal buffer and CryptoStream.FlushFinalBlock() closes the stream. I don't know that Close() disposes internal buffer by ECMA spec. MS stream apparently holds. Regards, Atsushi Eno _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
