Cisco Cisco ASA 5555-X Adaptive Security Appliance - No Payload Encryption Licensing Information
7
Open Source Software Licenses for ASA and PIX Security Appliances, Version 8.0
OL-13014-01
Introduction
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
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.
BSD 1.0 License
This file is part of the OpenSSH software.
The licences which components of this software fall under are as follows. First, we will summarize and
say that all components are under a BSD licence, or a licence more free than that.
say that all components are under a BSD licence, or a licence more free than that.
OpenSSH contains no GPL code.
1.
Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
All rights reserved
As far as I am concerned, the code I have written for this software can be used freely for any purpose.
Any derived versions of this software must be clearly marked as such, and if the derived work is
incompatible with the protocol description in the RFC file, it must be called by a name other than
“ssh” or “Secure Shell”.
Any derived versions of this software must be clearly marked as such, and if the derived work is
incompatible with the protocol description in the RFC file, it must be called by a name other than
“ssh” or “Secure Shell”.
[Tatu continues]
However, I am not implying to give any licenses to any patents or copyrights held by third parties,
and the software includes parts that are not under my direct control. As far as I know, all included
source code is used in accordance with the relevant license agreements and can be used freely for
any purpose (the GNU license being the most restrictive); see below for details.
and the software includes parts that are not under my direct control. As far as I know, all included
source code is used in accordance with the relevant license agreements and can be used freely for
any purpose (the GNU license being the most restrictive); see below for details.
[However, none of that term is relevant at this point in time. All of these restrictively licensed
software components which he talks about have been removed from OpenSSH, i.e.,
software components which he talks about have been removed from OpenSSH, i.e.,
•
RSA is no longer included, found in the OpenSSL library
•
IDEA is no longer included, its use is deprecated
•
DES is now external, in the OpenSSL library
•
GMP is no longer used, and instead we call BN code from OpenSSL
•
Zlib is now external, in a library
•
The make-ssh-known-hosts script is no longer included
•
TSS has been removed
•
MD5 is now external, in the OpenSSL library
•
RC4 support has been replaced with ARC4 support from OpenSSL
•
Blowfish is now external, in the OpenSSL library
[The licence continues]
Note that any information and cryptographic algorithms used in this software are publicly available
on the Internet and at any major bookstore, scientific library, and patent office worldwide. More
information can be found e.g. at
on the Internet and at any major bookstore, scientific library, and patent office worldwide. More
information can be found e.g. at
http://www.cs.hut.fi/crypto
.