Date: Thu, 08 Mar 2018 18:48:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 226458] www/chromium: unbundle libvpx Message-ID: <bug-226458-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226458 Bug ID: 226458 Summary: www/chromium: unbundle libvpx Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: jbeich@FreeBSD.org CC: chromium@FreeBSD.org, kde@FreeBSD.org Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) Flags: maintainer-feedback?(kde@FreeBSD.org), maintainer-feedback?(chromium@FreeBSD.org) CC: chromium@FreeBSD.org, kde@FreeBSD.org According to Mozilla v1.6.1 needs at least ports r460753 and ports r463848, Android - ports r463910. There're probably more, so staying on anything but= the latest version is a security risk given the lack of sandboxing. - www/chromium: bundles libvpx v1.6.1-1403-gcbe62b9c2 - www/iridium: bundles libvpx v1.6.1-263-g8121f8547 - www/qt5-webengine: bundles libvpx v1.6.0-702-g5c64c01 https://security-tracker.debian.org/tracker/source-package/libvpx --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226458-13>