JD writes “Apex Designs have announced that their GTA-style game Payback is being ported to Linux. There’s a short status report (including some early screenshots) available here.”

SuSE: Several security related bugs have been found in all squid packages
contained in SuSE products. These bugs are being fixed in our update
packages and cover modifications in the gopher client code, the FTP
directory listing parser that generates HTML output, FTP protocol
sanity checks concerning server address comparison between control
and data connection, in the MSNT auth helper as well as in proxy
authentication forwarding code. Our update packages also contain
non-security relevant additions as suggested by the squid developers.”

____________________________________________________________________________

                        SuSE Security Announcement

        Package:                squid
        Announcement-ID:        SuSE-SA:2002:025
        Date:                   Tuesday, Jul 9th 2002 01:30 MEST
        Affected products:      6.4, 7.0, 7.1, 7.2, 7.3, 8.0
                                SuSE Linux Connectivity Server
                                SuSE Linux Enterprise Server
        Vulnerability Type:     possible remote code execution
        Severity (1-10):        6
        SuSE default package:   no

    Content of this advisory:
        1) security vulnerability resolved: squid
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds
        3) standard appendix (further information)

____________________________________________________________________________

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

    squid is a web proxy cache contained but not installed and activated
    by default on SuSE products.

    Several security related bugs have been found in all squid packages
    contained in SuSE products. These bugs are being fixed in our update
    packages and cover modifications in the gopher client code, the FTP
    directory listing parser that generates HTML output, FTP protocol
    sanity checks concerning server address comparison between control
    and data connection, in the MSNT auth helper as well as in proxy
    authentication forwarding code. Our update packages also contain
    non-security relevant additions as suggested by the squid developers.
    The severity of the errors in the package range from harmless to critical.
    The gopher client bugs as well as the bug in the FTP directory parsing
    code are believed to be exploitable in the sense of being able to remotely
    execute code introduced by the attacker. The bug in the MSNT auth helper
    does not affect our binary packages because the feature is not activated
    at compile time.
    While Olaf Kirch (SuSE Security) has found and also fixed parts of the
    bugs, SuSE Security has not verified the claim about the remote
    exploitability to execute code, though.
    For more information about the squid web proxy and first-hand information
    about the security problems found, please see the project's website at
    http://www.squid-cache.org/.

    A brief note about the package names in the distributions:
    All SuSE Linux distributions contain two squid packages. The names are
    squid2 and squid23 for SuSE Linux 6.4 through 7.1, and squid and
    squid-beta for all newer distributions. The squid-beta package on SuSE
    Linux 8.0 is unaffected.
    To find out which version of the squid package you are using, use the
    command
        rpm -qf `which squid`


    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.

    After applying the rpm command for the update, you should restart the
    squid daemon process for the update to become effective:
        rcsquid stop ; sleep 10; rcsquid start

    Our maintenance customers have been 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/squid-2.4.STABLE6-2.i386.rpm
      01f5c698e0418e6055e9ed1018493380
    ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/squid-2.4.STABLE6-9.i386.patch.rpm

      917c26da9c444085d045b708548eae3e
    ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/squid-2.4.STABLE6-9.i386.rpm
      fa4780901f96712ea22eef28bdf53700
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/squid-2.4.STABLE6-9.src.rpm
      dc96baf5541829ee6e615861d17146aa

    SuSE-7.3
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/squid-2.3.STABLE4-162.i386.rpm
      86df1f5a50ed65cd038d9cc2b2782f9b
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/squid-beta-2.4.STABLE2-99.i386.rpm
      4d1462ec0691eb0b6572b67064d5899b
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/squid-2.3.STABLE4-162.src.rpm

      ab61356851ac840d427f1ffd94ff6d14
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/squid-beta-2.4.STABLE2-99.src.rpm
      c75a0693b587827017fd7f7b6f387d43

    SuSE-7.2
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/squid-2.3.STABLE4-162.i386.rpm
      0eb805295d26ae7a634e70248536f743
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/squid-beta-2.4.STABLE1-105.i386.rpm
      7c710d4080457b90c90c9641ceb27923
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/squid-2.3.STABLE4-162.src.rpm
      9e2d0f0a81d3231bb36efce6eb09b806
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/squid-beta-2.4.STABLE1-105.src.rpm

      f6a59ea75478277a5cf1eaa45308e2db

    SuSE-7.1
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/squid2-2.2.STABLE5-224.i386.rpm
      458c23172bd607c2e1b64bcca668743f
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/squid23-2.3.STABLE4-82.i386.rpm
      aef3ece720951def7e22cdd28b65782a
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/squid2-2.2.STABLE5-224.src.rpm
      66edc4b69aa84aecfe33efef5589611e
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/squid23-2.3.STABLE4-82.src.rpm
      7c01a574da94df5b72b864a1648021d3

    SuSE-7.0
    ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/squid2-2.2.STABLE5-223.i386.rpm

      05603a978583210b281ab4860fef6f00
    ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/squid23-2.3.STABLE4-81.i386.rpm
      ae208d4e4896f8092f122a2e79f472f3
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/squid2-2.2.STABLE5-223.src.rpm
      11d569d72642b2a4414b0c35a87a0bd1
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/squid23-2.3.STABLE4-81.src.rpm
      990b507d6c8ea50f10ba7fe6b218bcfb

    SuSE-6.4
    ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/squid2-2.2.STABLE5-223.i386.rpm
      56dc0b40ae95bce1e49c1758920debd0
    ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/squid23-2.3.STABLE4-81.i386.rpm

      907f05e3be9012003a8d6fbce866b8c5
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/squid2-2.2.STABLE5-223.src.rpm
      2e8655ca0fbdd53f45c64990de92697e
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/squid23-2.3.STABLE4-81.src.rpm
      58e1d68d8e5dc8dbcc9d53446436e077




    Sparc Platform:

    SuSE-7.3
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/squid-2.3.STABLE4-57.sparc.rpm
      fe3040600c6f08394db78a73d435475b
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/squid-beta-2.4.STABLE2-27.sparc.rpm
      f0e296889bcc571da9a35cd02d6efd9c
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/squid-2.3.STABLE4-57.src.rpm

      dfbc5f10d9993d299b420d1787b14c0b
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/squid-beta-2.4.STABLE2-27.src.rpm
      dc6ff79b6e48821b81b1d53a837fe88c

    SuSE-7.1
    ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/squid2-2.2.STABLE5-210.sparc.rpm
      6fc7ded2b633825957959cd0a373c4d2
    ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/squid23-2.3.STABLE4-63.sparc.rpm
      43693ee6312ce6f178baeb50340d8639
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/squid2-2.2.STABLE5-210.src.rpm
      5cae476344a776ce50a1a1805ef4ffcc
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/squid23-2.3.STABLE4-63.src.rpm

      65fdf61f12b9c4ec5c91857c3af76497

    SuSE-7.0
    ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/squid2-2.2.STABLE5-210.sparc.rpm
      e928951c8d068e982bb00b50472d716d
    ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/squid23-2.3.STABLE4-63.sparc.rpm
      cafe9565d1021f69ee31636d8d854457
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/squid2-2.2.STABLE5-210.src.rpm
      ebd9c000ab1da0db1ea99998b3f0cf15
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/squid23-2.3.STABLE4-63.src.rpm

      149927211efa4c2419eed6b000859689





    AXP Alpha Platform:

    SuSE-7.1
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/squid2-2.2.STABLE5-230.alpha.rpm
      4df2821b296d2cd980b516a690b9a1bd
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/squid23-2.3.STABLE4-80.alpha.rpm
      a01625b4b191f84fff32e38c8d336fac
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/squid2-2.2.STABLE5-230.src.rpm
      9deaebb24e5dfbe5f20a5488c279458e
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/squid23-2.3.STABLE4-80.src.rpm
      2ec1d32a64dbdb0a15d892dd622c091a

    SuSE-7.0
    ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/squid2-2.2.STABLE5-230.alpha.rpm

      73b3f402a7f50ccb6ac9045da87b1c40
    ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/squid23-2.3.STABLE4-79.alpha.rpm
      6938b75054e93f2ec1520e0b3b093790
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/squid2-2.2.STABLE5-230.src.rpm
      ddef84a2c1c430d341c1b8e8ae1a0d77
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/squid23-2.3.STABLE4-79.src.rpm
      faaf272a46f39ebc0d6956cb8b508395

    SuSE-6.4
    ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/squid2-2.2.STABLE5-230.alpha.rpm
      d308089c0b35b812a6bece1b612bd171
    ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/squid23-2.3.STABLE4-78.alpha.rpm

      a2446410ef8fd3b0832394bc52cae927
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/squid2-2.2.STABLE5-230.src.rpm
      2a0837f760ec3262268645a5d1dd99ce
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/squid23-2.3.STABLE4-78.src.rpm
      01d07096af26e19aecf35ae29fc39f85





    PPC Power PC Platform:

    SuSE-7.3
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/squid-2.3.STABLE4-77.ppc.rpm
      6d84192dfcfa15ec05ee0c1fbf8cc564
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/squid-beta-2.4.STABLE2-64.ppc.rpm
      fde4eea7193755ecb72c8e98006efc83
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/squid-2.3.STABLE4-77.src.rpm

      44c07a7d4b37be012c87b1057c38728c
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/squid-beta-2.4.STABLE2-64.src.rpm
      7ca4b1b7a1802bffdffef3b6d5d342a5

    SuSE-7.1
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/squid2-2.2.STABLE5-203.ppc.rpm
      28b9a3b64fe23408a4bd16031d384b02
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/squid23-2.3.STABLE4-73.ppc.rpm
      b7a2e5c2a446a2848537fe65362e8cb5
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/squid2-2.2.STABLE5-203.src.rpm
      d0a9141bac8b44f826698b0d90c91d80
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/squid23-2.3.STABLE4-73.src.rpm

      488f2d67c6a300bca3d06a6cff26988f

    SuSE-7.0
    ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/squid2-2.2.STABLE5-202.ppc.rpm
      5ef4ef00e866d0efb451334bc12a8db7
    ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/squid23-2.3.STABLE4-72.ppc.rpm
      ceba8ae4348b499d75a8798282899fff
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/squid2-2.2.STABLE5-202.src.rpm
      d2a8b8bbc4c93073ddba930b96a0a459
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/squid23-2.3.STABLE4-72.src.rpm
      a1e44b9a51d96125e7664a784a1fbce0

    SuSE-6.4
    ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/squid2-2.2.STABLE5-202.ppc.rpm

      84afced56c0f0a4502bab69ed6de7cc1
    ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/squid23-2.3.STABLE4-72.ppc.rpm
      fe9ce325bb9580f0c8a9804800ac9179
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/squid2-2.2.STABLE5-202.src.rpm
      c1d61ef183dd5b11191f6872852b24e9
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/squid23-2.3.STABLE4-72.src.rpm
      ef6b394d43f64936df30f9ffcd315495


____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

  - We are investigating if recently found weaknesses in resolver libraries
    on BSD systems affect the SuSE Linux glibc as well. Also, the resolver
    code in bind nameserver utilities is under investigation.
    Further news about the resolver issues is underway.

  - ghostscript
    RedHat released a security announcement concerning a problem in
    ghostscript, which could be exploited to gain privilege of the print
    server user. We are investigating whether SuSE Linux is affected.

____________________________________________________________________________

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 uninstalled 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 toplevel 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 annoucements 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 cleartext signature shows proof of the
    authenticity of the text.
    SuSE GmbH 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>

Squid-Cache.org: “squid-2.4.STABLE7 has been released to address a number of
security issues in Squid and related software. All users of the
Squid HTTP Proxy are strongly encouraged to upgrade.”

__________________________________________________________________

      Squid Proxy Cache Security Update Advisory SQUID-2002:3
__________________________________________________________________

Advisory ID:            SQUID-2002:3
Date:                   July 3, 2002
Summary:                Squid-2.4.STABLE7 released to address a
                        number of security related issues.
Affected versions:      Squid-2.x up to and including 2.4.STABLE6
__________________________________________________________________

       http://www.squid-cache.org/Advisories/SQUID-2002_3.txt
__________________________________________________________________

Problem Description:

 squid-2.4.STABLE7 has been released to address a number of
 security issues in Squid and related software. All users of the
 Squid HTTP Proxy are strongly encouraged to upgrade.

 Security related changes in the 2.4.STABLE7 release:

 - Several bugfixes and cleanup of the Gopher client, both
   to correct some security issues and to make Squid properly
   render certain Gopher menus.
 - Security fixes in how Squid parses FTP directory listings into
   HTML
 - FTP data channels are now sanity checked to match the address
   of the requested FTP server. This to prevent theft or injection
   of data. See the new ftp_sanitycheck directive if this sanity
   check is not desired.
 - The MSNT auth helper has been updated to v2.0.3+fixes for
   buffer overflow security issues found in this helper.
 - A security issue in how Squid forwards proxy authentication
   credentials has been fixed

 Other changes in the 2.4.STABLE7 release:

 - Squid now correctly rejects any requests using transfer-
   encoding. Squid is a HTTP/1.0 proxy and as such does not
   implement or support transfer-encoding.
 - Minor changes to support Apple MAC OS X and some other
   platforms more easily.
 - The client -T option has been implemented
 - HTCP related bugfixes in "squid -k reconfigure"

 For more details on the changes see the descriptions in our
 patch archive for version Squid-2.4.STABLE6:

   http://www.squid-cache.org/Versions/v2/2.4/bugs/

------------------------------------------------------------------

Severity:

 It is believed that several of the Gopher bug and the FTP
 directory parsing related bugs can be exploited to allow remote
 execution of code.

 The user executing the attack must be allowed to use the proxy
 for any potential attack to be successful, but it is believed
 that a remote attacker can use a small amount of social
 engineering to make an attack without direct access to the proxy.

 The third issue relating to FTP data channels is minor in nature
 in most installations, but there may be unfortunate interactions
 with firewalling policies etc making it a more severe issue than
 normal.

 The MSNT auth helper issue is believed to possibly allow remote
 execution of code in certain configurations.

 The issue in forwarding of proxy authentication credentials may
 expose your users private proxy login+password to selected
 external web sites depending on your configuration.

__________________________________________________________________

Updated Packages:

 The Squid-2.4.STABLE7 release contains fixes for all these
 problems. You can download the Squid-2.4.STABLE7 release from

   ftp://ftp.squid-cache.org/pub/squid-2/STABLE/
   http://www.squid-cache.org/Versions/v2/2.4/

 or the mirrors (may take a while before all mirrors are updated).
 For a list of mirror sites see

   http://www.squid-cache.org/Mirrors/ftp-mirrors.html
   http://www.squid-cache.org/Mirrors/http-mirrors.html

 Individual patches to the mentioned issues can be found from our
 patch archive for version Squid-2.4.STABLE6

   http://www.squid-cache.org/Versions/v2/2.4/bugs/

 The patches should also apply with only a minimal effort to
 earlier Squid 2.4 versions if required.

 If you are using a prepackaged version of Squid then please
 refer to the package vendor for availability information on
 updated packages.

__________________________________________________________________

Determining if your version is vulnerable:

 To determine which version of Squid you are using, run the command

    squid -v

 You are likely to be vulnerable to these issues if you are
 running version 2.4.STABLE6 or earlier.

 If you are using a binary or otherwise pre-packaged version
 please verify with your vendor on which versions are affected as
 some vendors ship earlier versions with the needed patches
 applied.  Note that unless you have upgraded to a version
 released after 2002-07-01 you are  most likely vulnerable to
 these issues.

 There is no easy means to determine if your version is affected
 other than by the Squid version number.

 You may be vulnerable to the MSNT auth issue if your squid.conf
 file contains the directive

   authenticate_program /usr/local/squid/libexec/squid/msnt_auth

 and you have not upgraded your copy of msnt_auth to a corrected
 version

 Note: msnt_auth is sometimes installed as msntauth, and the path
 may differ depending on the installation method.

__________________________________________________________________

Other versions of Squid:

 Versions prior to the 2.4 series are deprecated, please update
 to Squid-2.4.STABLE7 if you are using a version older than 2.4.

 Users of unreleased versions of squid (2.6.DEVEL or 2.5.PRE
 versions) should run the most recent version available to ensure
 that security issues arising during the development are addressed
 as quickly as possible. Furthermore, unreleased versions should
 not be used in a production environment.

__________________________________________________________________

Workarounds:

 We recommend that you upgrade rather than try to workaround the
 issues by configuration. To most of the issues there is no easy
 workarounds that does not severely impact the functionality.

 The Gopher and FTP issues can be worked around by denying proxying
 of ftp:// or gopher:// URLs, for example by inserting the following
 lines at the top of your squid.conf

   # Workaround for bugs in Squid-2.4.STABLE6 and earlier
   acl workaround proto FTP Gopher
   http_access deny workaround

 The authentication credentials issue only applies if you are using
 proxy authentication, allow users access to some sites without
 the need to authenticate and you do not fully trust these sites or
 the network between these sites and the proxy. To work around the
 problem make sure your users needs to authenticate on all sites or
 none.

 If you are using the msnt_auth authentication helper then you are
 only vulnerable if you are using the allowusers or denyusers
 extension of msnt_auth. To work around this defiance of msnt_auth
 you can use the proxy_auth acl type to specify the valid users
 and delete the allowusers and denyusers files.

__________________________________________________________________

Contact details for the squid project:

 For installation / upgrade support: Your first point of contact
 should be your binary package vendor.

 If your install is built from the original squid sources, then
 the squid-users@squid-cache.org mailing list is your primary
 support point. (see 
 for subscription details).

 For bug reporting, particularly security related bugs the
 squid-bugs@squid-cache.org mailing list is the appropriate forum.
 It's a closed list (though anyone can post) and security related
 bug reports are treated in confidence until the impact has been
 established. For non security related bugs, the squid bugzilla
 database should be used .

__________________________________________________________________

Credits:

 Olaf Kirch (formerly @ Caldera), for reporting the FTP and Gopher
 related issues

 MARA Systems AB, for sponsoring the development of patches to the
 FTP, Gopher, authentication and transfer encoding issues.

 Duane Wessels, for fixes to the MSNT auth helper

__________________________________________________________________

Revision history:

 2002-07-03 21:10 GMT Initial release
__________________________________________________________________
END

Linux Orbit reports “While discussing home firewall setups with a colleague, I was introduced to a name I had not heard before. He said that he had set up a floppy based firewall using Freesco. “What is Freesco?” I asked. “Is it based on SCO Unix?” No, as it turns out – it is a free Cisco router alternative based on Linux 2.0.38 and Ipfwadm that is very easy to setup.”

Nokia and IBM today
announced an agreement on digital content delivery for mobile applications
and services. Combining their expertise, Nokia and IBM will provide
wireless operators and service providers with a complete solution for
content management and delivery. According to the agreement, IBM will
market Nokia’s delivery server software for mobile content downloading. The
companies have also agreed to collaborate on secure content delivery
solutions, including digital rights management, according to industry-wide
open standards and specifications.
The solution combines the Nokia Delivery Server with IBM Digital Media
Factory framework and enables service providers to offer exciting new
content services for mobile users, such as Java based mobile games,
polyphonic MIDI ring tones, digital images, graphics, screen savers and
icons. The services built on the solution, called Digital Media for Mobile
Devices (DM Mobile), will allow users to fully leverage the advanced
features of mobile devices such as preview and seamless downloading of new
content.

Using a modular approach, future developments of the Nokia and IBM solution
will allow support for delivery and protection of a richer set of media
types. This will allow operators and service providers to leverage their
initial investment and increase their revenue streams.

“We are very pleased to work together with IBM on mobile content delivery
and provide service providers with a top-quality solution for rapidly
emerging services. Furthermore, we share the same view on an architecture
development for protected content and Digital Rights Management in the
mobile domain. Both Nokia and IBM have a strong commitment to drive and
adopt an open based DRM technology that will result in a rich set of new
services that are interoperable throughout networks and mobile devices,”
said Pertti Korhonen, executive vice president, Mobile Software, Nokia.

“This agreement pulls together the critical components necessary to support
the secure delivery of content,” said Dick Anderson, general manager of
IBM’s Digital Media group. “It enables new and exciting applications to be
created and delivered to new advanced mobile devices. IBM and Nokia are at
the forefront of protecting content from creation to delivery in a wireless
environment.”

The Nokia Delivery Server will become part of IBM’s Digital Media Factory
framework, based on a number of IBM core products and business partners,
which helps companies create, store, manage and distribute digital content
across the digital media value chain. IBM Global Services will sell and
support the resulting offering with consulting, installation, and
integration.

The Nokia Delivery Server software will also integrate with IBM’s Service
Provider Delivery Environment (SPDE — pronounced “speed-ee”), an open
standards based framework built on IBM’s WebSphere e-business
infrastructure software designed to give wireline and wireless service
providers the flexibility to introduce new revenue generating voice, text
and Internet-based services to their customers faster, easier and at a
lower cost. The Nokia Delivery Server is to be ported and made available
for use on IBM Linux-based eServer* xSeries** systems. Finally, the
combined IBM/Nokia Download Server solution will be supported and
demonstrated by the IBM Network Integration Laboratory in La Gaude, France
as a specific solution that is integrated with the IBM SPDE and Digital
Media Factory frameworks.

Both Nokia and IBM are active members of the newly formed Open Mobile
Alliance (OMA). OMA is the nearly 200-member company organization charged
with delivering open standards for the mobile industry, helping to create
interoperable services which work across countries, operators and mobile
terminals and are tailored for user’s needs.

About Nokia
Nokia is the world leader in mobile communications. Backed by its
experience, innovation, user-friendliness and secure solutions, the company
has become the leading supplier of mobile phones and a leading supplier of
mobile, fixed broadband and IP networks. By adding mobility to the Internet
Nokia creates new opportunities for companies and further enriches the
daily lives of people. Nokia is a broadly held company with listings on six
major exchanges. www.nokia.com.

About IBM
IBM is the world’s largest information technology company, with 80 years of
leadership in helping businesses innovate. IBM works with companies of all
sizes around the world to deploy the full range of IBM technologies,
products and services. IBM can be found on the web at http://www.ibm.com.

** Indicates trademark or registered trademark of International Business
Machines Corporation. All other trademarks or registered trademarks are
property of their respective owners.

Rajesh Goyal writes: “LinuxCertified,Inc. a leading provider of Linux training, will offer its next weekend system administration bootcamp on July 13-14, 2002 in San Francisco bay area (south bay). This workshop is designed for busy information technology professionals and is designed to cover the most important Linux administration areas. All attendees get a free Linux laptop.
In addition to carefully designed lecture material delivered by experienced Linux professionals, there is a heavy emphasis on hands-on learning. The training starts two weeks before the actual class, with access to an online Linux server, where students complete few challenging pre-class activities. Attendees get a powerful Linux laptop on their arrival, along with other class materials. They load Linux on their laptop during the class, and use it for all the class activities and assignments. At the end of the class they take this laptop with them to further enhance their Linux expertise. Absolute beginners with no UNIX experience can first come to the popular “Linux Fundamentals” class and subsequently join the system administration bootcamp.

Rapid growth of Linux into corporate and government IT environments is fueling the need for Linux certified professionals. CIOs and managers are eager to have Linux experts in their organizations. A certification provides a tangible mechanism for their hiring evaluation, as well as a means to market the prowess of organizations.

“As an independent IT consultant I am always on my toes to learn new technologies, without much free time to devote to classes. The LinuxCertified bootcamp was a perfect way for me to jump start my Linux knowledge. I can now use Linux as a valuable tool in my career,” said Taylor Cottam, an independent consultant who joined one of the LinuxCertified, Inc. weekend bootcamps.

This weekend bootcamp is specially designed to prepare the attendees for the objectives of Level 1 certification exams offered by Linux Professional Institute (LPI). The workshop also meets the objectives of the Red Hat Certified Engineer (RHCE) exam and Sair Linux & GNU certification (LCA). Our attendees build a strong sense of community with our instructors, fellow students, and our network of recruiters and companies looking for Linux consultants.

About LinuxCertified, Inc.

The mission of LinuxCertified, Inc. is to bring Linux to mainstream IT usage. We firmly believe that Linux has an enormous potential, once it crosses over from the early adopters to the more mainstream users. Our goal is to help this transition by providing:

– Linux trained and certified professionals
– Linux certified products that cater to mainstream users rather than early adopters.

Contact:
info@linuxcertified.com
http://www.linuxcertified.com/
Tel: 408 314 6700

————————————-
Linux is a registered trademark of Linus Torvalds.
All other names and trademarks are the property of their respective owners.

Anonymous Reader writes: The Linux Test Project test suite LTP-20020709.tgz has been released.
Visit our website ( http://ltp.sourceforge.net )to download the latest
version of the test suite, and, for information on test results on pre
release, release candidate and stable releases of the kernel.
There is also a list of test cases that are expected to fail, please find the list at http://ltp.sourceforge.net/expected-errors.php

We encourage the community to post results, patches or new tests on
our mailing list and use the CVS bug tracking facility to report problems that you might encounter with the test suite.
More details available at our web-site.

Anonymous Reader writes: Tuesday, July 9th, 2002 from the home of Wayne’s World, Aurora IL,
tonight LIVE on
www.thelinuxshow.com, at 6pm pt, 7pm mt, 8pm ct, and 9pm et, Kevin Hill, Jeff Gerhardt, Doc
Searls (Linux Journal), Arne Flones and Russ Pavlicek; have another strange and wonderful show lined up tonight on The Linux Show!!Segment One- The News. We will cover THE HOT NEWS of the last few weeks tonight. In particular, we will talk about the CARP backlash, and how the passage of the new oppresive web casting fees are starting to motiveate chants of Taxation without Representation, and we will also talk about the very sad news of Gene Kan’s death .

Segment Two- Tim O’Reilly And The Strange Case of the Disappearing Open Source Vendors

We will be joined tonight by publisher and technology maven Tim O’Reilly. Tim is the founder and CEO of O’Reilly & Associates, thought by many to be the elite computer book publisher in the world. O’Reilly also publishes online through the O’Reilly Network (www.oreillynet.com) and hosts conferences on technology topics (incluiding a very popular Open Source conference). Tim is
a respected activist for open source and open standards, and an opponent of software patents and other incursions of new intellectual property laws into the public domain.

Tonight, though we may meander our way through several issues with Tim (such as the high price of technology books  ;-)), our main focus will be to discuss Tim’s view of the “state of the industry” for Open Source vendors. Has something gone wrong? Or, are we where we should be with the development of Open Source as an industry model?

If you are in a band or represent an artist, please contact us asap to be added to our play list.
Please join us on the show, and check our IRC Chat(irc.thelinuxshow.com
#linuxshow).
Remember tune in at 6pm pt, 7pm mt, 8pm ct, and 9pm et. NOTE: we are now on
Daylight Saving Time in the US.
Catch the Linux show at www.thelinuxshow.com“

– By Robin “Roblimo” Miller –
There are millions of people who either write for a living or would like to, and these millions represent a potentially lucrative market for developers who want to look at writers’ software needs and fill them at a reasonable price. Best of all, there is no need for a developer who wants to tap this market to write much code from scratch. OpenOffice is a fine base for writers’ software, especially for a developer who realizes that professional writers need software that will help them do more than just pound out words.

Different writers need different tools

I’ve attended more than a few writers’ group meetings in my time, and mentally I break writers into three categories:

• Pure artists. They write poetry, short stories, or relationship-based movie scripts, and have little or no chance of making a living selling their work (although they may not realize this). Artist-writers tend to spend a lot of time trying to figure out where to submit work for publication or production, and just as much time wondering what they can do to get editors’ or producers’ attention.

• Aspiring writers. These are the ones who try to write non-fiction articles, “commercial” fiction, and scripts for movies or TV shows that fall into genre categories easily understood by mainstream producers. They obsess over rejections, but exhort each other to keep trying in face-to-face groups, online forums, and in the pages of magazines like Writer’s Digest. The reality is that most of the people in this category can’t write very well, but they buy lots of books, magazines and software they hope will help them improve or find better markets for their work. Enough in this category gut it out and succeed to give others hope. Great market here!

• Working writers. Go to a meeting of working writers (or get on one of the many writers’ email lists) and you hear discussions about which publishers or producers are buying what from whom, and who pays how much and how promptly. Suddenly the majority of talk is about the business of writing, not about writing, because everyone in these groups has already learned how to write.

Obviously all three categories of writers need basic word processing, spell checking, and other text-production utilities to function. Screenwriters need specific formats — really just templates that could be made rather easily for OpenOffice and inserted into the menus so that they would be easy to find and open. Writers who specialize in other media may also want specialized templates. For instance, many book and article writers would rather have a “galley” format that puts all text into an endless file rather than breaking it up page by page as OpenOffice does by default.

Another thing both professional and aspiring writers need is a flexible word count utility, one that displays a running total, can leave certain words or blocks of words (like title and other “header” information) out of that count, and can rapidly count highlighted blocks of text. Many writers get paid by the word, and even newspaper and magazine staff writers who get salaries must often write articles that are as close as possible to 700, 1,000, 1,500 or some other arbitrary number of words in length.

An alternative length determination option that would be a real sales feature for many writers and editors would be a “column inches” or “column centimeters” count that could be set to match a given publication’s style. Quite often, especially near deadline, publications are juggling space tightly. A staff writer or editor may need to fit four articles into a given amount of space quickly, and might be juggling lengths of all four articles while a layout person is screaming at them to hurry up. A word processing program that could be set to match that publication’s column width, and used a font with the same character sizes and spacing the publication used and display a running “column inches” total, would be an invaluable tool for rushed editorial people. (This feature would certainly help spur mass sales to newspaper and magazine publishing companies.)

There are other features I’m sure other writers and editors might need, and a programmer who wanted to make a living selling software to writers ought to poll writers to see what those features might be. There are plenty of writer’s Web sites and online discussion groups around. Doing this bit of market research would cost nothing except time.

The business side of writing

Writing is a business. A professional freelance writer sends out article queries and expects to get responses from editors about them within a reasonable period of time. “Reasonable” can vary from publication to publication. Because many writers do not like to submit the same story idea to more than one editor at a time, tracking submissions is essential. The OpenOffice spreadsheet utility could easily be modified to do submission tracking.

The next phase of the writing business is turning out work on time. A professional writer — either staff or freelance — is often juggling many deadlines. Freelancers, especially, need to keep close track of what is due when, and to schedule their time appropriately. The more work a freelancer can turn out, the more money he or she earns. But deadline-blowing is a sure way to irritate editors and get them to stop giving you assignments. It’s a juggling act for the freelancer, and software that could make it easier is good, especially if that software is part of a single “Writing Software” package that can do many other things too, all for one low price.

One of those other things, of course, must be billing and collection. Some publishers pay quickly, and some don’t. Some require invoices in a particular format, others don’t really care. Some publications pay “on acceptance” while others don’t pay until an article is published, and in the case of many magazines, an article may not run for months after it is accepted, so it is easy for a busy writer to forget who is supposed to pay how much when. A single, easy-to-use application that could handle a writer’s submissions, acceptance, billing, and collections tracking would be wonderful, especially if it could generate invoices and print envelopes (which OpenOffice can), and a utility or plugin that could track expenses and assign them to individual articles might also be nice, although it might be wise to ask some of those writers’ group denizens if this is truly necessary — or if there are other business-type features they feel are more important.

Already a proven marketplace

There is no shortage of “writers’ software” already available for sale. A glance at the Writers SuperCenter site will show you lots of opportunities I haven’t mentioned. Note that all almost all of these programs assume a writer uses something like MS Word as his or her basic word processor, and it really isn’t a particularly good one for writers. There has been surprisingly little work done to make a true “Writers’ Word Processor,” and I believe one would sell rather well, especially if it was a true standalone program based on OpenOffice that could sell for less than MS Word or MS Office, and would sell even better if it was priced at $99 or less, which ought to be an entirely achievable price.

Remember, OpenOffice runs happily on both Linux and Windows, and a Mac OS X version is coming soon, so any writers’ program based on it could be truly cross-platform. This is good. Since many writers — especially aspiring ones — don’t have a lot of money, the idea that they can get a cheap writing and word processing program instead of springing for expensive Microsoft products is a huge advantage, especially if that program is better for a writer’s needs than Ms Word or MS Office.

“Better than” is the key. Not “nearly as good as, but cheaper,” but better. Price is not everything. For professional writers, especially, the quality of a tool can be more important than its cost, and the smart ones will happily pay for the best tools, just as professional mechanics learn, through sad experience, to buy the best tools, not the cheapest ones — and also learn that the best tools are not necessarily the ones with the highest price tags.

There is a happy medium in here somewhere. I don’t know where it is. This is why I keep saying the thing to do before writing code is to get on writers’ email lists and ask questions. One of those questions should be, “How much is this feature worth to you?”

One of many niches

This essay has focused on one little market niche, and one particular piece of Open Source software. How many similar needs waiting to be filled are out there? How many Open Source programs work well but lack features needed to make them commercially viable, features that could become “add on” software that wouldn’t violate the base program’s Open Source or Free Software license? More people need to be asking this question — and answering it, and the people who need to be doing the most asking and answering are those who are doing the original Open Source development, because they deserve to reap the fruits of their labors more than anyone else.

More money going to Open Source developers is good. There are also many pieces of software the rest of the world could use that can be developed more rapidly and inexpensively from an Open Source base than from a proprietary software base.

I see this as the next wave in Open Source development. It’s really already here. Now it needs to spread, and it will, without a great deal of prompting, because it makes absolute economic sense for both developers and users.

ZDNet UK has the report. “A San Francisco developer has begun beta-testing the first software designed to let Linux users access Apple’s popular music device.”