You are free to use cryptlib subject to the restrictions given below.
If you use cryptlib, you must give the authors credit in your software and/or documentation. | |
If you make any changes to the code, you should send a copy of the changes to the author to allow them to be integrated into the code. This is to allow a central consistent version to be maintained. | |
Any software you create with this code may not be merely a set or subset of cryptlib, with or without minor added functionality or a different interface. In particular you can't distribute cryptlib (or any modified form of it) as your own encryption product. This is to stop people adding their own wrappers and selling it as "their" encryption product. |
cryptlib is distributed under a dual license that allows free, open-source use under a GPL-like license and closed-source use under a standard commercial license. In addition, cryptlib is free for use in low-cost, non-open-source applications such as shareware, and for personal and research use. Exact terms are given at the bottom of this page.
cryptlib contains contributions from various open-source developers, see the acknowledgements section of the manual for details.
This software is OSI Certified Open Source Software. OSI Certified is a certification mark of the Open Source Initiative.
The current cryptlib release is cryptlib 3.4.8. cryptlib includes a 380-page user's guide and manual in PDF format, this is distributed separately from the code.
cryptlib is distributed in standard Zip format and can be extracted on virtually all target operating systems. Before working with it, you should read at least the Installation section of the manual, which covers details on installing the software on different platforms (under Unix you need to unzip with the -a option).
Ralf Senderek, who also provided the cryptlibConverter scripts, has a web page with various crypto tools built with cryptlib including a file encryption tool and a public/private key management tool.
Wolfgang Gothier has a web page with Visual Basic and Delphi add-ons for cryptlib that provide more VB- and Delphi-like interfaces than the standard one, as well as sample code in VB and Delphi.
.cryptlib is distributed under a dual license that allows free, open-source use under a GPL-compatible license and closed-source use under a standard commercial license. The GPL-compatible license (a.k.a. the Sleepycat license) is given below. A good overview and background behind the Sleepycat license, which also applies for cryptlib, is also available.
Copyright 1992-2018 Peter Gutmann. 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. Redistributions in any form must be accompanied by information on how to obtain complete source code for the cryptlib software and any accompanying software that uses the cryptlib software. The source code must either be included in the distribution or be available for no more than the cost of distribution, and must be freely redistributable under reasonable conditions. For an executable file, complete source code means the source code for all modules it contains or uses. It does not include source code for modules or files that typically accompany the major components of the operating system on which the executable file runs. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR 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.
Note that decoupling the software from the user, for example by running in a SaaS configuration, does not exempt you from these requirements.
If you're unable to comply with the above license then the following, alternate usage conditions apply:
Any large-scale commercial use of cryptlib requires a license. "Large-scale commercial use" means any revenue-generating purpose such as use for company-internal purposes, or use of cryptlib in an application or product, with a total gross revenue of over US$5,000. This allows cryptlib to be used in freeware and shareware applications, for evaluation and research purposes, and for non-revenue-generating or personal use without charge. In addition the author reserves the right to grant free licenses for commercial use in special cases (for example where there is a general benefit to the public), contact the author for details if you think you qualify.
There is a very low volume mailing list available that covers cryptlib development and usage and implementation details. To subscribe, send mail to the list administrator with the word "subscribe" in the message body. You should receive a reply informing you that you've been added to the list. General questions on cryptlib are answered in the cryptlib FAQ. You can also access the list via the web (note that this is a one-way gateway from the mailing list, you can't post to the list from the web/news interface but have to subscribe to the list by following the instructions above). An archive of older mailing-list postings is also available.
cryptlib 3.4.3 (and by extension all earlier versions) has been end-of-lifed. Anyone who has a support contract for cryptlib version 3.4.3 or older will continue to receive support until the contract is up for renewal, after which you must upgrade to the current 3.4.x release. Anyone without a support contract will no longer be able to receive support for 3.4.3 or earlier versions.