[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] RE: [cobalt-announce] <<< Software Update Notification For RaQ 1, RaQ 2 , RaQ 3, and RaQ 4 >>>
- Subject: [cobalt-users] RE: [cobalt-announce] <<< Software Update Notification For RaQ 1, RaQ 2 , RaQ 3, and RaQ 4 >>>
- From: "GPS" <gps@xxxxxxxxxxxxxx>
- Date: Fri Feb 23 16:34:06 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
The URL coding is incorrect on the 2/22/01 Raq2 patch.
The ACTUAL file name is RaQ2-All-Security-3.0.2-9077.pkg
The web site shows:
http://ftp.cobalt.com/pub/packages/raq2/eng/RaQ2-All-Security-3.0.1-9077.pkg
>-----Original Message-----
>From: cobalt-announce-admin@xxxxxxxxxxxxxxx
>[mailto:cobalt-announce-admin@xxxxxxxxxxxxxxx]On Behalf Of Jared L.
>Height
>Sent: Friday, February 23, 2001 3:58 PM
>To: cobalt-announce@xxxxxxxxxxxxxxx
>Subject: [cobalt-announce] <<< Software Update Notification For RaQ 1,
>RaQ 2 , RaQ 3, and RaQ 4 >>>
>
>
>===================================
>Cobalt Networks, Inc.
>Software Update Notification
>2/23/01
>===================================
>
>Hello Fellow Cobalt Customers!
>
>This is one in a series of periodic notifications designed to keep you
>informed of recent software updates, as they become available to you.
>
>For a full description of these and other updates, please go to:
>http://www.cobalt.com/support/download/
>
>Or for those of you who want to get straight to business, please go to:
>ftp://ftp.cobalt.com/pub/packages/
>
>We strongly recommend that you apply any and all updates appropriate to your
>server appliance.
>
>Thank you very much.
>Jared L. Height
>
>
>===================================
>Software Updates For RaQ 1
>===================================
>RaQ1-All-Security-3.0.2-9077: Pine v4.33-C1 Update 3.0.2
>Upon abnormal exit, the text editor saves any changes made to the file being
>edited into a new file in the current working directory labeled
>filename.save (where filename will correspond to the name of the file being
>edited, e.g. test.txt will be saved as test.txt.save). When saving this
>file, the text editor does not check for the file type. A user editing a
>file in a directory writable by others could be subject to having other
>files written to if a malicious user were to symbolically link the
>filename.save file to one of owner/group write access of the user. This
>would result in the contents of the pico session being written to the
>symbolically linked file.
>
>This security update installs Pine v4.33-C1 which includes the latest Pico
>v4.0.
>
>
>===================================
>Software Updates For RaQ 2
>===================================
>RaQ2-All-Security-3.0.1-9077: Pine v4.33-C1 Update 3.0.1
>Upon abnormal exit, the text editor saves any changes made to the file being
>edited into a new file in the current working directory labeled
>filename.save (where filename will correspond to the name of the file being
>edited, e.g. test.txt will be saved as test.txt.save). When saving this
>file, the text editor does not check for the file type. A user editing a
>file in a directory writable by others could be subject to having other
>files written to if a malicious user were to symbolically link the
>filename.save file to one of owner/group write access of the user. This
>would result in the contents of the pico session being written to the
>symbolically linked file.
>
>This security update installs Pine v4.33-C1 which includes the latest Pico
>v4.0.
>
>
>===================================
>Software Updates For RaQ 3
>===================================
>RaQ3-All-Security-4.0.2-9077: Pine v4.33-C1 Update 4.0.2
>Upon abnormal exit, the text editor saves any changes made to the file being
>edited into a new file in the current working directory labeled
>filename.save (where filename will correspond to the name of the file being
>edited, e.g. test.txt will be saved as test.txt.save). When saving this
>file, the text editor does not check for the file type. A user editing a
>file in a directory writable by others could be subject to having other
>files written to if a malicious user were to symbolically link the
>filename.save file to one of owner/group write access of the user. This
>would result in the contents of the pico session being written to the
>symbolically linked file.
>
>This security update installs Pine v4.33-C1 which includes the latest Pico
>v4.0.
>
>
>RaQ3-en-System-4.0.7-9229: POP Before SMTP Relaying (English)
>RaQ3-ja-System-4.0.7-9229: POP Before SMTP Relaying (Japanese)
>When activated, a client using a RaQ3 for a mail server will be denied
>outgoing email relaying until the client checks the client's incoming email
>first. After authentication has been established when the client checked
>the client's incoming mail, outgoing mail relaying is then allowed.
>
>
>===================================
>Software Updates For RaQ 4
>===================================
>RaQ4-All-Security-1.0.2-9077: Pine v4.33-C1 Update 1.0.2
>Upon abnormal exit, the text editor saves any changes made to the file being
>edited into a new file in the current working directory labeled
>filename.save (where filename will correspond to the name of the file being
>edited, e.g. test.txt will be saved as test.txt.save). When saving this
>file, the text editor does not check for the file type. A user editing a
>file in a directory writable by others could be subject to having other
>files written to if a malicious user were to symbolically link the
>filename.save file to one of owner/group write access of the user. This
>would result in the contents of the pico session being written to the
>symbolically linked file.
>
>This security update installs Pine v4.33-C1 which includes the latest Pico
>v4.0.
>
>
>RaQ4-en-System-1.0.7-9229: POP Before SMTP Relaying (English)
>RaQ4-ja-System-1.0.7-9229: POP Before SMTP Relaying (Japanese)
>When activated, a client using a RaQ4 for a mail server will be denied
>outgoing email relaying until the client checks the client's incoming email
>first. After authentication has been established when the client checked
>the client's incoming mail, outgoing mail relaying is then allowed.
>
>
>==========================
>Jared L. Height, Webmaster
>Sun Microsystems
>Server Appliance Business Unit
>555 Ellis Street
>Mountain View, CA 94043
>Ph: (650) 623-2737
>www.cobalt.com
>==========================
>
>_______________________________________________
>cobalt-announce mailing list
>cobalt-announce@xxxxxxxxxxxxxxx
>http://list.cobalt.com/mailman/listinfo/cobalt-announce
>