Date: Fri, 5 May 2017 11:47:30 -0400 From: Jim Ohlstein <jim@ohlste.in> To: Jos Chrispijn <bsdports@cloudzeeland.nl> Cc: freebsd-ports@freebsd.org, jkim@freebsd.org Subject: Re: ICU Portupdate faulty Message-ID: <6a8922fa-c8ac-91d9-4025-d003b772e336@ohlste.in> In-Reply-To: <8d3c7d80-d51e-3743-eb41-d6633c498153@cloudzeeland.nl> References: <1c87d7b6-54f7-77f0-7476-338bd24aee54@cloudzeeland.nl> <CAByVWPVRp4PnW0Fm26aL_TW4R9BUtOQvn9XEEaQtJFqHMz3xaA@mail.gmail.com> <8d3c7d80-d51e-3743-eb41-d6633c498153@cloudzeeland.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On 05/05/2017 11:37 AM, Jos Chrispijn wrote: > I am really not a fan of that. > > Better would be to solve the 'vulneratbilities' issue. > /Jos The vulnerabilites are outlined in http://www.vuxml.org/freebsd/607f8b57-7454-42c6-a88a-8706f327076d.html and appear to be patched in devel/icu 58.2_2,1 committed yesterday. See https://svnweb.freebsd.org/ports?view=revision&revision=440117. > > Op 5-5-2017 om 17:24 schreef mokhi: >> It seems the port has known vulnerabilities. >> If you are sure about what you are doing, run the make command with >> "DISABLE_VULNERABILITIES=yes" option as it suggests. -- Jim Ohlstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a8922fa-c8ac-91d9-4025-d003b772e336>