Hi, On Fri, Nov 09, 2018 at 11:02:33AM +0100, Nicolas M. Thiery wrote: > > I once again got bitten yesterday by installations of Sage without SSL > support. And thus no pip. Which made me check on Openssl's web page > which now states that "OpenSSL is licensed under an Apache-style > license". > > If this can help Sage having systematic support for SSL (e.g. through > openssl as standard package), that would be great!
I am tracking this page for a while (for openssl updates) and nothing changed there. Everything is hidden in the "-style" suffix, the "Apache-style" license refers to their usual license, that adds something about advertizriong them, making the license GPL-incompatible, see https://www.openssl.org/source/license.html Regarding relicensing, i forgot the link, but there is a clear statement (at the time of the 1.1.1 LTS release) that it will take times since they want to check with lawyers that everything is correct. Ciao, Thierry > Cheers, > Nicolas > > [1] https://www.openssl.org/ > > On Sat, Mar 31, 2018 at 07:01:45AM -0700, Emmanuel Charpentier wrote: > > Due notice taken. That would simplify [1]Trac#24107 (which is currently > > dormant, due to the undergoing changes in the configutation system) > > enormously. > > -- > > Emmanuel Charpentier > > Le samedi 31 mars 2018 14:06:11 UTC+2, Volker Braun a écrit : > > > > [2]https://www.openssl.org/blog/blog/2018/03/01/last-license/ > > They want to change the license in the next release, which is currently > > in Alpha, and tentatively set for May. > > On Saturday, March 31, 2018 at 11:44:58 AM UTC+2, Thierry > > (sage-googlesucks@xxx) wrote: > > > > Hi, > > not sure whether there is a database access issue, but according to > > [1], > > there is no contributor to be found for relicensing openssl. That > > would be > > awesome. > > Ciao, > > Thierry > > [1] [3]https://license.openssl.org/trying-to-find > > > > -- > > 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 [4]sage-devel+unsubscr...@googlegroups.com. > > To post to this group, send email to [5]sage-devel@googlegroups.com. > > Visit this group at [6]https://groups.google.com/group/sage-devel. > > For more options, visit [7]https://groups.google.com/d/optout. > > > > Références > > > > 1. https://trac.sagemath.org/ticket/24107 > > 2. https://www.openssl.org/blog/blog/2018/03/01/last-license/ > > 3. https://license.openssl.org/trying-to-find > > 4. mailto:sage-devel+unsubscr...@googlegroups.com > > 5. mailto:sage-devel@googlegroups.com > > 6. https://groups.google.com/group/sage-devel > > 7. https://groups.google.com/d/optout > > Nicolas > -- > Nicolas M. Thiéry "Isil" <nthi...@users.sf.net> > http://Nicolas.Thiery.name/ > > -- > 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 https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
