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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                gpg
        Announcement ID:        SUSE-SA:2007:024
        Date:                   Fri, 30 Mar 2007 13:00:00 +0000
        Affected Products:      SUSE LINUX 9.3
                                SUSE LINUX 10.0
                                SUSE LINUX 10.1
                                openSUSE 10.2
                                UnitedLinux 1.0
                                SuSE Linux Enterprise Server 8
                                SuSE Linux Openexchange Server 4
                                SuSE Linux Desktop 1.0
                                SuSE Linux Standard Server 8
                                SuSE Linux School Server
                                SUSE LINUX Retail Solution 8
                                SUSE SLES 9
                                Novell Linux Desktop 9
                                Open Enterprise Server
                                Novell Linux POS 9
                                SUSE SLED 10
                                SUSE SLES 10
        Vulnerability Type:     signature bypassing
        Severity (1-10):        5
        SUSE Default Package:   yes
        Cross-References:       CVE-2007-1263

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             gpg signature bypassing
           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

   When printing a text stream with a GPG signature it was possible
   for an attacker to create a stream with "unsigned text, signed text"
   where both unsigned and signed text would be shown without distinction
   which one was signed and which part wasn't.

   This problem is tracked by the Mitre CVE ID CVE-2007-1263.

   The update introduces a new option --allow-multiple-messages to print
   out such messages in the future, by default it only prints and handles
   the first one.

   gpg2 and various clients using GPG to check digital signatures are
   affected too, but will be fixed separately.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   None.

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 10.2:
             7e8844844d89dec746bb0f2e6faecd4f

   SUSE LINUX 10.1:
             0a26653f3fa65d46e4e192539c7ace01

   SUSE LINUX 10.0:
             758b8a3198153d484ec09a6b1d760fb2

   SUSE LINUX 9.3:
             447e593b1328e0a8c0900c525be488f5

   Power PC Platform:

   openSUSE 10.2:
             2a709e1eb6a22ace9eeba678a771ccff

   SUSE LINUX 10.1:
             0258f25101194c8ed1d39511748baef5

   SUSE LINUX 10.0:
             d8c8873e538881723d7b98cafc6402ea

   x86-64 Platform:

   openSUSE 10.2:
             2535c0dd40a972c7e028ac0d60d00aeb

   SUSE LINUX 10.1:
             88ab493766d181b2aeb85e9ba41d0f04

   SUSE LINUX 10.0:
             c8abc6fc65e284c64f4259d8d50dd1b8

   SUSE LINUX 9.3:
             0c5aa6ad775f5746256d7960adbeb86b

   Sources:

   openSUSE 10.2:
             3fd3ae52f6a004a24d2fd4d822a88d67

   SUSE LINUX 10.1:
             b691ff4ff478979dfe5dc1e0f6534272

   SUSE LINUX 10.0:
             e05305b96b232bef94eaa06249471c51

   SUSE LINUX 9.3:
             9bc52a7b1845bbeb23858b92696fe67b

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

   UnitedLinux 1.0
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SuSE Linux Openexchange Server 4
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   Open Enterprise Server
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   Novell Linux POS 9
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   Novell Linux Desktop 9
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SuSE Linux Enterprise Server 8
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SuSE Linux Standard Server 8
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SuSE Linux School Server
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SUSE LINUX Retail Solution 8
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SuSE Linux Desktop 1.0
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SUSE SLES 10
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

   SUSE SLES 9
     http://support.novell.com/techcenter/psdb/3fafef103902137d0bea93863e650bdb.html

______________________________________________________________________________

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.

    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) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

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

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. Execute the command

         md5sum 

       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
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

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

    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 e-mail to
                .

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