-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                postfix
        Announcement ID:        SUSE-SA:2010:011
        Date:                   Mon, 15 Feb 2010 14:00:00 +0000
        Affected Products:      openSUSE 11.2
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     5.0 (AV:N/AC:L/Au:N/C:N/I:N/A:P)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-0230

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             postfix port open
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            - see SUSE Security Summary Report
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The value of SMTPD_LISTEN_REMOTE accidentally defaulted to 'yes'. The postfix
   smtp daemon therefore was reachable over the network by default.
   This update resets the value to 'no' in /etc/sysconfig/mail. If you
   intentionally want postfix to listen for remote connections you need to
   manually set it to 'yes' again.
   
   This update also fixes a problem where the relay database was not created and
   postfix refused to start.

2) Solution or Work-Around

   Manually set SMTPD_LISTEN_REMOTE to 'no' and run
   # SuSEconfig --module postfix

3) Special Instructions and Notes

   Please restart postfix after the update.
   
   Watch out for SuSEconfig output indicating that /etc/postfix/main.cf
   wasn't fixed due to local modifications. In that case either rename
   /etc/postfix/main.cf.SuSEconfig to /etc/postfix/main.cf or manually
   run
   # postconf -e "inet_interfaces = localhost"

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   
   x86 Platform:
   
   openSUSE 11.2:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-debuginfo-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-debugsource-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-mysql-debuginfo-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-postgresql-debuginfo-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-devel-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-doc-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-mysql-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-postgresql-2.6.1-2.6.1.i586.rpm
   
   x86-64 Platform:
   
   openSUSE 11.2:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-debuginfo-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-debugsource-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-mysql-debuginfo-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-postgresql-debuginfo-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-devel-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-doc-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-mysql-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-postgresql-2.6.1-2.6.1.x86_64.rpm
   
   Sources:
   
   openSUSE 11.2:
   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   - see SUSE Security Summary Report

______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    The internal rpm package signatures provide an easy way to verify the
    authenticity of an RPM package. Use the command

     rpm -v --checksig 

    to verify the signature of the package, replacing  with the
    filename of the RPM package downloaded. The package is unmodified if it
    contains a valid signature from build@suse.de with the key ID 9C800ACA.

    This key is automatically imported into the RPM database (on
    RPMv4-based distributions) and the gpg key ring of 'root' during
    installation. You can also find it on the first installation CD and at
    the end of this announcement.

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

    opensuse-security@opensuse.org
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    opensuse-security-announce@opensuse.org
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

SuSE: 2010-011: postfix Security Update

February 15, 2010
The value of SMTPD_LISTEN_REMOTE accidentally defaulted to 'yes'

Summary


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                postfix
        Announcement ID:        SUSE-SA:2010:011
        Date:                   Mon, 15 Feb 2010 14:00:00 +0000
        Affected Products:      openSUSE 11.2
        Vulnerability Type:     remote denial of service
        CVSS v2 Base Score:     5.0 (AV:N/AC:L/Au:N/C:N/I:N/A:P)
        SUSE Default Package:   yes
        Cross-References:       CVE-2010-0230

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             postfix port open
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            - see SUSE Security Summary Report
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The value of SMTPD_LISTEN_REMOTE accidentally defaulted to 'yes'. The postfix
   smtp daemon therefore was reachable over the network by default.
   This update resets the value to 'no' in /etc/sysconfig/mail. If you
   intentionally want postfix to listen for remote connections you need to
   manually set it to 'yes' again.
   
   This update also fixes a problem where the relay database was not created and
   postfix refused to start.

2) Solution or Work-Around

   Manually set SMTPD_LISTEN_REMOTE to 'no' and run
   # SuSEconfig --module postfix

3) Special Instructions and Notes

   Please restart postfix after the update.
   
   Watch out for SuSEconfig output indicating that /etc/postfix/main.cf
   wasn't fixed due to local modifications. In that case either rename
   /etc/postfix/main.cf.SuSEconfig to /etc/postfix/main.cf or manually
   run
   # postconf -e "inet_interfaces = localhost"

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   
   x86 Platform:
   
   openSUSE 11.2:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-debuginfo-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-debugsource-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-mysql-debuginfo-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/i586/postfix-postgresql-debuginfo-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-devel-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-doc-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-mysql-2.6.1-2.6.1.i586.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/postfix-postgresql-2.6.1-2.6.1.i586.rpm
   
   x86-64 Platform:
   
   openSUSE 11.2:
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-debuginfo-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-debugsource-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-mysql-debuginfo-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/debug/update/11.2/rpm/x86_64/postfix-postgresql-debuginfo-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-devel-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-doc-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-mysql-2.6.1-2.6.1.x86_64.rpm
   http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/x86_64/postfix-postgresql-2.6.1-2.6.1.x86_64.rpm
   
   Sources:
   
   openSUSE 11.2:
   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   - see SUSE Security Summary Report

______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    The internal rpm package signatures provide an easy way to verify the
    authenticity of an RPM package. Use the command

     rpm -v --checksig 

    to verify the signature of the package, replacing  with the
    filename of the RPM package downloaded. The package is unmodified if it
    contains a valid signature from build@suse.de with the key ID 9C800ACA.

    This key is automatically imported into the RPM database (on
    RPMv4-based distributions) and the gpg key ring of 'root' during
    installation. You can also find it on the first installation CD and at
    the end of this announcement.

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

    opensuse-security@opensuse.org
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    opensuse-security-announce@opensuse.org
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

References

Severity

Related News