From:
[email protected]
Package: stunnel4
Version: 2:4.050-2
The current policy of making /var/run/stunnel4 owned by nobody:nogroup
is less than ideal. The nobody user should never own any files,
likewise no files should ever have group nobody due to the potential
for cross contamination. Giving stunnel its own system user/group
would improve things considerably. The current stunnel4 package
works against admins who've made this change by hand; everytime its
reinstalled it changes the /var/run/stunnel4 directory's ownership
back to nobody:nogroup. In my configuration, this led to the stunnel
service not surviving the most recent upgrade because it was unable to
write its pid file.
--
Jamie Heilman
http://audible.transient.net/~jamie/
"Most people wouldn't know music if it came up and bit them on the ass."
-Frank Zappa
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)