view xml/en/docs/faq/license_copyright.xml @ 2060:237b67ef69a6

Improved win32 build instructions. Added "--with-openssl-opt=no-asm" argument which is required since OpenSSL 1.0.2, as OpenSSL started to use assembler by default in 1.0.0 and then broke builds with MASM in OpenSSL 1.0.2 (ticket #1396). While here, added "--with-debug", added missing "--http-scgi-temp-path" and "--http-uwsgi-temp-path", updated OpenSSL to 1.0.2l, switched to slightly more readable one-argument-per-line style in configure example, added indentation to continuation lines, removed useless "--builddir=objs" argument ("objs" is the default), and removed useless "-f objs/Makefile" argument in nmake (nginx generates appropriate Makefile in the current directory).
author Maxim Dounin <mdounin@mdounin.ru>
date Tue, 17 Oct 2017 17:57:36 +0300
parents ddec437b692b
children a841077735f9
line wrap: on
line source

<!--
  Copyright (C) Nginx, Inc.
  -->

<!DOCTYPE article SYSTEM "../../../../dtd/article.dtd">

<article name="How can nginx copyright be acknowledged
               when using nginx as part of a proprietary
               software distribution?"
         link="/en/docs/faq/license_copyright.html"
         lang="en"
         rev="1">

<section>

<para>
<initial>Q:</initial>
I’d like to use nginx distribution as part of my proprietary
software package. How can nginx copyright be acknowledged
when using nginx as part of a proprietary software distribution?
</para>

<para>
&nbsp;
</para>

<para>
<initial>A:</initial>
The text below should be added to your license conditions,
followed by the text of the applicable 2-clause BSD license described
<link url="http://nginx.org/LICENSE">here</link>.

<programlisting>
This product contains software provided by Nginx, Inc. and its contributors.
</programlisting>

</para>

<para>
Also, if your build of nginx includes any of the following 3rd party
products: zlib, PCRE, OpenSSL &#8212; it’s worth including their
copyright acknowledgements and disclaimers as well.
</para>

</section>

</article>