From owner-freebsd-ports Fri Jul 14 22:12:10 2000 Delivered-To: freebsd-ports@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BC88337C2F0 for ; Fri, 14 Jul 2000 22:12:06 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA68523 for ; Fri, 14 Jul 2000 23:12:05 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id XAA01511 for ; Fri, 14 Jul 2000 23:11:56 -0600 (MDT) Message-Id: <200007150511.XAA01511@billy-club.village.org> To: ports@freebsd.org Subject: Version question/request Date: Fri, 14 Jul 2000 23:11:56 -0600 From: Warner Losh Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a version question/request. I'd like to create a script that runs in /etc/security that will produce output like the following: YOUR SYSTEM HAS THE FOLLOWING PORTS THAT HAVE KNOWN SECURITY ISSUES IN THE VERSION YOU ARE RUNNING: woofootd (have 2.1 need 2.2) qpooper (have 2.98 need 3.11) etc This works great most of the time, however there are times that it doesn't work. Those times are where we've either F'ed up a patch so there's a security hole or we patch it with a patch-xx file before the author can issue a new release. In these cases when the problem is fixed, I'd love the version number to change with (or soon after) the security patch goes into the tree. Does anybody have any good ideas on how to do the version number part of this? I was thinking of adding a known suffix like "-S1" for the first security fix "-S2" for the second, etc. Then when the author fixes it and generates his own version, the suffix goes away. This would give us wu-ftpd-2.6.1-S2 which will sort after 2.6.1 but before 2.6.2. Hmmm, that does assume that the author fixes it in his/her/its next release, so maybe some other tag is needed. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message