OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Project Master
Root: /v/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 23-Jun-2005 20:33:40
Branch: HEAD Handle: 2005062319334000
Modified files:
openpkg-web/security OpenPKG-SA-2005.011-shtool.txt
Log:
release OpenPKG Security Advisory 2005.011 (shtool)
Summary:
Revision Changes Path
1.4 +17 -8 openpkg-web/security/OpenPKG-SA-2005.011-shtool.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/security/OpenPKG-SA-2005.011-shtool.txt
============================================================================
$ cvs diff -u -r1.3 -r1.4 OpenPKG-SA-2005.011-shtool.txt
--- openpkg-web/security/OpenPKG-SA-2005.011-shtool.txt 23 Jun 2005
14:29:09 -0000 1.3
+++ openpkg-web/security/OpenPKG-SA-2005.011-shtool.txt 23 Jun 2005
18:33:40 -0000 1.4
@@ -1,3 +1,6 @@
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
@@ -100,17 +103,16 @@
Please check whether you are affected by running "<prefix>/bin/openpkg
rpm -q shtool". If you have the "shtool" package installed and its
version is affected (see above), we recommend that you immediately
- upgrade it (see Solution) and its dependent packages (see above), if
- any, too [4][5].
+ upgrade it (see Solution) [3][4].
Solution:
Select the updated source RPM appropriate for your OpenPKG release
- [6], fetch it from the OpenPKG FTP service [7] or a mirror
- location, verify its integrity [8], build a corresponding binary RPM
- from it [3] and update your OpenPKG installation by applying the
- binary RPM [5]. For the most recent release OpenPKG 2.3, perform the
- following operations to permanently fix the security problem (for
- other releases adjust accordingly).
+ [6], fetch it from the OpenPKG FTP service [7] or a mirror location,
+ verify its integrity [8], build a corresponding binary RPM from it [3]
+ and update your OpenPKG installation by applying the binary RPM [5].
+ For the affected release OpenPKG 2.3, perform the following operations
+ to permanently fix the security problem (for other releases adjust
+ accordingly).
$ ftp ftp.openpkg.org
ftp> bin
@@ -145,3 +147,10 @@
for details on how to verify the integrity of this advisory.
________________________________________________________________________
+-----BEGIN PGP SIGNATURE-----
+Comment: OpenPKG <[EMAIL PROTECTED]>
+
+iD8DBQFCuwBMgHWT4GPEy58RAhbpAJ97hyBv9hd+Z6tHo0AaC34O4puVugCgjSZ7
+kG885jFAJ+kCHvIcEKAufSc=
+=bIdp
+-----END PGP SIGNATURE-----
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [email protected]
