From owner-freebsd-vuxml@FreeBSD.ORG Fri Dec 17 18:50:02 2004 Return-Path: Delivered-To: freebsd-vuxml@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 927A116A4CE for ; Fri, 17 Dec 2004 18:50:02 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFA143D1F for ; Fri, 17 Dec 2004 18:50:02 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 7A0C611D76; Fri, 17 Dec 2004 19:50:00 +0100 (CET) Date: Fri, 17 Dec 2004 19:50:00 +0100 From: "Simon L. Nielsen" To: Dan Langille Message-ID: <20041217185000.GB762@zaphod.nitro.dk> References: <41C2D30F.16142.730D56B@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline In-Reply-To: <41C2D30F.16142.730D56B@localhost> User-Agent: Mutt/1.5.6i cc: freebsd-vuxml@freebsd.org Subject: Re: Do you respect the date_modified field? X-BeenThere: freebsd-vuxml@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documenting security issues in VuXML List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2004 18:50:02 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.12.17 12:37:35 -0500, Dan Langille wrote: > At present, FreshPorts deletes all VuXML information each time a=20 > commit to ~/ports/security/vuxml/vuln.xml occurs. To reduce database=20 > churn, I'm now looking at optimizing this process. >=20 > I expect the answer to my question to be yes, but do not want to rely=20 > upon only my expectation. Do you respect the date_modified field? In general yes, though of course there can be slips sometimes. Of course, if FreshPorts starts to use the modified date I think it's even more likely that modified date will be updated correctly since people will notice if it wasn't bumped. I almost always check my entries on FreshPorts after commit as an extra check that I havn't made any mistakes in the committed entry... > I ask for reasons of keeping things simple. FreshPorts inserts each=20 > vuln into a table. Is it sufficient for FreshPorts to compare the=20 > last_modified field as supplied in vuln.xml to determine whether or=20 > not it should update its information? Not quite that simple unfortunatly. Modified date is not updated when an entry is modified the same day as when it was originally added, or if the modified date already has been bumped once on the date of the commit. So you need to update for all entries which has either modification or entry date today... actually you probably need to take entries from the date before and after also due to timezone's. But that should still reduce the number of entries that must bed update considerably. Actually it should be rather simple to generate the real modification date for each entry using "cvs annotate vuln.xml"... I might play around with that later today :-). --=20 Simon L. Nielsen --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBwypXh9pcDSc1mlERAhZwAKDKPr5SKpHs38E42LfFxuDOZWA9HgCfbJ+L /t83+vBmxwsDjs0W22PeXvk= =9H4I -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc--