Note di rilascio di Sophos Endpoint Security and Control

Fase di manutenzione

Endpoint Security and Control versione 9.5 è ora in fase di manutenzione. Sebbene venga ancora supportato e si continuino ad aggiornare, con cadenza mensile, il motore di rilevamento delle minacce e i dati relativi alle minacci, le funzione non verranno ulteriormente sviluppate. Per verificare la data di ritiro, andare alla pagina web http://www.sophos.com/it-it/support/retirements.aspx.

È possibile effettuare l'upgrade alla versione 10.

Numeri di versione

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

Per individuare le versioni del motore di rilevamento delle minacce e dei dati relativi alle minacce:

  1. Aprire Endpoint Security and Control.
  2. Nel riquadro di sinistra, sotto Assistenza e informazioni, cliccare su Visualizza informazioni sul prodotto.
  3. Sotto Anti-virus e HIPS, cliccare su Software.
Nota: alcune delle caratteristiche citate in queste note di rilascio sono disponibili solo nei computer gestiti o se in possesso di una licenza adeguata.

Novità di questo rilascio

  • Il motore di rilevamento delle minacce e i dati relativi alle minacce sono stati aggiornati.

Problemi risolti

  • (DEF85900) Il contrassegno di Address Space Layout Randomization (ASLR) "/DYNAMICBASE" non è impostato sui binari Sophos, in particolare quelli caricati in processi non-Sophos.
  • (DEF85510) Le vulnerabilità relativa a Attiva Filtro XSS (XSS) quando Sophos Browser Helper Object (BHO) blocca contenuto web malevolo.

Problemi noti

La seguente lista include problemi noti al momento del lancio del prodotto. Per un elenco aggiornato, comprendente i problemi riscontrati dopo il rilascio, consultare l'articolo http://www.sophos.com/it-it/support/knowledgebase/110579.aspx.

Programma di installazione su computer autonomo

  • (CR26760) Inaspettatamente l'installazione di Sophos Client Firewall non riesce, se eseguita da un pacchetto Windows Installer (.msi) su Vista con User Access Control abilitato.

Sophos Anti-Virus

  • La protezione web utilizza un LSP (Layered Service Provider) per facilitare le ricerche URL. Quando la protezione web è abilitata in concomitanza con un sistema LSP incompatibile, si possono verificare situazioni di instabilità. Quando un sistema LSP, notoriamente incompatibile, è già installato nel computer, Sophos LSP non viene installato. Per ulteriori informazioni, consultare il link http://www.sophos.com/it-it/support/knowledgebase/111203.aspx.

  • (DEF59971) Web Protection genera messaggi di log con codici di riferimento ID criptici, come ad esempio: "Richiesta web bloccata su "www.example.com" per utente PC123\Tim. 'Mal/HTMLGen-A' è stato rilevato su questo sito, ID di riferimento: 19". Al momento, non sono presenti chiavi accessibili per questi numeri ID.
  • (DEF57112) La scansione in accesso viene disabilitata quando si effettua il downgrade da Sophos Endpoint Security and Control 9.5, se si verificano le seguenti condizioni:
    • In precedenza è stato installato sul computer Sophos Anti-Virus 6 o precedente.
    • È stato effettuato un upgrade a SESC 9.5.
    • Si cerca di eseguire il downgrade di SESC 9.X o precedenti.

    Verrà inoltre visualizzato un messaggio di errore, ed il computer potrebbe non essere protetto dal malware. La soluzione è cancellare i valori della chiave di registro sottostanti e riavviare il servizio SAV.

    HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\SAVI

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

    (dove NNNN è l'ultima chiave).

  • (DEF56055) Se si modifica manualmente l'elenco DNS mediante il Pannello di controllo, Sophos Live Protection smette di funzionare. Per eludere questo problema, riavviare il servizio di Sophos Anti-Virus.
  • (WKI55631) Web protection non supporta Windows XP Service Pack 1 e Windows 2000 Service Pack 3. Per eludere questo problema, installare il service pack più recente del proprio sistema operativo.
  • (DEF20694) Quando Sophos Anti-Virus rileva un'applicazione controllata in una condivisione remota, il relativo allarme indica sempre che tale applicazione è stata rilevata nel computer locale.
  • (DEF18144, DEF16510) Sussistono problemi noti relativi alla scansione del contenuto web con determinate estensioni browser (per es. con Google Gears e RealPlayer 11 Download and Record). Disabilitare tali estensioni browser.

Sophos Device Control

  • (DEF39454) In Windows Vista, se un utente non amministratore inserisce un dispositivo che Sophos Device Control potrebbe bloccare, a tale utente potranno essere richieste le credenziali di amministratore. L'utente potrebbe vedersi negato l'accesso al dispositivo, sia che inserisca le credenziali richieste sia che non lo faccia. Se non inserisce le credenziali richieste non viene comunque inviato alcun allarme alla console di gestione.

Sophos Client Firewall

  • (DEF61237) Quando si effettua l'upgrade di Sophos Endpoint Security and Control alla versione 9.5, può venire visualizzato un messaggio di Sophos Client Firewall che richiede accesso per il processo nascosto SAVProxy.exe, avviato da %ProgramFiles%\Sophos\AutoUpdate\ALMon.exe. Per eludere il problema, basta consentire l'accesso alla rete per tutti i processi nascosti avviati da ALMon.exe, e successivamente riavviare il computer.
  • (DEF59219) Se si cerca di aggiungere un checksum per alcune applicazioni di sistema nella cartella System32 utilizzando la finestra di dialogo Configurazione firewall, viene invece aggiunto un checksum per il file corrispondente nella cartella SysWOW64. È comunque possibile aggiungere entrambi i checksum in questione in modalità interattiva.
  • (WKI55953) Quando viene installato Sophos Client Firewall, vengono temporaneamente disconnesse tutte le schede di rete. Per questo motivo le connessioni di rete risultano non disponibili per un tempo di circa 20 secondi, e le applicazioni di rete, quali Microsoft Remote Desktop, vengono disconnesse.
  • (WKI32813) Sophos Client Firewall rileva Internet Explorer 8 come processo nascosto. Per ulteriori informazioni, consultare il link http://www.sophos.com/it-it/support/knowledgebase/54899.aspx.
  • (DEF18752) Quando Windows XP esegue Sophos Client Firewall e VMware, i computer virtuali potrebbero non riuscire ad accedere alla rete. Per ulteriori informazioni, consultare il link http://www.sophos.com/it-it/support/knowledgebase/15434.aspx.
  • (DEF53171) Sophos Client Firewall, in Windows versione 7, non supporta il modello dirver a "banda larga mobile".
  • (DEF16039) Sophos Client Firewall potrebbe occasionalmente bloccare applicazioni consentite.
  • (CR27434) Quando le regole nell'editor di configurazione vengono modificate, pacchetti di traffico che non dovrebbero risentire di tali modifiche potrebbero essere bloccati per un breve periodo di tempo durante l'aggiornamento delle regole. Ciò dovrebbe verificarsi per un periodo di tempo molto limitato, ma potrebbe essere ugualmente evidente nel caso in cui venissero inviati allarmi alla console di gestione.
  • (CR27073) Indirizzi/interfacce IPv6 non sono registrati nel log del traffico col formato IPv6.
  • (CR26950) Non è possibile navigare utilizzando il tasto Tab dopo l'aggiunta e la cancellazione di un'applicazione nella parte alta della scheda Processi.
  • (CR26248) Quando il log viene visualizzato in una vista che si autoaggiorna (quale Connessioni consentite), la vista potrebbe smettere di aggiornarsi se il servizio risulta esposto a un carico elevato. Passando a un'altra vista e poi tornando a quella precedente, l'autoaggiornamento riprende ad operare.
  • (CR25569) Sebbene le regole che blocca il traffico IPv6 blocca il traffico in entrata e uscita dal computer, non bloccano invece il traffico loopback IPv6.

Informazioni aggiuntive

  • Su sistemi Windows 2000 che eseguono Internet Explorer 5 o 6, Web Protection consente l'accesso a siti bloccati mediante Windows Explorer.
  • Sophos Device Control non blocca i dispositivi di memorizzazione rimovibili che vengono utilizzati come unità di sistema, dal momento che ciò può destabilizzare il sistema operativo.
  • Le installazioni autonome di Endpoint Security and Control non supportano Windows Server Core.
  • Le installazioni gestite ed autonome di Endpoint Security and Control non supportano Windows Server Core Hyper-V.
  • Componenti condivisi di Windows

    Quando viene installato il software Sophos, vengono installati o aggiornati anche alcuni componenti di Windows che potrebbero essere utilizzati da software non-Sophos:

    Software Sophos Componente condiviso di Sophos
    Nome Nomi file Versioni Data di inclusione nel software Sophos
    Sophos Anti-Virus Microsoft XML Core Services msxml4.dll 4.30.2100.0 Settembre 2009
    msxml4r.dll 4.30.2100.0 Settembre 2009
    ATL Library ATL80.dll 8.0.50727.4053 Giugno 2007
    Microsoft Visual C/C++ Runtime Library msvcm80.dll 8.0.50727.4053 Giugno 2007
    msvcp80.dll 8.0.50727.4053 Giugno 2007
    msvcr80.dll 8.0.50727.4053 Giugno 2007
    Sophos AutoUpdate Windows Installer msi.dll 2.0.2600.2 Novembre 2003
    msiexec.exe 2.0.2600.2 Novembre 2003
    msihnd.dll 2.0.2600.2 Novembre 2003
    msimain.sdb N.d. Novembre 2003
    msimsg.dll 2.0.2600.2 Novembre 2003
    msisip.dll 2.0.2600.2 Novembre 2003
    msls31.dll 3.10.337.0 Novembre 2003
    mspatcha.dll 5.1.2600.0 Novembre 2003
    riched20.dll 5.30.23.1200 Novembre 2003
    sdbapiU.dll 1.0.0.1 Novembre 2003
    shfolder.dll 5.0.2919.20 Novembre 2003
    usp10.dll 1.325.2180.1 Novembre 2003
    Sophos Client Firewall Microsoft XML Core Services msxml4.dll 4.30.2100.0 Settembre 2009
    msxml4r.dll 4.30.2100.0 Settembre 2009
    Microsoft Visual C/C++ Runtime Library msvcm80.dll 8.0.50727.4053 Marzo 2010
    msvcp80.dll 8.0.50727.4053 Marzo 2010
    msvcr80.dll 8.0.50727,4053 Marzo 2010

Supporto tecnico

È possibile ricevere supporto tecnico per i prodotti Sophos in uno dei seguenti modi:

Note legali

Copyright © 2009-2013 Sophos Limited. Tutti i diritti riservati. Nessuna parte di questa pubblicazione può essere riprodotta, memorizzata in un sistema di recupero informazioni, o trasmessa, in qualsiasi forma o con qualsiasi mezzo, elettronico o meccanico, inclusi le fotocopie, la registrazione e altri mezzi, salvo che da un licenziatario autorizzato a riprodurre la documentazione in conformità con i termini della licenza, oppure previa autorizzazione scritta del titolare dei diritti d'autore.

Sophos e Sophos Anti-Virus sono marchi registrati di Sophos Limited. Tutti gli altri nomi citati di società e prodotti sono marchi o marchi registrati dei rispettivi titolari.

Common Public License

Il software Sophos descritto in questo documento comprende o può comprendere programmi di software concessi in licenza (o sottolicenza) all'utente secondo i termini della Common Public License (CPL), la quale, tra gli altri diritti, permette all'utente di avere accesso al codice sorgente. La CPL richiede, per qualsiasi software concesso in licenza secondo i termini della stessa, e distribuito in formato codice oggetto, che il codice sorgente di tale software venga messo a disposizione anche degli altri utenti del formato codice oggetto. Per qualsiasi software che rientri nei termini della CPL, il codice sorgente è disponibile tramite ordine postale inviandone richiesta a Sophos; per e-mail a support@sophos.com o tramite internet su http://www.sophos.com/it-it/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 licence 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. 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. 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. All rights reserved.

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