git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Will OpenSSL's license change impact us?

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 24, 2017, 23:51 UTC
Message-ID
<CACBZZX6F47uC9jLxppgkUnwVpGV2jpzzP4kwTuqKgayCevomeA@mail.gmail.com>

They're changing their license[1] to Apache 2 which unlike the current fuzzy compatibility with the current license[2] is explicitly incompatible with GPLv2[3].

We use OpenSSL for SHA1 by default unless NO_OPENSSL=YesPlease.

This still hasn't happened, but given the lifetime of git versions packaged up by distros knowing sooner than later if this is going to be a practical problem would be good.

If so perhaps we could copy the relevant subset of the code int our tree, or libressl's, or improve block-sha1.

We also use OpenSSL for git-imap-send, AFAICT with no fallback other than "don't use ssl" or "use stunnel".

1. https://www.openssl.org/blog/blog/2017/03/20/license/
2. https://www.openssl.org/docs/faq.html#LEGAL2
3. https://www.apache.org/licenses/GPL-compatibility.html
Next: demerphq
Message 1 of 11 in “Will OpenSSL's license change impact us?”
  1. Ævar Arnfjörð BjarmasonMar 24, 2017
  2. demerphqMar 25, 2017
  3. Ævar Arnfjörð BjarmasonMar 25, 2017
  4. brian m. carlsonMar 25, 2017
  5. Ævar Arnfjörð BjarmasonMar 25, 2017
  6. Jeff KingMar 26, 2017
  7. Ævar Arnfjörð BjarmasonMar 25, 2017
  8. demerphqMar 25, 2017
  9. Ævar Arnfjörð BjarmasonMar 25, 2017
  10. Theodore Ts'oMar 25, 2017
  11. Ævar Arnfjörð BjarmasonMar 25, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.