punycode licensing

Salz, Rich rsalz at akamai.com
Wed Jul 10 01:31:24 UTC 2019

Thank you for the reply.

>The license under which the OpenSSL software is provided does not require "permission" to be sought for use of the software.
See https://www.openssl.org/source/apache-license-2.0.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openssl.org_source_apache-2Dlicense-2D2.0.txt&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=xXRygChGgiK1BqBdOliLUVY3TL3voFi6oS6EUcMdAaU&s=g7Itj8LyezH-cDY2PLhFY6RkrbcX4b3xX5A7_f9MQvE&e=>

Use, as defined by the license, doesn’t just mean end-users, and it is not limited to compiling, linking, and running executables.  A recipient can make derivative items, redistribute, and so on. All of those things are what OpenSSL would do if it “took in” code into the source base.

So why does the project require permission from other Apache-licensed licensed software? In other words, why will the project not accept and use the rights, covered by copyright and license, that it grants to others?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-project/attachments/20190710/a45357de/attachment-0001.html>

More information about the openssl-project mailing list