Sophos Anti-Virus für Mac OS X – Versionsinfo

Versionsnummern

Komponente Version
Sophos Anti-Virus 4.9.42
Threat Detection Engine 3.15.0
Threat-Daten 4.61, Januar 2011

Einstellung von Sophos Anti-Virus

Diese Produktversion wird demnächst eingestellt. Ab März 2011 wird das Produkt nicht mehr upgedatet. Wenn Sie mit Mac OS X 10.4 oder höher arbeiten, können Sie kostenlos auf Sophos Anti-Virus 7 aufrüsten. Ferner wird Mac OS X 10.3 und früher demnächst nicht mehr von Sophos unterstützt.

Nähere Informationen entnehmen Sie bitte dem Support-Artikel 111931 (http://www.sophos.de/support/knowledgebase/article/111931.html).

Neu in dieser Version

  • Threat Detection Engine und Threat-Daten wurden aktualisiert.

Bekannte Probleme

  • Wenn beim sofortigen Scannen auf OS X 10.4 eine infizierte Datei in einen Quarantäne-Ordner verschoben oder kopiert wird, fängt der On-Access-Scanner diesen Vorgang ab, da Spotlight den Quarantäne-Ordner indiziert, wenn eine Datei dort abgelegt wird. Um dies zu umgehen, fügen Sie in den Spotlight-Eigenschaften den Quarantäne-Ordner zur Liste ausgeschlossener Ordner hinzu.
  • Sollten Sie folgende Konfigurationsänderungen auf der Seite "Sophos Anti-Virus Update-Einstellungen" vornehmen, lösen diese nicht in Sophos Enterprise Console die Meldung "Abweichend von Richtlinie" aus:
    • Update über einen Secondary Server deaktivieren.
    • Einstellen des primären oder sekundären Proxyservers auf Systemeinstellungen des Proxyservers oder Keinen Proxy verwenden.
  • Wenn Sie auf Intel-basierten Macs auf das Sophos Anti-Virus-Symbol in der System-Statusleiste klicken und Über Sophos Anti-Virus wählen, wird das Über-Fenster immer hinter dem vordersten Fenster angezeigt.
  • Wenn Sie Sophos Anti-Virus von einem Server aus auf einem Macintosh-Computer mit Mac OS X 10.3 installieren, kann eine Fehlermeldung angezeigt werden, dass Sie den Installer nicht von einem Netzwerkvolume aus starten können. Der Grund dafür ist, dass Mac OS X 10.3 Dateiberechtigungen für den Zugriff auf SMB-Netzwerkfreigaben anders implementiert als die vorangegangenen Versionen von Mac OS X. Sollte diese Fehlermeldung erscheinen, kopieren Sie das Installer-Paket in einen lokalen Pfad und starten Sie es von dort aus.
  • Wenn Sophos Anti-Virus ein Windows-Server-Volume automatisch während eines Updates oder während des Sendens einer InterCheck-Server-Meldung mountet, bleibt der Server gelegentlich auch nach dem Ende der Aktion gemountet. Dies stellt kein Problem bei nachfolgenden Updates oder Benachrichtigungen dar. Das Volume kann bei Bedarf manuell wieder ungemountet werden.

  • Wenn Sie den Server angeben, von dem aus sich Sophos Anti-Virus aktualisiert, können Sie kein Konto mit leerem Kennwort verwenden.

    Sie geben den Server, von dem aus Sophos Anti-Virus aktualisiert wird, und das Konto, über das auf ihn zugegriffen wird, in der Registerkarte Primary Server bzw. Secondary Server an (auf diese Seiten gelangen Sie, indem Sie die Systemeinstellungen von Sophos Anti-Virus öffnen, auf die Registerkarte AutoUpdate klicken und Netzwerkeinstellungen wählen). Wenn es sich bei diesem Server um ein Windows-Netzwerk-Volume handelt, können Sie kein Konto mit einem leeren Kennwort angeben.

    Wenn das Windows-Netzwerk-Volume Gastzugriff erlaubt, können Sie sowohl den Benutzernamen und das Kennwort leer lassen. Ansonsten müssen Sie einen Benutzernamen und ein Kennwort eingeben.

  • An folgenden Stellen wird anstelle der Produktversion die Virendaten-Version angezeigt:
    • im auf dem Bildschirm angezeigten Sophos Anti-Virus-Fenster
    • im Über-Fenster, das beim Auswählen von Über Sophos Anti-Virus aus dem Sophos Anti-Virus-Menü angezeigt wird.

Weitere Informationen

  • In Sophos Enterprise Console und Sophos Control Center können Sie E-Mail-Benachrichtigungen für Viren-Alerts, Scan-Fehler oder Sonstige Fehler einrichten. Mac OS X-Computer unterstützen nicht die Option Scan-Fehler und senden daher auch nicht diese Art Benachrichtigung.

Technischer Support

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

Rechtlicher Hinweis

Copyright © 2004–2011 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.

ACE™, TAO™, CIAO™, and CoSMIC™

ACE1, TAO2, CIAO3, and CoSMIC4 (henceforth referred to as “DOC software”) are copyrighted by Douglas C. Schmidt5 and his research group6 at Washington University7, University of California8, Irvine, and Vanderbilt University9, Copyright © 1993–2005, all rights reserved.

Since DOC software is open-source, free software, you are free to use, modify, copy, and distribute–perpetually and irrevocably–the DOC software source code and object code produced from the source, as well as copy and distribute modified versions of this software. You must, however, include this copyright statement along with code built using DOC software.

You can use DOC software in commercial and/or binary software releases and are under no obligation to redistribute any of your source code that is built using DOC software. Note, however, that you may not do anything to the DOC software code, such as copyrighting it yourself or claiming authorship of the DOC software code, that will prevent DOC software from being distributed freely using an open-source development model. You needn’t inform anyone that you’re using DOC software in your software, though we encourage you to let us10 know so we can promote your project in the DOC software success stories11.

DOC software is provided as is with no warranties of any kind, including the warranties of design, merchantability, and fitness for a particular purpose, noninfringement, or arising from a course of dealing, usage or trade practice. Moreover, DOC software is provided with no support and without any obligation on the part of Washington University, UC Irvine, Vanderbilt University, their employees, or students to assist in its use, correction, modification, or enhancement. A number of companies12 around the world provide commercial support for DOC software, however. DOC software is Y2K-compliant, as long as the underlying OS platform is Y2K-compliant.

Washington University, UC Irvine, Vanderbilt University, their employees, and students shall have no liability with respect to the infringement of copyrights, trade secrets or any patents by DOC software or any part thereof. Moreover, in no event will Washington University, UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages.

The ACE13, TAO14, CIAO15, and CoSMIC16 web sites are maintained by the DOC Group17 at the Institute for Software Integrated Systems (ISIS)18 and the Center for Distributed Object Computing of Washington University, St. Louis19 for the development of open-source software as part of the open-source software community20. By submitting comments, suggestions, code, code snippets, techniques (including that of usage), and algorithms, submitters acknowledge that they have the right to do so, that any such submissions are given freely and unreservedly, and that they waive any claims to copyright or ownership. In addition, submitters acknowledgethat any such submission might become part of the copyright maintained on the overall body of code, which comprises the DOC software. By making a submission, submitter agree to these terms. Furthermore, submitters acknowledge that the incorporation or modification of such submissions is entirely at the discretion of the moderators of the open-source DOC software projects or their designees.

The names ACE, TAO, CIAO, CoSMIC, WashingtonUniversity, UC Irvine, and Vanderbilt University, may not be used to endorse or promote products or services derived from this source without express written permission from Washington University, UC Irvine, or Vanderbilt University. Further, products or services derived from this source may not be called ACE, TAO, CIAO, or CoSMIC nor may the name Washington University, UC Irvine, or Vanderbilt University appear in their names, without express written permission from Washington University, UC Irvine, and Vanderbilt University.

If you have any suggestions, additions, comments, or questions, please let me21 know.

Douglas C. Schmidt22

References

  1. http://www.cs.wustl.edu/~schmidt/ACE.html
  2. http://www.cs.wustl.edu/~schmidt/TAO.html
  3. http://www.dre.vanderbilt.edu/CIAO/
  4. http://www.dre.vanderbilt.edu/cosmic/
  5. http://www.dre.vanderbilt.edu/~schmidt/
  6. http://www.cs.wustl.edu/~schmidt/ACE-members.html
  7. http://www.wustl.edu/
  8. http://www.uci.edu/
  9. http://www.vanderbilt.edu/
  10. mailto:doc_group@cs.wustl.edu
  11. http://www.cs.wustl.edu/~schmidt/ACE-users.html
  12. http://www.cs.wustl.edu/~schmidt/commercial-support.html
  13. http://www.cs.wustl.edu/~schmidt/ACE.html
  14. http://www.cs.wustl.edu/~schmidt/TAO.html
  15. http://www.dre.vanderbilt.edu/CIAO/
  16. http://www.dre.vanderbilt.edu/cosmic/
  17. http://www.dre.vanderbilt.edu/
  18. http://www.isis.vanderbilt.edu/
  19. http://www.cs.wustl.edu/~schmidt/doc-center.html
  20. http://www.opensource.org/
  21. mailto:d.schmidt@vanderbilt.edu
  22. http://www.dre.vanderbilt.edu/~schmidt/

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.

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–2006 The OpenSSL Project. 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. 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 licence [including the GNU Public Licence.]

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