Figured that out: files, referred to in config files for modules (under
/etc/raddbdir) must be referred to $chroot in case of running as unpriveleged
user in $chroot (in my case):
/etc/freeradius/mods-enabled/attr_filter:
attr_filter attr_filter.post-proxy {
key = "%{Realm}"
filename = /mychrootdir/myraddb/mods-config/${.:name}/post-proxy
}
This is messy, because in the file above the original prefix was
${modconfdir}, that is set in radiusd.conf. But changing it in
radiusd.conf to $chroot/raddb/mods-config does nothing. On the other
hand, the ${modconfdir} variable is set precisely for the use with those
module config files!
Then there are other problems...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730362
Title:
fails to start as user/group freerad (recommended!)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1730362/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
