You're receiving this bug because the package in Summary has produced _FORTIFY_SOURCE related warnings indicating the presence of a sure overflow in a static buffer.
Even though this is not always an indication of a security problem it might even be. So please check this out ASAP.
By the way, _FORTIFY_SOURCE is disabled when you disable optimisation, so don't try finding out the cause using -O0.
Your friendly neighborhood tinderboxer
Created attachment 247488 [details]
Created attachment 260990 [details, diff]
Patch to fix buffer overflow
Created attachment 260991 [details]
ebuild to apply the patch
Hi Kevin, your patch here has still a problem: strncpy() doesn't ensure a final '\0' with the size provided, so it should be sizeof(dest)-1 rather than simply sizeof(dest). It takes away the warning because it won't hit the limit but it won't take care of terminating it properly, so further errors could creep afterwards. The interface you were expecting is strlcpy() which is not available in GLIBC.
Created attachment 261017 [details, diff]
Fixed patch to provide enough space for the \0
Nice catch... I should've known better, but it's been a while since I've done any heavy C development. Anyway, I've uploaded a corrected patch.
+*selfdhcp-0.2a-r1 (03 Mar 2012)
+ 03 Mar 2012; Pacho Ramos <firstname.lastname@example.org>
+ +files/selfdhcp-0.2a-buffer-overflow.patch, +selfdhcp-0.2a-r1.ebuild,
+ Fix overflow, bug #337520 by flameeyes and fix by Kevin McCarthy.