OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 08-Mar-2004 15:10:09
Branch: HEAD Handle: 2004030814100900
Modified files:
openpkg-web/security OpenPKG-SA-0000.000-template.txt
Log:
update template for OpenPKG 2.0
Summary:
Revision Changes Path
1.17 +13 -13 openpkg-web/security/OpenPKG-SA-0000.000-template.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/security/OpenPKG-SA-0000.000-template.txt
============================================================================
$ cvs diff -u -r1.16 -r1.17 OpenPKG-SA-0000.000-template.txt
--- openpkg-web/security/OpenPKG-SA-0000.000-template.txt 8 Jan 2004 08:02:14
-0000 1.16
+++ openpkg-web/security/OpenPKG-SA-0000.000-template.txt 8 Mar 2004 14:10:09
-0000 1.17
@@ -12,13 +12,13 @@
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= foo-1.2.4-20040123 >= foo-1.2.4-20049124
+OpenPKG 2.0 <= foo-1.2.3-2.0.0 >= foo-1.2.3-2.0.1
OpenPKG 1.3 <= foo-1.2.3-1.3.0 >= foo-1.2.3-1.3.1
-OpenPKG 1.2 <= foo-1.2.3-1.2.0 >= foo-1.2.3-1.2.1
Affected Releases: Dependent Packages:
OpenPKG CURRENT bar quux
-OpenPKG 1.3 bar quux
-OpenPKG 1.2 bar
+OpenPKG 2.0 bar quux
+OpenPKG 1.3 bar
Description:
According to a ... security advisory based on hints from ...
@@ -38,19 +38,19 @@
[5][6], fetch it from the OpenPKG FTP service [7][8] or a mirror
location, verify its integrity [9], build a corresponding binary RPM
from it [3] and update your OpenPKG installation by applying the binary
- RPM [4]. For the current release OpenPKG 1.3, perform the following
+ RPM [4]. For the current release OpenPKG 2.0, perform the following
operations to permanently fix the security problem (for other releases
adjust accordingly).
$ ftp ftp.openpkg.org
ftp> bin
- ftp> cd release/1.3/UPD
- ftp> get foo-1.2.3-1.3.1.src.rpm
+ ftp> cd release/2.0/UPD
+ ftp> get foo-1.2.3-2.0.1.src.rpm
ftp> bye
- $ <prefix>/bin/rpm -v --checksig foo-1.2.3-1.3.1.src.rpm
- $ <prefix>/bin/rpm --rebuild foo-1.2.3-1.3.1.src.rpm
+ $ <prefix>/bin/openpkg rpm -v --checksig foo-1.2.3-2.0.1.src.rpm
+ $ <prefix>/bin/openpkg rpm --rebuild foo-1.2.3-2.0.1.src.rpm
$ su -
- # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/foo-1.2.3-1.3.1.*.rpm
+ # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/foo-1.2.3-2.0.1.*.rpm
Additionally, we recommend that you rebuild and reinstall
all dependent packages (see above), if any, too. [3][4]
@@ -62,10 +62,10 @@
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-...
[3] http://www.openpkg.org/tutorial.html#regular-source
[4] http://www.openpkg.org/tutorial.html#regular-binary
- [5] ftp://ftp.openpkg.org/release/1.2/UPD/foo-1.2.3-1.2.1.src.rpm
- [6] ftp://ftp.openpkg.org/release/1.3/UPD/foo-1.2.3-1.3.1.src.rpm
- [7] ftp://ftp.openpkg.org/release/1.2/UPD/
- [8] ftp://ftp.openpkg.org/release/1.3/UPD/
+ [5] ftp://ftp.openpkg.org/release/1.3/UPD/foo-1.2.3-1.3.1.src.rpm
+ [6] ftp://ftp.openpkg.org/release/2.0/UPD/foo-1.2.3-2.0.1.src.rpm
+ [7] ftp://ftp.openpkg.org/release/1.3/UPD/
+ [8] ftp://ftp.openpkg.org/release/2.0/UPD/
[9] http://www.openpkg.org/security.html#signature
________________________________________________________________________
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
