[Mono-bugs] [Bug 61394][Min] Changed - Error checking in "sn -pc container file.pub"
Sun, 11 Jul 2004 19:01:18 -0400 (EDT)
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 firstname.lastname@example.org.
--- shadow/61394 2004-07-10 14:20:36.000000000 -0400
+++ shadow/61394.tmp.14790 2004-07-11 19:01:18.000000000 -0400
@@ -1,14 +1,14 @@
Product: Mono: Class Libraries
@@ -28,6 +28,32 @@
$ cat myfile.pub
I don't know how CSP containers work, but I'm going to assume this behavior
+------- Additional Comments From email@example.com 2004-07-11 19:01 -------
+The best word to describe key pairs containers is "stange" - at least
+when used with .NET.
+The problem is that there are no way to directly manipulate containers
+in .NET - this must be done (indirectly) via
+[D|R]SACryptoServiceProvider using CspParameters. However, by default
+_and_ (lack of/bad) design the two class creates a new key pair when
+Sadly, this makes it impossible (using the .NET API) to know if the
+key pair was existing before creating an object referencing a specific
+It would be possible (now that Mono support containers - which it
+didn't when the security tools were created) to add Mono specific code
+to detect such conditions (but this wouldn't work when executed under
+MS runtime) so this would results in different a behaviour (and
+containers were added only "get the same behaviour" - not to enhance
+Anyway my advise to everyone is to, as much as possible, stay away
+from containers. They were added to Mono for "enhanced" compatibility
+with MS implementation - but they aren't the best solution to store
+key pairs on Linux.