I was able to trim this down to a specific subset and make a unit test out of it. Although SslStream has compatibility problems communicating with other implementations (such as .Net), mono SslStream also has a problem talking to *itself*. The root causes are the same for both the internal compatibility problem, and the external problems. So the internal problem is demonstrated in the SslStreamTest here: https://github.com/rahvee/mono/commit/b0362fe70fb445f90197eab712b8d995f88d78e1
Should I submit a pull request? Note: This test currently passes on .Net, and fails on mono. I don't know if you guys want me submitting a test that is known to fail on mono. Should I file a bug in bugzilla? (I'm not sure if I have sufficient permission). And as a matter of style, in the above commit I needed to use some classes that weren't available in the MonoTest namespace, so I used "global::System....." in several places. Is this the correct and/or best way to deal with it? Or is there a better way to handle that? _______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
