[Mono-bugs] [Bug 60573][Nor] Changed - CryptoStream output 1 block short after Flush

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=60573

--- shadow/60573	2004-06-23 10:37:56.000000000 -0400
+++ shadow/60573.tmp.13435	2004-06-23 11:33:55.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 60573
 Product: Mono: Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: Other
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: sebastien@ximian.com                            
 ReportedBy: t7@pobox.com               
 QAContact: mono-bugs@ximian.com
@@ -330,6 +330,21 @@
 Note that if your application ensure 8 bytes blocks you can use
 PaddingMode.None (but this may be dangerous if you change cipher in
 the future as the block size can vary).
 
 If this isn't a padding issue I would appreciate a (as small as
 possible) test case for the Read. Thanks
+
+------- Additional Comments From sebastien@ximian.com  2004-06-23 11:33 -------
+Fixed in CVS.
+
+The problem was a different division of responsability (compared to MS
+implementation) between the CryptoStream class and the ICryptoTransform's.
+
+The fix couldn't be retrofitted in CryptoStream as the class doesn't
+know if it's dealing with an Encryptor or a Decryptor (this isn't
+exposed by ICryptoTransform). Luckily the ICryptoTransform-derived
+code is located in a single class
+(Mono.Security.Cryptography.SymmetricTransform).
+
+David: I'm closing the bug. If you have other issues (like the Read
+one) please open up another bug with a sample. Thanks again.