Update Announcement Format discussion

Jesse Keating jkeating at j2solutions.net
Sat Jan 10 22:18:47 UTC 2004


On Friday 09 January 2004 00:42, Warren Togami wrote:
> Please suggest a formatted template that contains all the usual
> things you find in security announcements for packages.  Don't forget
> md5sums, GPG keyid, URLs.  We should create a legacy advisory
> numbering system, and standardized Subject line.  Message subjects
> would then be something like "Fedora Legacy Advisory FL000425: libfoo
> format string vulnerability".
>
> Once you write the advisory template, fill in that template with
> sample information for the libfoo update so we can be sure our
> advisory format works.
>
> After we agree upon that template, then the draft for the mpg321
> no-package Legacy security advisory must be written advising users
> about the license issue preventing update, and suggestion to remove
> mpg321.
>
> Then lastly someone must emerge as a leader for this project, and
> perhaps create a "Fedora Legacy Advisory" GPG key for signing these
> announcements before they go to the various mailing lists.

Although I've been slightly busy this last couple weeks, I'm still here 
to try and lead this thing.  With your help, I'm willing to create the 
GPG key, shop it around for signing and start pushing these 
announcements.

> Jesse do you know if we got those other mailing lists?

Lists have been requested, waiting for approval.


Here is what I have as an example layout:

Subject: [FLSA-2004:${bugzillaID}] Updated sendmail resolves security 
vulnerability

clearsigned GPG

-----------------------------------------------------------------------
               Fedora Legacy Update Advisory

Synopsis:          Updated sendmail resolves security vulnerability
Advisory ID:       FLSA:${bugzillaID}
Issue date:        2004-01-05
Updated on:        2004-01-05
Product:           Red Hat Linux
Keywords:          Security/Bugfix
Cross references:  Bugzillasystem/ID
Obsoletes:         
CVE Names:         CAN-2003-0984 CAN-2003-0985
-----------------------------------------------------------------------

1. Topic:

Updated sendmail packages are now available that fix a security 
vulnerability which may allow local users to gain root privileges.

2. Relevant releases/architectures:

Red Hat Linux 7.1 - athlon, i386, i586, i686
Red Hat Linux 7.2 - athlon, i386, i586, i686
Red Hat Linux 7.3 - athlon, i386, i586, i686
Red Hat Linux 8.0 - athlon, i386, i586, i686
Red Hat Linux 9 - athlon, i386, i586, i686

3. Problem description:

Sendmail handles the functions of an MTA on Linux systems.

${PERSON} discovered a flaw in some function of sendmail
versions 2.4.23 and previous which may allow a local attacker to
gain root privileges.  No exploit is currently available; however, it is
believed that this issue is exploitable (although not trivially.) The
Common Vulnerabilities and Exposures project (cve.mitre.org) has 
assigned the name CAN-2003-0985 to this issue.

All users are advised to upgrade to these errata packages, which contain 
a backported security patch that corrects this issue.

4. Solution:

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade.  Only those
RPMs which are currently installed will be updated.  Those RPMs which 
are not installed but included in the list will not be updated.  Note 
that you can also use wildcards (*.rpm) if your current directory 
*only* contains the desired RPMs.

Please note that this update is also available via yum and apt.  Many
people find this an easier way to apply updates.  To use yum issue:

yum update

or to use apt:

apt-get update

This will start an interactive process that will result in the 
appropriate RPMs being upgraded on your system.  This assumes that you 
have yum or apt-get configured for obtaining Fedora Legacy content.  
Please visit http://www.fedoralegacy.org/download for directions on how 
to configure yum and apt-get.

5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):

${BUGZILLA_SYSTEM} - 90338 - Security flaw found in Sendmail

6. RPMs required:

Red Hat Linux 7.1:

SRPMS:
ftp://download.fedoralegacy.org/7.1/en/os/SRPMS/sendmail-2.4.20-28.7.src.rpm

athlon:
ftp://download.fedoralegacy.org/7.1/en/os/athlon/sendmail-2.4.20-28.7.athlon.rpm

(So on and so forth)

end clearsign GPG

I'd like to develop some kind of web form that only the authorized 
people will have access to that we can plug values into and hit submit 
that will send it out and keep an online copy of it somewhere within 
fedoralegacy.org so that folks can reference it as well as the bugzilla 
ID.

Thoughts?

-- 
Jesse Keating RHCE MCSE (geek.j2solutions.net)
Fedora Legacy Team      (www.fedora.us/wiki/FedoraLegacy)
Mondo DevTeam           (www.mondorescue.org)
GPG Public Key          (geek.j2solutions.net/jkeating.j2solutions.pub)
 
Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating





More information about the fedora-legacy-list mailing list