Jul 242012
 

I noticed last night that the list of ‘Latest Vulnerabilities’ on dev and beta differ from that found on production. Specifically, prod lists entries for:

  1. php5 Jul 23
  2. php52 Jul 23
  3. php53 Jul 23
  4. rubygem-activemodel*

As previously noted, the new vuxml processing code is on the dev and beta servers, but not yet in production. I’ll be looking in this.

Website Pin Facebook Twitter Myspace Friendfeed Technorati del.icio.us Digg Google StumbleUpon Premium Responsive

  One Response to “vuxml not the same on production”

  1. I think I found it.

    $ cvs di -u process_vuxml.sh
    Index: process_vuxml.sh
    ===================================================================
    RCS file: /home/repositories/freshports-1/scripts/process_vuxml.sh,v
    retrieving revision 1.6
    diff -u -r1.6 process_vuxml.sh
    --- process_vuxml.sh    22 Jul 2012 12:05:21 -0000      1.6
    +++ process_vuxml.sh    24 Jul 2012 15:55:11 -0000
    @@ -46,9 +46,9 @@
            rm ${VUXMLFLAGFILE}
            logger -t "FreshPorts ${0}"  "vuxml processing begins"
            echo `date` "FreshPorts ${0}"  "vuxml processing begins"                  >> ${LOGFILE}
    -       /usr/bin/perl ./process_vuxml.pl -w < ${PORTSDIR}/security/vuxml/vuln.xml >> ${LOGFILE}
    +       /usr/bin/perl ./process_vuxml.pl < ${PORTSDIR}/security/vuxml/vuln.xml >> ${LOGFILE}
            logger -t "FreshPorts ${0}"  "vuxml ident begins"
    -       /usr/bin/perl ./vuxml_ident.pl        ${PORTSDIR}/security/vuxml/vuln.xml > ${BASEDIR}/dynamic/vuxml_revision
    +       /usr/bin/perl ./vuxml_ident.pl     ${PORTSDIR}/security/vuxml/vuln.xml > ${BASEDIR}/dynamic/vuxml_revision
            logger -t "FreshPorts ${0}"  "vuxml latest begins"
            /usr/bin/perl ./vuln_latest.pl
            rm ${VUXMLMUTEX}