Sophos Endpoint Security and Control – Versionsinfo

Wartungsphase

Endpoint Security and Control 9.5 befindet sich jetzt in der Wartungsphase. Die Version wird zwar noch unterstützt und die Threat Detection Engine und Threat-Erkennungsdaten werden weiterhin monatlich aktualisiert, es werden jedoch keine neuen Funktionen mehr entwickelt. Hier können Sie sich über Produkteinstellungen informieren: http://www.sophos.com/de-de/support/retirements.aspx.

Sie können ein Upgrade auf Version 10 durchführen.

Versionsnummern

Sophos Anti-Virus 9.5.7
Sophos Client Firewall 2.5.0
Sophos AutoUpdate 2.5.13

So ermitteln Sie die Version der Threat Detection Engine und Threat-Erkennungsdaten:

  1. Öffnen Sie Endpoint Security and Control.
  2. Klicken Sie auf der linken Seite im Bereich Hilfe und Informationen auf Produktinfo.
  3. Klicken Sie unter Antivirus und HIPS auf Software.
Hinweis: Einige in dieser Versionsinfo erwähnte Funktionen sind nur auf verwalteten Computern oder für entsprechende Lizenzinhaber verfügbar.

Neu in dieser Version

  • Threat Detection Engine und Threat-Daten wurden aktualisiert.

Behobene Probleme

  • (DEF85900) Die "Address Space Layout Randomization (ASLR)"-Kennzeichnung "/DYNAMICBASE" verweist nicht auf Sophos Binärdateien, insbesondere wenn diese in Nicht-Sophos-Prozessen geladen werden.
  • (DEF85510) Sicherheitslücke in Zusammenhang mit Cross Site Scripting (XSS), wenn Sophos Browser Hilfsobjekt (BHO) schädliche Web-Inhalte blockiert.

Bekannte Probleme

Im Folgenden werden die bei Veröffentlichung der Software bekannten Probleme zusammengefasst. Eine aktuelle Übersicht hierzu finden Sie zudem unter http://www.sophos.com/de-de/support/knowledgebase/110579.aspx.

Standalone Installer

  • (CR26760) Die Installation von Sophos Client Firewall über einen Windows Installer (.msi-Datei) schlägt unter Vista bei aktivierter Benutzerkontosteuerung unerwartet fehl.

Sophos Anti-Virus

  • Das Abrufen von URLs wird beim Web-Schutz durch LSPs (Layered Service Provider) vereinfacht. Wenn der Web-Schutz bei nicht unterstütztem LSP aktiviert ist, beeinträchtigt dies unter Umständen die Stabilität des Systems. Wenn ein bekanntermaßen nicht kompatibler LSP bereits auf dem Computer installiert wurde, wird der Sophos LSP nicht installiert. Nähere Informationen entnehmen Sie bitte dem Support-Artikel http://www.sophos.com/de-de/support/knowledgebase/111203.aspx.

  • (DEF59971) Die Kennungen von Protokollmeldungen des Web-Schutzes können nicht zugeordnet werden. Beispiel: "Web-Anfrage "www.beispiel.de" wurde für Benutzer PC123\Tim blockiert". "Mal/HTMLGen-A" wurde auf dieser Website erkannt, Referenzkennung 19". Diese Kennungen wurden nicht definiert.
  • (DEF57112) Unter folgenden Umständen werden On-Access-Scans bei einem Downgrade von Sophos Endpoint Security and Control 9.5 deaktiviert:
    • Auf dem Computer war zu ein früheren Zeitpunkt Sophos Anti-Virus 6 oder früher installiert.
    • Sie haben ein Upgrade auf SESC 9.5 durchgeführt.
    • Sie versuchen, auf SESC 9.X oder abzurüsten.

    Eine Fehlermeldung weist darauf hin, dass der Computer möglicherweise nicht vor Malware geschützt ist. Das Problem lässt sich durch Löschen der folgenden Registrierungseinträge und einem Neustart des SAV Service-Dienstes beheben.

    HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\SAVI

    HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\SAVI\SAV-0000 bis SAV-NNNN

    (NNNN ist dabei der letzte Schlüssel).

  • (DEF56055) Wenn Sie die DNS-Liste in der Systemsteuerung manuell ändern, funktioniert Sophos Live-Schutz nicht mehr. Starten Sie den Sophos Anti-Virus-Dienst neu, um das Problem zu umgehen.
  • (WKI55631) Der Web-Schutz unterstützt Windows XP Service Pack 1 und Windows 2000 Service Pack 3 nicht. Sie können das Problem durch Installation des aktuellen Service Packs für das Betriebssystem installieren.
  • (DEF20694) Wenn Sophos Anti-Virus eine Controlled Application in einer Remote-Freigabe erkennt, zeigt die Meldung immer an, dass die Anwendung auf dem lokalen Computer erkannt wurde.
  • (DEF18144, DEF16510) Bei einigen Browser-Erweiterungen (z.B. Google Gears und RealPlayer 11 Download und Aufnahme) treten Probleme auf, die Sophos bekannt sind. Es empfiehlt sich, diese Browser-Erweiterungen zu deaktivieren.

Sophos Device Control

  • (DEF39454) Wenn ein Benutzer ohne Administratorrechte in Windows Vista ein Gerät anschließt, das von Sophos Device Control gesperrt wird, wird zur Eingabe von Administratorzugangsdaten aufgefordert. Dem Benutzer wird der Zugriff auf das Gerät verweigert, auch wenn die geforderten Zugangsdaten eingegeben werden. Wenn keine Administratorzugangsdaten eingegeben werden, wird kein Alert an die Management Console gesendet.

Sophos Client Firewall

  • (DEF61237) Wenn Sophos Endpoint Security and Control auf Version 9.5 upgegradet wird, wird in Sophos Client Firewall unter Umständen eine Meldung angezeigt, in der Netzwerkzugang für den versteckten Prozess SAVProxy.exe angefordert wird, der von %Programme%\Sophos\AutoUpdate\ALMon.exe gestartet wurde. Sie können das Problem umgehen, indem Sie allen von ALMon.exe gestarteten Prozessen Netzwerkzugriff gewähren und anschließend den Computer neu starten.
  • (DEF59219) Prüfsummen, die über das Dialogfeld Firewall-Konfiguration zu Systemanwendungen im Ordner System32 hinzugefügt werden sollen, werden zur entsprechenden Datei im Ordner SysWOW64 hinzugefügt. Sie können beide Prüfsummen im interaktiven Modus hinzufügen.
  • (WKI55953) Bei der Installation von Sophos Client Firewall wird vorübergehend die Verbindung zu allen Netzwerkadaptern unterbrochen. Netzwerkverbindungen sind bis zu 20 Sekunden lang nicht mehr verfügbar und die Verbindung zu vernetzten Anwendungen, wie Microsoft Remote Desktop, wird getrennt.
  • (WKI32813) Sophos Client Firewall meldet Internet Explorer 8 als versteckten Prozess. Nähere Informationen entnehmen Sie bitte dem Support-Artikel http://www.sophos.com/de-de/support/knowledgebase/54899.aspx.
  • (DEF18752) Wenn unter Windows XP Sophos Client Firewall und VMware ausgeführt werden, können virtuelle Systeme mitunter nicht auf das Netzwerk zugreifen. Nähere Informationen entnehmen Sie bitte dem Support-Artikel http://www.sophos.com/de-de/support/knowledgebase/15434.aspx.
  • (DEF53171) Sophos Client Firewall unterstützt das „Mobile Broadband“-Treibermodell in Windows 7 nicht.
  • (DEF16039) Sophos Client Firewall sperrt mitunter vertrauenswürdige Anwendungen.
  • (CR27434) Bei Änderungen der Regeln im Configuration Editor werden Datenpakete, die von den Regeln nicht betroffen sind, kurzzeitig blockiert. Dies macht sich möglicherweise beim Senden von Alerts an die Management-Konsole bemerkbar.
  • (CR27073) IPv6-Adressen/Schnittstellen im Datenbewegungsprotokoll werden nicht im IPv6-Format protokolliert.
  • (CR26950) Nach dem Hinzufügen und Löschen einer Anwendung im oberen Bereich der Registerkarte Prozesse kann nicht mit der Tabulatortaste navigiert werden.
  • (CR26248) Wenn das Protokoll in einer Ansicht angezeigt wird, die automatisch aktualisiert wird (z.B. Zugelassene Verbindungen), wird die Ansicht bei hoher Auslastung des Diensts nicht mehr aktualisiert. Nach dem Wechsel in eine andere Ansicht und zurück, funktioniert die automatische Aktualisierung einwandfrei.
  • (CR25569) Auch wenn Regeln ein-und ausgehenden IPv6-Datenverkehr sperren, wird IPv6-Datenverkehr nicht zurückgeschleift.

Weitere Informationen

  • Auf Systemen mit Windows 2000 und Internet Explorer 5 oder 6 wird der Zugriff auf gesperrte Seiten über Windows Explorer vom Web-Schutz nicht unterbunden.
  • Sophos Device Control sperrt keine Wechseldatenträger, die als Systemlaufwerke verwendet werden, da dies die Stabilität des Betriebssystems beeinträchtigt.
  • Einzelplatzinstallationen von Endpoint Security and Control unterstützen Windows Server Core nicht.
  • Verwaltete und Einzelplatzinstallationen von Endpoint Security and Control unterstützen Windows Server Core Hyper-V nicht.
  • Freigegebene Windows-Komponenten

    Wenn Sie Sophos Software installieren, werden einige Windows Komponenten, die auch von Sophos-fremder Software verwendet werden, installier oder upgegradet:

    Sophos Software Windows-Komponente
    Name Dateinamen Versionen Einbezug in Sophos Software
    Sophos Anti-Virus Microsoft XML Core Services msxml4.dll 4.30.2100.0 September 2009
    msxml4r.dll 4.30.2100.0 September 2009
    ATL Library ATL80.dll 8.0.50727.4053 Juni 2007
    Microsoft Visual C/C++ Runtime Libraries msvcm80.dll 8.0.50727.4053 Juni 2007
    msvcp80.dll 8.0.50727.4053 Juni 2007
    msvcr80.dll 8.0.50727.4053 Juni 2007
    Sophos AutoUpdate Windows Installer msi.dll 2.0.2600.2 November 2003
    msiexec.exe 2.0.2600.2 November 2003
    msihnd.dll 2.0.2600.2 November 2003
    msimain.sdb November 2003
    msimsg.dll 2.0.2600.2 November 2003
    msisip.dll 2.0.2600.2 November 2003
    msls31.dll 3.10.337.0 November 2003
    mspatcha.dll 5.1.2600.0 November 2003
    riched20.dll 5.30.23.1200 November 2003
    sdbapiU.dll 1.0.0.1 November 2003
    shfolder.dll 5.0.2919.20 November 2003
    usp10.dll 1.325.2180.1 November 2003
    Sophos Client Firewall Microsoft XML Core Services msxml4.dll 4.30.2100.0 September 2009
    msxml4r.dll 4.30.2100.0 September 2009
    Microsoft Visual C/C++ Runtime Libraries msvcm80.dll 8.0.50727.4053 März 2010
    msvcp80.dll 8.0.50727.4053 März 2010
    msvcr80.dll 8.0.50727.4053 März 2010

Technischer Support

Sie können sich wie folgt an den technischen Support von Sophos wenden:

Rechtlicher Hinweis

Copyright © 2009–2013 Sophos Limited. Alle Rechte vorbehalten. Diese Publikation darf weder elektronisch oder mechanisch reproduziert, elektronisch gespeichert oder übertragen, noch fotokopiert oder aufgenommen werden, es sei denn, Sie verfügen entweder über eine gültige Lizenz, gemäß der die Dokumentation in Übereinstimmung mit dem Lizenzvertrag reproduziert werden darf, oder Sie haben eine schriftliche Genehmigung des Copyright-Inhabers.

Sophos und Sophos Anti-Virus sind eingetragene Marken der Sophos Limited. Alle anderen Produkt- und Unternehmensbezeichnungen sind Marken oder eingetragene Marken der jeweiligen Inhaber.

Common Public License

The Sophos software that is described in this document includes or may include some software programs that are licensed (or sublicensed) to the user under the Common Public License (CPL), which, among other rights, permits the user to have access to the source code. The CPL requires for any software licensed under the terms of the CPL, which is distributed in object code form, that the source code for such software also be made available to the users of the object code form. For any such software covered under the CPL, the source code is available via mail order by submitting a request to Sophos; via email to support@sophos.de or via the web at http://www.sophos.com/de-de/support/contact-support/contact-information.aspx. A copy of the license agreement for any such included software can be found at http://opensource.org/licenses/cpl1.0.php

ConvertUTF

Copyright 2001–2004 Unicode, Inc.

This source code is provided as is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. If this file has been purchased on magnetic or optical media from Unicode, Inc., the sole remedy for any claim will be exchange of defective media within 90 days of receipt.

Unicode, Inc. hereby grants the right to freely use the information supplied in this file in the creation of products supporting the Unicode Standard, and to make copies of this file in any form for internal or external distribution as long as this notice remains attached.

dtoa.c

The author of this software is David M. Gay.

Copyright © 1991, 2000 by Lucent Technologies.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.

Info-ZIP

Copyright © 1990–2005 Info-ZIP. All rights reserved.

For the purposes of this copyright and license, “Info-ZIP” is defined as the following set of individuals:

Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ed Gordon, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Steven M. Schweda, Christian Spieler, Cosmin Truta, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White

This software is provided “as is,” without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use 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. Redistributions of source code must retain the above copyright notice, definition, disclaimer, and this list of conditions.
  2. Redistributions in binary form (compiled executables) must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or disabled.
  3. Altered versions—including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, and dynamic, shared, or static library versions—must be plainly marked as such and must not be misrepresented as being the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases—including, but not limited to, labeling of the altered versions with the names “Info- ZIP” (or any variation thereof, including, but not limited to, different capitalizations), “Pocket UnZip,” “WiZ” or “MacZip” without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s).
  4. Info-ZIP retains the right to use the names “Info-ZIP,” “Zip,” “UnZip,” “UnZipSFX,” “WiZ,” “Pocket UnZip,” “Pocket Zip,” and “MacZip” for its own source and binary releases.

mt19937ar.c

Copyright (c) 1997–2002 Makoto Matsumoto and Takuji Nishimura. 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. The names of its contributors may not 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.

OpenSSL cryptographic toolkit

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL license

Copyright © 1998–2011 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 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. 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 acknowledgment:

    “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).

Original SSLeay license

Copyright © 1995–1998 Eric Young (eay@cryptsoft.com) All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape’s 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 are met:

  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 SUCH DAMAGE.

The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]

Simple ECMAScript Engine

Copyright © 2003, 2004, 2005, 2006, 2007 David Leonard. Alle Rechte vorbehalten.

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 David Leonard 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.

strcasestr.c

Copyright © 1990, 1993 The Regents of the University of California. Alle Rechte vorbehalten.

This code is derived from software contributed to Berkeley by Chris Torek.

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 University 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 REGENTS 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 REGENTS 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.

UnRAR

The source code of UnRAR utility is freeware. This means:

  1. All copyrights to RAR and the utility UnRAR are exclusively owned by the author - Alexander Roshal.
  2. The UnRAR sources may be used in any software to handle RAR archives without limitations free of charge, but cannot be used to re-create the RAR compression algorithm, which is proprietary. Distribution of modified UnRAR sources in separate form or as a part of other software is permitted, provided that it is clearly stated in the documentation and source comments that the code may not be used to develop a RAR (WinRAR) compatible archiver.
  3. The UnRAR utility may be freely distributed. It is allowed to distribute UnRAR inside of other software packages.
  4. THE RAR ARCHIVER AND THE UnRAR UTILITY ARE DISTRIBUTED “AS IS”. NO WARRANTY OF ANY KIND IS EXPRESSED OR IMPLIED. YOU USE AT YOUR OWN RISK. THE AUTHOR WILL NOT BE LIABLE FOR DATA LOSS, DAMAGES, LOSS OF PROFITS OR ANY OTHER KIND OF LOSS WHILE USING OR MISUSING THIS SOFTWARE.
  5. Installing and using the UnRAR utility signifies acceptance of these terms and conditions of the license.
  6. If you don’t agree with terms of the license you must remove UnRAR files from your storage devices and cease to use the utility.

Thank you for your interest in RAR and UnRAR.

Alexander L. Roshal