Date: Wed, 21 Oct 2015 06:22:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 203909] [MAINTAINER] devel/sope: Add CFLAGS supressing compiler warnings Message-ID: <bug-203909-13-YvzKO3YmoB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203909-13@https.bugs.freebsd.org/bugzilla/> References: <bug-203909-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203909 --- Comment #8 from Euan Thoms <euan@potensol.com> --- (In reply to Kubilay Kocak from comment #6) The _potential_ security implications are just that (AFAIK). There is no proven exploitable security flaw yet. Only that the kinds of coding errors the compiler warnings are highlighting are systematic of causing security issues. Along with less than obvious bugs. So, it's just good practice to clear these up and make the upstream code better quality. These compiler warnings aren't even the tip of the iceberg of a proper security audit. But every little helps. Marking the port with a security warning would be a premature assumption. There are no outstanding CVE's AFAIK. As for the CFLAGs, I will remove them from the Makefile and add them to my internal notes I keep on my github ports development branch. I'll update the patches for devel/sope www/sogo just now. -- 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-203909-13-YvzKO3YmoB>