Re: [Mono-dev] Bug with Ssl cert validation
On 2014-03-19 01:55, Greg Young wrote: Just off the top of my head... maybe a summer of code would be better spent on these kinds of issues and improving the throughput of donations as opposed to the next interesting technical topic. +1. The complexities (no obvious build files, no csproj, no visible documentation (e.g. pointed to via README), numerous warnings on default compiles) in building mcs and running tests has also kept me from contributing except in the most trivial ways. Regards, David ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
Well said. Every time I ask I get a response along the lines of oh you just run make along with an anecdote about a script error or required package which gives about 20% of the required info. A script which is guaranteed to build on Linux, Windows VS2010 and VS2012 (lots of devs haven't upgraded) and possibly on Mac too would enable all the little guys to quickly fix trivial bugs. When I spent a week trying to get it to compile, to fix my one line bug, I gave up. I want to contribute but I only have time to do that and not to mend a build system I don't understand. Bryan Crotaz Silver Curve On 19 Mar 2014, at 08:45, David Schmitt da...@dasz.at wrote: On 2014-03-19 01:55, Greg Young wrote: Just off the top of my head... maybe a summer of code would be better spent on these kinds of issues and improving the throughput of donations as opposed to the next interesting technical topic. +1. The complexities (no obvious build files, no csproj, no visible documentation (e.g. pointed to via README), numerous warnings on default compiles) in building mcs and running tests has also kept me from contributing except in the most trivial ways. Regards, David ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
Hi guys Not being able to work with sources (debug) as greatest rejection point for users around me and those are ergular .net - c# developers used to work with .net and Visual Studio. Though just testing and proper bug reporting is great help for Xamarin team. You'll have to understand that increasing number of community pull requests will have impact on Xamarin team - testing and approval. So we can not expect miracles to happen in next few months and we have to understand that * there is not enough manpower / resources in Xamarin alone * documentation is outdated and missing * volume is increasing and small team like Xamarin + community almost every aspect o communication - see forums and mailing lists o number of users o platforms * Xamarin focus currently (and we must understand why is this so and accept this as the fact) o mobile platforms o Xamarin Studio So let's organize. 1. for starter maybe changing the subject. line so we could track this easier 2. define/decide where we could put notes (latest findings, ideas, workarounds) today google docs or github it is up to us - just do not get dragged in into endless discussions There is so much to say/do, but have to go. cheers Mel On 2014.03.19 09:49, Bryan Crotaz wrote: Well said. Every time I ask I get a response along the lines of oh you just run make along with an anecdote about a script error or required package which gives about 20% of the required info. A script which is guaranteed to build on Linux, Windows VS2010 and VS2012 (lots of devs haven't upgraded) and possibly on Mac too would enable all the little guys to quickly fix trivial bugs. When I spent a week trying to get it to compile, to fix my one line bug, I gave up. I want to contribute but I only have time to do that and not to mend a build system I don't understand. Bryan Crotaz Silver Curve On 19 Mar 2014, at 08:45, David Schmitt da...@dasz.at wrote: On 2014-03-19 01:55, Greg Young wrote: Just off the top of my head... maybe a summer of code would be better spent on these kinds of issues and improving the throughput of donations as opposed to the next interesting technical topic. +1. The complexities (no obvious build files, no csproj, no visible documentation (e.g. pointed to via README), numerous warnings on default compiles) in building mcs and running tests has also kept me from contributing except in the most trivial ways. Regards, David ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Miljenko Cvjetko dipl.ing. ET Direktor/CEO Projektant rjes(enja/Solution Architect Razvojni programer/Senior developer Voditelj projekta/Project Manager IX juz(na obala 13 Kajzerica Zagreb T: 385 1 777 M: 385 91 557 447 3 F: 385 1 7779556 e: mcvje...@holisticware.net w: http://holisticware.net ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
From: Sebastien Pouliot [mailto:sebastien.poul...@gmail.com] var mySslStream = new SslStream (client.GetStream(), false, ValidateServerCertificate); if you read the source [1] (or look at the API compatibility page [2]) you'll see that this .ctor is decorated with [MonoTODO (userCertificateValidationCallback is not passed X509Chain and SslPolicyErrors correctly)] Changing it to var mySslStream = new SslStream (client.GetStream(), false); *and* having run `mozroots` will work. Thank you for this information, but it causes me an equally significant problem. I need to accept the server cert if it passes validation with mozroots, but if that fails, then I need to get user input to determine if they'll accept the cert. I guess the best way to do this will be to first create the SslStream and AuthenticateAsClient, and simply wait to see if it succeeds. If it fails, then throw it away, create a new SslStream with RemoteCertificateValidationCallback, and ignore the X509Chain and SslPolicyErrors, just simply present the certificate to user. Any better ideas? Thanks again, for your very prompt and helpful response. :-) ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
On Tue, Mar 18, 2014 at 6:33 AM, Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: From: Sebastien Pouliot [mailto:sebastien.poul...@gmail.com] var mySslStream = new SslStream (client.GetStream(), false, ValidateServerCertificate); if you read the source [1] (or look at the API compatibility page [2]) you'll see that this .ctor is decorated with [MonoTODO (userCertificateValidationCallback is not passed X509Chain and SslPolicyErrors correctly)] Changing it to var mySslStream = new SslStream (client.GetStream(), false); *and* having run `mozroots` will work. Thank you for this information, but it causes me an equally significant problem. I need to accept the server cert if it passes validation with mozroots, but if that fails, then I need to get user input to determine if they'll accept the cert. I guess the best way to do this will be to first create the SslStream and AuthenticateAsClient, and simply wait to see if it succeeds. If it fails, then throw it away, create a new SslStream with RemoteCertificateValidationCallback, and ignore the X509Chain and SslPolicyErrors, just simply present the certificate to user. Any better ideas? Contribute! :-) Thanks again, for your very prompt and helpful response. :-) ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
I'd love to contribute, but I have now spent several days trying and failing to compile Mono for Visual Studio so that I can fix bugs in the C# libraries. If someone could write a VS2010 solution that can be used to debug Mono, that would help hundreds of devs like me who just want to fix their favourite bug. On 18 March 2014 11:52, Sebastien Pouliot sebastien.poul...@gmail.comwrote: On Tue, Mar 18, 2014 at 6:33 AM, Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: From: Sebastien Pouliot [mailto:sebastien.poul...@gmail.com] var mySslStream = new SslStream (client.GetStream(), false, ValidateServerCertificate); if you read the source [1] (or look at the API compatibility page [2]) you'll see that this .ctor is decorated with [MonoTODO (userCertificateValidationCallback is not passed X509Chain and SslPolicyErrors correctly)] Changing it to var mySslStream = new SslStream (client.GetStream(), false); *and* having run `mozroots` will work. Thank you for this information, but it causes me an equally significant problem. I need to accept the server cert if it passes validation with mozroots, but if that fails, then I need to get user input to determine if they'll accept the cert. I guess the best way to do this will be to first create the SslStream and AuthenticateAsClient, and simply wait to see if it succeeds. If it fails, then throw it away, create a new SslStream with RemoteCertificateValidationCallback, and ignore the X509Chain and SslPolicyErrors, just simply present the certificate to user. Any better ideas? Contribute! :-) Thanks again, for your very prompt and helpful response. :-) ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Bryan Crotaz Managing Director Silver Curve ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
From: Sebastien Pouliot [mailto:sebastien.poul...@gmail.com] Sent: Tuesday, March 18, 2014 7:52 AM Any better ideas? Contribute! :-) Honestly, I *do* like this idea, and I'm trying. I'm a C# developer, and have never been a mono developer (I've been a user of C#/mono, but never a contributor), and I'm finding the learning curve to be pretty steep... In a recent thread, I pushed through to the point of being able to build the mono sources, build something linked against the mono source, and step through the mono source. I tried to do the same thing this time, but when I step into AuthenticateAsClient, all the code is grayed out, and if I step one step further, the debugger crashes. So I spent some time trying to figure out why I couldn't step into that code any further, and then I started sprinkling WriteLine statements... And there *has* to be a better way. I wouldn't say I gave up. I posted here and thanks to Sebastien, got a workaround, which takes the pressure off so I can focus on our product deliverable. But I'd like to get a better understanding of this mono source and how to properly debug it. Or maybe I just need to suck it up and work through the WriteLine debugging workflow? I hope not. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
From: Bryan Crotaz [mailto:bryan.cro...@silvercurve.co.uk] I'd love to contribute, but I have now spent several days trying and failing to compile Mono for Visual Studio so that I can fix bugs in the C# libraries. If someone could write a VS2010 solution that can be used to debug Mono, that would help hundreds of devs like me who just want to fix their favourite bug. Did you see these posts? http://mono.1490590.n4.nabble.com/Getting-started-on-mono-sources-td4661906.html Scroll down to step-by-step and also --disable-bcl-opt I know this is for Xamarin Studio on mac (or linux/unix)... And also, I've only had mixed success in stepping / debugging mono sources this way, but maybe you have access to a non-windows machine? Or maybe you care to build mono with cygwin on windows, and attempt to reproduce this result in Visual Studio? I know VS has a checkbox, like XS, to enable/disable stepping through assembly sources. But of course, you can't step through the Microsoft closed source. ;-) And you'll probably have to figure out some tricks to make VS debug against the mono assemblies instead of .NET. This might be easiest using MonoDevelop / XS (even on windows.) I venture a guess that it's easier to make XS debug against mono sources. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
I spent 4 days trying to get make to work on Cygwin. Followed those instructions and others. Every post I found had significant errors in it (eg Cygwin package names ) or was years out of date. Bryan Crotaz Silver Curve On 18 Mar 2014, at 13:25, Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: From: Bryan Crotaz [mailto:bryan.cro...@silvercurve.co.uk] I'd love to contribute, but I have now spent several days trying and failing to compile Mono for Visual Studio so that I can fix bugs in the C# libraries. If someone could write a VS2010 solution that can be used to debug Mono, that would help hundreds of devs like me who just want to fix their favourite bug. Did you see these posts? http://mono.1490590.n4.nabble.com/Getting-started-on-mono-sources-td4661906.html Scroll down to step-by-step and also --disable-bcl-opt I know this is for Xamarin Studio on mac (or linux/unix)... And also, I've only had mixed success in stepping / debugging mono sources this way, but maybe you have access to a non-windows machine? Or maybe you care to build mono with cygwin on windows, and attempt to reproduce this result in Visual Studio? I know VS has a checkbox, like XS, to enable/disable stepping through assembly sources. But of course, you can't step through the Microsoft closed source. ;-) And you'll probably have to figure out some tricks to make VS debug against the mono assemblies instead of .NET. This might be easiest using MonoDevelop / XS (even on windows.) I venture a guess that it's easier to make XS debug against mono sources. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
I spent 4 days trying to get make to work on Cygwin. Followed those instructions and others. Every post I found had significant errors in it (eg Cygwin package names ) or was years out of date. There are at least two blockers/bugs in Cygwin/Mingw32 that I know of that prevent Mono from building. Firstly a header file in the mingw32 Win32 headers needs to be edited to remove a duplicate declaration. There is even a comment in the offending header file that it needs to be removed. Why they don't just remove it in the distribution I have no idea. Next, /etc/fstab in Cygwin needs to be edited to add noacl to the /cygdrive mount. This is to avoid the situation where files created by a Win32 executable launched from a bash script end up with no permissions on the Cygwin side (from Cygwin's attempt to map Windows permissions to Unix permissions). The files with no permissions cause failures in make later on. Specifying noacl fixes this issue. These two issues (particularly the second) had me stuck for several days, but are never mentioned in any tutorial on building Mono in Windows that I could find. I still never ended up with a successful mono build in Cygwin though. Another thing, ignore the tutorials that say you can't use make from Cygwin and need a special version of make 3.80 from elsewhere. That no longer applies. Sly ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
Just off the top of my head... maybe a summer of code would be better spent on these kinds of issues and improving the throughput of donations as opposed to the next interesting technical topic. Greg On Wed, Mar 19, 2014 at 2:39 AM, Konaju Games (Dev) d...@konaju.com wrote: I spent 4 days trying to get make to work on Cygwin. Followed those instructions and others. Every post I found had significant errors in it (eg Cygwin package names ) or was years out of date. There are at least two blockers/bugs in Cygwin/Mingw32 that I know of that prevent Mono from building. Firstly a header file in the mingw32 Win32 headers needs to be edited to remove a duplicate declaration. There is even a comment in the offending header file that it needs to be removed. Why they don't just remove it in the distribution I have no idea. Next, /etc/fstab in Cygwin needs to be edited to add noacl to the /cygdrive mount. This is to avoid the situation where files created by a Win32 executable launched from a bash script end up with no permissions on the Cygwin side (from Cygwin's attempt to map Windows permissions to Unix permissions). The files with no permissions cause failures in make later on. Specifying noacl fixes this issue. These two issues (particularly the second) had me stuck for several days, but are never mentioned in any tutorial on building Mono in Windows that I could find. I still never ended up with a successful mono build in Cygwin though. Another thing, ignore the tutorials that say you can't use make from Cygwin and need a special version of make 3.80 from elsewhere. That no longer applies. Sly ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Le doute n'est pas une condition agréable, mais la certitude est absurde. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Bug with Ssl cert validation
From: Bryan Crotaz [mailto:bryan.cro...@silvercurve.co.uk] I spent 4 days trying to get make to work on Cygwin. Followed those instructions and others. Every post I found had significant errors in it (eg Cygwin package names ) or was years out of date. Oh shoot - don't know why I didn't think of this before. Even when building on mac or linux recently, the latest git checkout has failed for me. I would recommend checking out for example, 3.2.3 or something that's known to compile, and see if that helps. The latest windows package is 3.2.3, so I would suggest starting there. Maybe later revs haven't been released because of problems, or maybe there just hasn't been enough interest / effort to build the later versions... At least we can safely say that 3.2.3 *does* compile for *someone*. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
