I'm not Linux fanboy, but modern squid never runs as root. So,
most probably it runs as nobody user.
Ah, yes:
# TAG: cache_effective_user
# If you start Squid as root, it will change its effective/real
# UID/GID to the user specified below. The default is to
change
# to UID of nobody.
# see also; cache_effective_group
#Default:
# cache_effective_user nobody
# TAG: cache_effective_group
# Squid sets the GID to the effective user's default group ID
# (taken from the password file) and supplementary group list
# from the groups membership.
#
# If you want Squid to run with a specific GID regardless of
# the group memberships of the effective user then set this
# to the group (or GID) you want Squid to run as. When set
# all other group privileges of the effective user are ignored
# and only this GID is effective. If Squid is not started as
# root the user starting Squid MUST be member of the specified
# group.
#
# This option is not recommended by the Squid Team.
# Our preference is for administrators to configure a secure
# user account for squid with UID/GID matching system policies.
#Default:
# Use system group memberships of the cache_effective_user account
As documented. :)
AFAIK best solution is create non-privileged group & user
(like squid/squid) and set both this parameters explicity.
Then change owner recursively on SSL cache to this user.
12.09.2017 0:36, Rohit Sodhia пишет:
Neither of those values are set in my config. Even
though I'm not using squid for caching, I need those values?
They aren't set in the default configs either.
|
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users