SuSE Linux Advisories: mod_php4, hylafax

____________________________________________________________________________

                        SuSE Security Announcement

        Package:                mod_php4
        Announcement-ID:        SuSE-SA:2002:036
        Date:                   Friday, Oct 4th 2002 10:30 MEST
        Affected products:      7.0, 7.1, 7.2, 7.3, 8.0
                                SuSE eMail Server 3.1
                                SuSE eMail Server III
                                SuSE Linux Enterprise Server
                                SuSE Linux Connectivity Server
                                SuSE Linux Office Server
        Vulnerability Type:     remote privilege escalation
        Severity (1-10):        5
        SuSE default package:   no
        Cross References:       CAN-2002-0985

    Content of this advisory:
        1) security vulnerability resolved:
            - control char injection in mail()
            - handling 5th argument of mail() while in "safe mode"
            - CRLF injection
        2) pending vulnerabilities, solutions, workarounds:
            - glibc
            - ghostview/kghostview
            - fetchmail
            - kdelibs
            - ethereal
        3) standard appendix (further information)

____________________________________________________________________________

1)  problem description, brief discussion, solution, upgrade information

    PHP is a well known and widely used web programming language.
    If a PHP script runs in "safe mode" several restrictions are applied
    to it including limits on execution of external programs.

    An attacker can pass shell meta-characters or sendmail(8) command line
    options via the 5th argument (introduced in version 4.0.5) of the mail()
    function to execute shell commands or control the behavior of sendmail(8).

    The CRLF injection vulnerabilities in fopen(), file(), header(), ...
    allow an attacker to bypass ACLs or trigger cross-side scripting.

    The mod_php4 package is not installed by default.
    A temporary fix is not known.

    Please note, that the following packages were rebuild too:
      - mod_php4-core
      - mod_php4-aolserver
      - mod_php4-devel
      - mod_php4-servlet
      - mod_php4-roxen

    Please download the update package for your distribution and verify its
    integrity by the methods listed in section 3) of this announcement.
    Then, install the package using the command "rpm -Fhv file.rpm" to apply
    the update.
    Our maintenance customers are being notified individually. The packages
    are being offered to install from the maintenance web.


    i386 Intel Platform:

    SuSE-8.0
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/mod_php4-4.1.0-257.i386.patch.rpm
      00ce030f55f4d0af32528402a5cbe269
    SuSE-8.0
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/mod_php4-4.1.0-257.i386.rpm
      3399c5b577464a282c85a6fcb56be915
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/mod_php4-4.1.0-257.src.rpm
      730c4b802dd14b9f9fc0ce2bb83fdc4e

    SuSE-7.3
      ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/mod_php4-4.0.6-193.i386.rpm
      c82972d8b1933a388adb6669e625835f
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/mod_php4-4.0.6-193.src.rpm
      8a8bf1262e11f4adbfa973b1ba9c9b54

    SuSE-7.2
      ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/mod_php4-4.0.6-192.i386.rpm
      b93a3680eef353f3e16de8f7dd13dfb8
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/mod_php4-4.0.6-192.src.rpm
      3304dae258e667a56b6d095eb552016f

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/mod_php4-4.0.4pl1-142.i386.rpm
      8a829c7fd56622b736a7f538e2d8cc3c
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/mod_php4-4.0.4pl1-142.src.rpm
      23e6b8d1f2128dd4885f85d939646078

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/mod_php4-4.0.4pl1-135.i386.rpm
      99e3e87bf1f18a839f2b1a2f80c3f336
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/mod_php4-4.0.4pl1-135.src.rpm
      68013bd4050dff75267cdde07894e5d8


    Sparc Platform:

    SuSE-7.3
      ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/mod_php4-4.0.6-66.sparc.rpm
      397044fb23b60f444fcb6b76986027bf
    source rpm:
      ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/mod_php4-4.0.6-66.src.rpm
      431de04e4b31cf939e0cb9a1881c9e72

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/mod_php4-4.0.4pl1-45.sparc.rpm
      a6146130f0c20821696406e62ab22863
    source rpm:
      ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/mod_php4-4.0.4pl1-45.src.rpm
      e1019229ec79ea7175f188ecc348e2b6


    AXP Alpha Platform:

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/mod_php4-4.0.4pl1-54.alpha.rpm
      8010e1ef878dd366bb3dcce07b5c8a99
    source rpm:
      ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/mod_php4-4.0.4pl1-54.src.rpm
      7906462b3a64d505dc78e298512312de

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/mod_php4-4.0.4pl1-55.alpha.rpm
      55e770e7a01a680e3a776bb085d91254
    source rpm:
      ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/mod_php4-4.0.4pl1-55.src.rpm
      0e6654da0c43f3170ddcf0b132ae9ac3


    PPC Power PC Platform:

    SuSE-7.3
      ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/mod_php4-4.0.6-99.ppc.rpm
      52421717b8fdd0c9ee4d96d3f0bb1e89
    source rpm:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/mod_php4-4.0.6-99.src.rpm
      df7274f651888c62ad3693d3672ccc00

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/mod_php4-4.0.4pl1-53.ppc.rpm
      b43d618d2eba73477dd8f9e2d2215118
    source rpm:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/mod_php4-4.0.4pl1-53.src.rpm
      f9457dc7736cdfecaa2e4a7a01c0c53f

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/mod_php4-4.0.4pl1-45.ppc.rpm
      56d6fb88d0032f5dcc12397f295e42b2
    source rpm:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/mod_php4-4.0.4pl1-45.src.rpm
      b684c0aa03ec7ec9c8d75f5558bbea1e

____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - glibc
      Client applications which use res_search/res_nsreach and/or res_query()/
      res_nquery() of libresolv could trigger a DNS decoding error, a SEGV or
      leak information by reading beyond the end of a too small 'answer'
      buffer.
      The update packages are being built and tested. We will publish a security
      announcement as soon as they are ready.


    - ghostview/kghostview
      Bufferoverflows have recently been discovered in these packages. They allow
      attackers to execute arbitrary code with the privileges of the user
      viewing special crafted documents created by the attacker. New packgaes will
      soon be available on our ftp servers.

    - fetchmail
      Fetchmail contains remotely exploitable overflows in the mail header
      parsing functions. In depth discussion of these problems can be found at
      http://security.e-matters.de/advisories/032002.html.
      New packages will soon be available on our ftp servers.

    - kdelibs
      KDE's SSL implementation fails to check the trust chain in SSL
      certificates. This bug allows faking valid SSL certificates.
      New KDE packages will be available soon to fix this and other bugs.

    - ethereal
      Several potential security issues have been discovered in ethereal
      0.9.4. After this package is tested succesfuly it will be relased.
____________________________________________________________________________

3)  standard appendix: authenticity verification, additional information

  - Package authenticity verification:

    SuSE update packages are available on many mirror ftp servers all over
    the world. While this service is being considered valuable and important
    to the free and open source software community, many users wish to be
    sure about the origin of the package and its content before installing
    the package. There are two verification methods that can be used
    independently from each other to prove the authenticity of a downloaded
    file or rpm package:
    1) md5sums as provided in the (cryptographically signed) announcement.
    2) using the internal gpg signatures of the rpm package.

    1) execute the command
        md5sum <name-of-the-file.rpm>
       after you downloaded the file from a SuSE ftp server or its mirrors.
       Then, compare the resulting md5sum with the one that is listed in the
       announcement. Since the announcement containing the checksums is
       cryptographically signed (usually using the key security@suse.de),
       the checksums show proof of the authenticity of the package.
       We disrecommend to subscribe to security lists which cause the
       email message containing the announcement to be modified so that
       the signature does not match after transport through the mailing
       list software.
       Downsides: You must be able to verify the authenticity of the
       announcement in the first place. If RPM packages are being rebuilt
       and a new version of a package is published on the ftp server, all
       md5 sums for the files are useless.

    2) rpm package signatures provide an easy way to verify the authenticity
       of an rpm package. Use the command
        rpm -v --checksig <file.rpm>
       to verify the signature of the package, where <file.rpm> is the
       filename of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an un-installed rpm
       package file.
       Prerequisites:
        a) gpg is installed
        b) The package is signed using a certain key. The public part of this
           key must be installed by the gpg program in the directory
           ~/.gnupg/ under the user's home directory who performs the
           signature verification (usually root). You can import the key
           that is used by SuSE in rpm packages for SuSE Linux by saving
           this announcement to a file ("announcement.txt") and
           running the command (do "su -" to be root):
            gpg --batch; gpg < announcement.txt | gpg --import
           SuSE Linux distributions version 7.1 and thereafter install the
           key "build@suse.de" upon installation or upgrade, provided that
           the package gpg is installed. The file containing the public key
           is placed at the top-level directory of the first CD (pubring.gpg)
           and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


  - SuSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   general/linux/SuSE security discussion.
            All SuSE security announcements are sent to this list.
            To subscribe, send an email to
                <suse-security-subscribe@suse.com>.

    suse-security-announce@suse.com
        -   SuSE's announce-only mailing list.
            Only SuSE's security announcements are sent to this list.
            To subscribe, send an email to
                <suse-security-announce-subscribe@suse.com>.

    For general information or the frequently asked questions (faq)
    send mail to:
        <suse-security-info@suse.com> or
        <suse-security-faq@suse.com> respectively.

    =====================================================================
    SuSE's security contact is <security@suse.com> or <security@suse.de>.
    The <security@suse.de> public key is listed below.
    =====================================================================
____________________________________________________________________________

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular,
    it is desired that the clear-text signature shows proof of the
    authenticity of the text.
    SuSE Linux AG makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.

Type Bits/KeyID    Date       User ID
pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>



Bye,
     Thomas
-- 
  Thomas Biege <thomas@suse.de>
  SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg
  Function: Security Support & Auditing
  "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka"
  Key fingerprint = 51 AD B9 C7 34 FC F2 54  01 4A 1C D4 66 64 09 83
-- 

  Cold silence has a tendency to atrophy any sense of compassion
                                                  - Maynard James Keenan


____________________________________________________________________________

                        SuSE Security Announcement

        Package:                hylafax
        Announcement-ID:        SuSE-SA:2002:035
        Date:                   Friday, Oct 4th 2002 10:30 MEST
        Affected products:      7.0, 7.1, 7.2, 7.3, 8.0
                                SuSE Linux Connectivity Server
                                SuSE Linux Enterprise Server
                                SuSE Linux Office Server
        Vulnerability Type:     remote privilege escalation
        Severity (1-10):        4
        SuSE default package:   no
        Cross References:       CAN-2002-1050

    Content of this advisory:
        1) security vulnerability resolved:
            - format string bug in logging
              code for TSI
            - buffer overflow in faxgetty
              while handling image data
        2) pending vulnerabilities, solutions, workarounds:
            - glibc
            - ghostview/kghostview
            - fetchmail
            - kdelibs
            - ethereal
        3) standard appendix (further information)

____________________________________________________________________________

1)  problem description, brief discussion, solution, upgrade information

    HylaFAX is a client-server architecture for receiving and sending
    facsimiles.

    The logging function of faxgetty prior version 4.1.3 was vulnerable to
    a format string bug when handling the TSI value of a received facsimile.
    This bug could easily be used to trigger a denial-of-service attack or
    to execute arbitrary code remotely.

    Another bug in faxgetty, a buffer overflow, can be abused by a remote
    attacker by sending a large line of image data to execute arbitrary
    commands too.

    Several format string bugs in local helper applications were fixed too.
    These bugs can not be exploited to gain higher privileges on a system
    running SuSE Linux because of the absence of setuid bits.

    The hylafax package is not installed by default.
    A temporary fix is not known.

    Please download the update package for your distribution and verify its
    integrity by the methods listed in section 3) of this announcement.
    Then, install the package using the command "rpm -Fhv file.rpm" to apply
    the update.
    Our maintenance customers are being notified individually. The packages
    are being offered to install from the maintenance web.


    i386 Intel Platform:

    SuSE-8.0
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/hylafax-4.1-285.i386.patch.rpm
      3115ebdb9e65027f35809463c5e6ae7e
    SuSE-8.0
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/hylafax-4.1-285.i386.rpm
      07b0f2d015b0fd83c5bb9be548e7b8fb
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/hylafax-4.1-285.src.rpm
      8231586e2de356c737ef3d6f9d17c0ea

    SuSE-7.3
      ftp://ftp.suse.com/pub/suse/i386/update/7.3/n3/hylafax-4.1-284.i386.rpm
      de51bda21cc9ee1a4dd3cd06ccccf71e
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/hylafax-4.1-284.src.rpm
      aac2ecddf06934f286960f52f2e7670e

    SuSE-7.2
      ftp://ftp.suse.com/pub/suse/i386/update/7.2/n3/hylafax-4.1beta2-376.i386.rpm
      275c73b0b192da9c883cfebf6638604e
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/hylafax-4.1beta2-376.src.rpm
      b8698144b8bb859d880659fcf01eb020

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/i386/update/7.1/n3/hylafax-4.1beta2-375.i386.rpm
      c322bc9007191e3692341b5702b29200
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/hylafax-4.1beta2-375.src.rpm
      4d76cd426565e411941b4aaebf6ad761

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/i386/update/7.0/n2/hylafax-4.1beta2-373.i386.rpm
      fa7399ce161a44dbad630928cd6b3b84
    source rpm:
      ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/hylafax-4.1beta2-373.src.rpm
      0ac9d8b33b75f29b55a5750f17a65b93


    Sparc Platform:

    SuSE-7.3
      ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n3/hylafax-4.1-112.sparc.rpm
      1cabb4113f858df010d305fa576c5a02
    source rpm:
      ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/hylafax-4.1-112.src.rpm
      a5ddaee97231c423e04fb71b757532a3

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n3/hylafax-4.1beta2-218.sparc.rpm
      1449e568071f5fb6080efebb8f2a7a2b
    source rpm:
      ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/hylafax-4.1beta2-218.src.rpm
      bf8c780206da51bc548e9fd4264b9bfc

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n2/hylafax-4.1beta2-218.sparc.rpm
      bb265465ea8b84ca31b5c954266daf1d
    source rpm:
      ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/hylafax-4.1beta2-218.src.rpm
      b5bcae601fe056f399fc8696aa156529


    AXP Alpha Platform:

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/axp/update/7.1/n3/hylafax-4.1beta2-245.alpha.rpm
      45d0fd7061f10e4bef9e57c42a9b160d
    source rpm:
      ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/hylafax-4.1beta2-245.src.rpm
      baf364ec3636077fe8f810edeb111572

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/axp/update/7.0/n2/hylafax-4.1beta2-244.alpha.rpm
      856e96ce4a165b74e70ebc9ef3201672
    source rpm:
      ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/hylafax-4.1beta2-244.src.rpm
      f68e2260aa36d4d218a3f3589333ea0e


    PPC Power PC Platform:

    SuSE-7.3
      ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n3/hylafax-4.1-189.ppc.rpm
      79846b9ae0f75f8ed9b17fed07ba6263
    source rpm:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/hylafax-4.1-189.src.rpm
      98a123cf18cb6b34ffd9018a76ad161f

    SuSE-7.1
      ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n3/hylafax-4.1beta2-218.ppc.rpm
      2bfe866f1bd1d93307449de95d84d6c2
    source rpm:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/hylafax-4.1beta2-218.src.rpm
      972c605bd3a9cc15bbbc5aa188dfc864

    SuSE-7.0
      ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n2/hylafax-4.1beta2-217.ppc.rpm
      00b1ae1c91235ecceb287ffe7aced175
    source rpm:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/hylafax-4.1beta2-217.src.rpm
      e905325a032854fb653cf458e0db8942

____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - glibc
      Client applications which use res_search/res_nsreach and/or res_query()/
      res_nquery() of libresolv could trigger a DNS decoding error, a SEGV or
      leak information by reading beyond the end of a too small 'answer'
      buffer.
      The update packages are being built and tested. We will publish a security
      announcement as soon as they are ready.

    - ghostview/kghostview
      Bufferoverflows have recently been discovered in these packages. They
      allow attackers to execute arbitrary code with the privileges of the
      user viewing special crafted documents created by the attacker. New
      packgaes will soon be available on our ftp servers.

    - fetchmail
      Fetchmail contains remotely exploitable overflows in the mail header
      parsing functions. In depth discussion of these problems can be found
      at http://security.e-matters.de/advisories/032002.html.
      New packages will soon be available on our ftp servers.

    - kdelibs
      KDE's SSL implementation fails to check the trust chain in SSL
      certificates. This bug allows faking valid SSL certificates.
      New KDE packages will be available soon to fix this and other bugs.

    - ethereal
      Several potential security issues have been discovered in ethereal
      0.9.4. After this package is tested succesfuly it will be relased.

____________________________________________________________________________

3)  standard appendix: authenticity verification, additional information

  - Package authenticity verification:

    SuSE update packages are available on many mirror ftp servers all over
    the world. While this service is being considered valuable and important
    to the free and open source software community, many users wish to be
    sure about the origin of the package and its content before installing
    the package. There are two verification methods that can be used
    independently from each other to prove the authenticity of a downloaded
    file or rpm package:
    1) md5sums as provided in the (cryptographically signed) announcement.
    2) using the internal gpg signatures of the rpm package.

    1) execute the command
        md5sum <name-of-the-file.rpm>
       after you downloaded the file from a SuSE ftp server or its mirrors.
       Then, compare the resulting md5sum with the one that is listed in the
       announcement. Since the announcement containing the checksums is
       cryptographically signed (usually using the key security@suse.de),
       the checksums show proof of the authenticity of the package.
       We disrecommend to subscribe to security lists which cause the
       email message containing the announcement to be modified so that
       the signature does not match after transport through the mailing
       list software.
       Downsides: You must be able to verify the authenticity of the
       announcement in the first place. If RPM packages are being rebuilt
       and a new version of a package is published on the ftp server, all
       md5 sums for the files are useless.

    2) rpm package signatures provide an easy way to verify the authenticity
       of an rpm package. Use the command
        rpm -v --checksig <file.rpm>
       to verify the signature of the package, where <file.rpm> is the
       filename of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an un-installed rpm
       package file.
       Prerequisites:
        a) gpg is installed
        b) The package is signed using a certain key. The public part of this
           key must be installed by the gpg program in the directory
           ~/.gnupg/ under the user's home directory who performs the
           signature verification (usually root). You can import the key
           that is used by SuSE in rpm packages for SuSE Linux by saving
           this announcement to a file ("announcement.txt") and
           running the command (do "su -" to be root):
            gpg --batch; gpg < announcement.txt | gpg --import
           SuSE Linux distributions version 7.1 and thereafter install the
           key "build@suse.de" upon installation or upgrade, provided that
           the package gpg is installed. The file containing the public key
           is placed at the top-level directory of the first CD (pubring.gpg)
           and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


  - SuSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   general/linux/SuSE security discussion.
            All SuSE security announcements are sent to this list.
            To subscribe, send an email to
                <suse-security-subscribe@suse.com>.

    suse-security-announce@suse.com
        -   SuSE's announce-only mailing list.
            Only SuSE's security announcements are sent to this list.
            To subscribe, send an email to
                <suse-security-announce-subscribe@suse.com>.

    For general information or the frequently asked questions (faq)
    send mail to:
        <suse-security-info@suse.com> or
        <suse-security-faq@suse.com> respectively.

    =====================================================================
    SuSE's security contact is <security@suse.com> or <security@suse.de>.
    The <security@suse.de> public key is listed below.
    =====================================================================
____________________________________________________________________________

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular,
    it is desired that the clear-text signature shows proof of the
    authenticity of the text.
    SuSE Linux AG makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.

Type Bits/KeyID    Date       User ID
pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>


Bye,
     Thomas
-- 
  Thomas Biege <thomas@suse.de>
  SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg
  Function: Security Support & Auditing
  "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka"
  Key fingerprint = 51 AD B9 C7 34 FC F2 54  01 4A 1C D4 66 64 09 83
-- 

  Cold silence has a tendency to atrophy any sense of compassion
                                                  - Maynard James Keenan