Licensing Information

Submitting recipes to SecureProgramming.com

Thank you very much for taking part in the SecureProgramming.com web site, and submitting your recipe.

Recipes that are contributed to the SecureProgramming.com web site and approved by the site's editors are and will be freely available to all visitors to the site. SecureProgramming.com will make the code and explanations available under the same license that governs the use of code from The Secure Programming Cookbook for C and C++ (see below).

By submitting a recipe, you are agreeing to the following terms:

1. You own the copyright to your own code and explanation. This means that you can make whatever additional use of that code and explanation that you choose.
2. All submitted material will be made freely available on the SecureProgramming.com web site. Code will be available under the BSD license, as discussed below.
3. The SecureProgramming.com web site editors may edit, add to, and delete material from the submitted material in order to ensure technical and editorial quality control.
4. The site maintainers may choose to publish a selection of recipes from this site in book format. If the maintainers choose to publish your recipe, you will receive a free copy of the book and will be acknowledged by name in the book, as long as you provide a valid email address with your submission.
5. While you own the copyright to your own material, the publisher of any book as above will obtain the copyright to the compilation; that is, to the book as a book. The publisher has the right to print, publish, distribute and sell copies of the book, and works derived from the book, in printed form and in electronic media, to translate it, and to license others to do so, for the duration of the copyright in the book, in all languages, throughout the world.

Use of code

The code on this web site and in the books associated with this web site is available with the intention that it helps people get their job done. In general, you may use the code in the book in your programs and documentation. You do not need to contact us for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from the book does not need permission. Selling or distributing a CD-ROM of examples from O'Reilly books requires permission from O'Reilly. Answering a question by citing the book and quoting example code does not require permission. Incorporating a significant amount of example code from the book into your product's documentation requires permission.

Credit to the original authors is always appreciated, but not required.

If you have any worry that your use would not fall under the usage statement above, then you can alternatively agree to the terms of the BSD license, which amounts to attaching the following text to the code listing (replacing the copyright holder and year of authorship as appropriate):

Copyright © <YEAR>, <OWNER> All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met: 

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.

3. Neither the name of the <OWNER> nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

If you feel your use would fall outside the permission given above, feel free to contact O'Reilly for permission on book content: rights@oreilly.com, or the web site owners for permission on site content.