On Sun, Oct 25, 2015 at 3:11 AM, Volker Braun <vbraun.n...@gmail.com> wrote: > On Sunday, October 25, 2015 at 10:13:39 AM UTC+1, François wrote: >> >> That explain why I had to change the configuration for git. >> No openssl headers, I have heard they are going to switch to libressl, > > > Not sure about that, they probably want everybody to use their own > proprietary crypto framework. Right now only OSX's ssh uses libressl, > anything else in OSX that traditionally uses openssl still uses Apple's > openssl. > > The official suggestion from the dev relations is to just bundle openssl in > your application. Obviously that is terrible for security as there is no
At least openssl very recently changed their license to be GPL-compatible, so it is legal to include with Sage... finally. > central point to apply security updates. On the other hand Apple's track > record at applying security updates centrally has been, lets say, less than > stellar (and getting worse). > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
