Date: Tue, 12 Jul 2016 19:31:46 -0300 From: "Danilo G. Baio" <dbaio@bsd.com.br> To: Kurt Jaeger <lists@opsec.eu> Cc: freebsd-ports@freebsd.org Subject: Re: security/w3af update Message-ID: <CAKZCxeUz4PY_51X6QDCHRa03uR=-Jpz49T%2BaJBv_v2ELLGTzmQ@mail.gmail.com> In-Reply-To: <20160712104323.GG95302@home.opsec.eu> References: <CAKZCxeX241-ggomApQXF1rGwE7a8XAk8-xr5oCp7P5bCKOmUQw@mail.gmail.com> <20160712104323.GG95302@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 12, 2016 at 7:43 AM, Kurt Jaeger <lists@opsec.eu> wrote: > Hi! > > > I wrote an update for security/w3af and the hole was deeper than I > thought. > > Thanks! That looks very interesting! > > > It was necessary several new ports as dependency: > [...] > > I did not open a PR yet... I am wondering if is better open a new PR for > > each dependency or just one PR for security/w3af, anyone could help ? > > If you create PRs for each depend and link them to the main PR for > the security/w2af update, that would be the recommended way. > > > There are still a few issues to be resolved and plugins to be tested. > This > > happens with me too: > > https://github.com/andresriancho/w3af/issues/13636 > > > > The patch is here: > > http://dbaio.bs2cloud.com.br/FreeBSD/w3af/w3af_1.6.49.patch > > If you can add that patch to the port ? Hi! Thanks for your answer. It's done. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211061 Regards. -- Danilo G. Baio (dbaio)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKZCxeUz4PY_51X6QDCHRa03uR=-Jpz49T%2BaJBv_v2ELLGTzmQ>