The ebuild for bind-9.3.2 uses enewuser/enewgroup during src_install(), which does not run when installing from a binary package. As a result the named user/group is not created. Additionally, when installing it from a binary package it errors during the chown commands in pkg_config() but does not die from the error, the installer is left believing that the package is installed correctly if they do not notice the errors during emerging. This might cause security concerns in some environments. The enewgroup/enewuser commands should probably be moved to a function that is run during binary package installs also, such as pkg_setup().
(In reply to comment #0) > The enewgroup/enewuser commands should probably be moved to a function that is > run during binary package installs also, such as pkg_setup(). Nah, this belongs to pkg_preinst()
(In reply to comment #1) > (In reply to comment #0) > > The enewgroup/enewuser commands should probably be moved to a function that is > > run during binary package installs also, such as pkg_setup(). > > Nah, this belongs to pkg_preinst() > In this case pkg_preinst() would work, since there are no dependencies on the user/group already existing before src_install(). However, there are ebuilds that perform the various chown/fowners functions in src_install(). Some of them don't bother to check if the user/group already exists or not during src_install() (mail-filter/p2scan, mail-filter/postgrey, for examples). Adding them in pkg_setup() would cover both situations, would it not? Why encourage shoddy coding?
*** This bug has been marked as a duplicate of 124680 ***
