| · | ISAAC Random Number Generator
|
| ISAAC has been placed into the public domain by its author, Bob Jenkins in 1996.
|
| -----------------------------------------------------------------------------------------------------------
|
| My random number generator, ISAAC.
|
| (c) Bob Jenkins, March 1996, Public Domain
|
| You may use this code in any way you wish, and it is free. No warrantee.
|
| -----------------------------------------------------------------------------------------------------------
|
| · | RSA Public Key Encryption
|
| The RSA algorithm was patented until September 2000 when RSA® Security Inc. released the algorithm into the public domain. "BEDFORD, Mass., September 6, 2000 -- RSA® Security Inc. (NASDAQ: RSAS) today announced it has released the RSA public key encryption algorithm into the public domain, allowing anyone to create products that incorporate their own implementation of the algorithm." At the time of writing a copy of this statement can be found at http://www.rsasecurity.com/news/pr/000906-1.html
|
| The Twofish block cipher by Counterpane Labs was developed and analyzed by Bruce Schneier, John Kelsey, Doug Whiting, David Wagner, Chris Hall and Niels Ferguson. Twofish was one of the five Advanced Encryption Standard finalists. At the time of writing the Twofish homepage can be found at http://www.counterpane.com/twofish.html. The cipher has been made available to the general public by the following statement on http://www.counterpane.com/about-twofish.html :
|
| " Twofish is unpatented, and the source code is uncopyrighted and license-free; it is free for all uses. Everyone is welcome to download Twofish and use it in their application. There are no rules about use, although I would appreciate being notified of any commercial applications using the algorithm so that I can list them on this website. "
|
| · | ZLIB Compression Library
|
| ZLIB is a lossless data-compression library written by Jean-loup Gailly and Mark Adler. ZLIB is made
|
| " Copyright (C) 1995-2002 Jean-loup Gailly and Mark Adler
|
| This software is provided 'as-is', without any express or implied
|
| warranty. In no event will the authors be held liable for any damages
|
| arising from the use of this software.
|
| Permission is granted to anyone to use this software for any purpose,
|
| including commercial applications, and to alter it and redistribute it
|
| freely, subject to the following restrictions:
|
| 1. The origin of this software must not be misrepresented; you must not
|
| claim that you wrote the original software. If you use this software
|
| in a product, an acknowledgment in the product documentation would be
|
| appreciated but is not required.
|
| 2. Altered source versions must be plainly marked as such, and must not be
|
| misrepresented as being the original software.
|
| 3. This notice may not be removed or altered from any source distribution.
|
| Jean-loup Gailly jloup@gzip.org
|
| Mark Adler madler@alumni.caltech.edu "
|
| The RIPE message digest was written by Antoon Bosselaers for Katholieke Universiteit Leuven, Department of Electrical Engineering ESAT/COSIC, Belgium. License conditions ask us to quote the following :
|
| " RIPEMD-160 software written by Antoon Bosselaers,
|
| available at http://www.esat.kuleuven.ac.be/~cosicart/ps/AB-9601/ "
|
| · | Viking Art - SecExMail Logo
|
| Katja Bengtsson of Brisbane, Australia ( katja@offshoremailroom.com )
|
| SecExMail contains cryptographic software from the OpenSSL project at www.openssl.org which is licensed under a "BSD-style" open source licenses. These licenses asks us to state the following :
|
| "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
|
| "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com)."
|
| SecExMail is an independent, derived work and no endorsement of SecExMail by the OpenSSL project is implied. The full text of the OpenSSL license and the original SSLeay License is reproduced below.
|
| ====================================================================
|
| Copyright (c) 1998-2001 The OpenSSL Project. All rights reserved.
|
| Redistribution and use in source and binary forms, with or without
|
| modification, are permitted provided that the following conditions
|
| 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
|
| 3. All advertising materials mentioning features or use of this
|
| software must display the following acknowledgment:
|
| "This product includes software developed by the OpenSSL Project
|
| for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
|
| 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
|
| endorse or promote products derived from this software without
|
| prior written permission. For written permission, please contact
|
| openssl-core@openssl.org.
|
| 5. Products derived from this software may not be called "OpenSSL"
|
| nor may "OpenSSL" appear in their names without prior written
|
| permission of the OpenSSL Project.
|
| 6. Redistributions of any form whatsoever must retain the following
|
| "This product includes software developed by the OpenSSL Project
|
| for use in the OpenSSL Toolkit (http://www.openssl.org/)"
|
| THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
|
| EXPRESSED 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 OpenSSL PROJECT OR
|
| ITS 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.
|
| ====================================================================
|
| This product includes cryptographic software written by Eric Young
|
| (eay@cryptsoft.com). This product includes software written by Tim
|
| Hudson (tjh@cryptsoft.com).
|
| Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
|
| This package is an SSL implementation written
|
| by Eric Young (eay@cryptsoft.com).
|
| The implementation was written so as to conform with Netscapes SSL.
|
| This library is free for commercial and non-commercial use as long as
|
| the following conditions are adhered to. The following conditions
|
| apply to all code found in this distribution, be it the RC4, RSA,
|
| lhash, DES, etc., code; not just the SSL code. The SSL documentation
|
| included with this distribution is covered by the same copyright terms
|
| except that the holder is Tim Hudson (tjh@cryptsoft.com).
|
| Copyright remains Eric Young's, and as such any Copyright notices in
|
| the code are not to be removed.
|
| If this package is used in a product, Eric Young should be given attribution
|
| as the author of the parts of the library used.
|
| This can be in the form of a textual message at program startup or
|
| in documentation (online or textual) provided with the package.
|
| Redistribution and use in source and binary forms, with or without
|
| modification, are permitted provided that the following conditions
|
| 1. Redistributions of source code must retain the 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. All advertising materials mentioning features or use of this software
|
| must display the following acknowledgement:
|
| "This product includes cryptographic software written by
|
| Eric Young (eay@cryptsoft.com)"
|
| The word 'cryptographic' can be left out if the routines from the library
|
| being used are not cryptographic related :-).
|
| 4. If you include any Windows specific code (or a derivative thereof) from
|
| the apps directory (application code) you must include an acknowledgement:
|
| "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
|
| THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``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 AUTHOR 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
|
| The licence and distribution terms for any publicly available version or
|
| derivative of this code cannot be changed. i.e. this code cannot simply be
|
| copied and put under another distribution licence
|
| [including the GNU Public Licence.]
|
| Chris Kohlhepp and Mark Robertson, Bytefusion Ltd.
|
|
|