Multi Service Edge Device HL950
Administrator’s Guide
Page 137 (159)
EN/LZT 108 5995 R3
June
2003
9 Important
Information
This chapter provides information about product care, license agreements and regulatory information.
9.1
Product Care and Maintenance
NOTE!
Read this information before using your Ericsson Multi Service Edge Device HL950 for safe
and efficient use.
Your Multi Service Edge Device HL950 is a highly sophisticated electronic device. To get the most
out of it, be sure to read the following text about product care, safety and efficient use.
Do not
expose the product to liquid or moisture.
Do not
expose the product to extreme temperatures, neither hot nor cold.
Do not
expose the product to lit candles, cigarettes, cigars, open flames, etc.
Do not
drop, throw or try to bend the product since rough treatment could damage it.
Do not
allow children to play with the equipment as it contains small parts that could be detached and
create a choking hazard.
Use only
original Ericsson components and replacement parts. Failure to do so may result in
performance loss, damage to the product, fire, electric shock or injury, and will invalidate the
warranty.
Treat the product with care
, keep it in a clean and dust free place. Use only a soft, damp cloth to
clean the product.
9.2 Freeware
Licenses
9.2.1
Java Runtime Environment, JRE v1.4.1
This product includes code licensed from RSA Security, Inc.
Some portions licensed from IBM are available at
http://oss.software.ibm.com/icu4j/
9.2.2 OpenSSH
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.
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".
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