Re: New pkg audit / vuln.xml failures (php55, unzoo)

Please send these things to ports-sect...@freebsd.org so that they can have a look at these please. Thanks, Remko > On 23 May 2015, at 17:30, Roger Marquis wrote: > > FYI regarding these new and significant failures of FreeBSD security > policy and procedures. > > PHP55 vulnerabilities announ

Re: New pkg audit / vuln.xml failures (php55, unzoo)

On Sat, May 23, 2015 at 11:30 AM, Roger Marquis wrote: > If you find a vulnerability such as a new CVE or mailing list > announcement please send it to the port maintainer and > as quickly as possible. They are whoefully > understaffed and need our help. Though freebsd.org indicates that > secu

Re: New pkg audit / vuln.xml failures (php55, unzoo)

Is it enough to only update php55? I could create a patch with relative easyness in that case. 2015-05-23 17:30 GMT+02:00 Roger Marquis : > FYI regarding these new and significant failures of FreeBSD security > policy and procedures. > > PHP55 vulnerabilities announced over a week ago >

New pkg audit / vuln.xml failures (php55, unzoo)

FYI regarding these new and significant failures of FreeBSD security policy and procedures. PHP55 vulnerabilities announced over a week ago ) have still not been ported to lang/php55. You can, however, edit the Makefile, increment the POR

rubygem databases conflicting file placement

As there have been a few updates to rubygem ports occurring, would someone be able to look into why these ports: /usr/ports/databases/rubygem-arel3 2014-08-27 /usr/ports/databases/rubygem-activerecord 2015-04-03 place files into the same location and cause conflict? I've added the dates of when

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you