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:   12-Mar-2004 15:48:01
  Branch: HEAD                             Handle: 2004031214480100

  Modified files:
    openpkg-web/security    OpenPKG-SA-0000.000-template.txt

  Log:
    add fake signing headers to template for easier line-by-line
    comparison with existing SAs; avoid word "current" when talking about
    a release by replacing it with term "most recent"

  Summary:
    Revision    Changes     Path
    1.18        +7  -4      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.17 -r1.18 OpenPKG-SA-0000.000-template.txt
  --- openpkg-web/security/OpenPKG-SA-0000.000-template.txt     8 Mar 2004 14:10:09 
-0000       1.17
  +++ openpkg-web/security/OpenPKG-SA-0000.000-template.txt     12 Mar 2004 14:48:01 
-0000      1.18
  @@ -1,3 +1,6 @@
  +-----BEGIN PGP SIGNED MESSAGE-----            #FIXME, this is a template
  +Hash: SHA1                                    #FIXME, this is a template
  +                                              #FIXME, this is a template
   ________________________________________________________________________
   
   OpenPKG Security Advisory                            The OpenPKG Project
  @@ -37,10 +40,10 @@
     Select the updated source RPM appropriate for your OpenPKG release
     [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 2.0, perform the following
  -  operations to permanently fix the security problem (for other releases
  -  adjust accordingly).
  +  from it [3] and update your OpenPKG installation by applying the
  +  binary RPM [4]. For the most recent 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
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to