| 1 |
# -*- text -*- |
| 2 |
###################################################################### |
| 3 |
# |
| 4 |
# Control socket interface. |
| 5 |
# |
| 6 |
# In the future, we will add username/password checking for |
| 7 |
# connections to the control socket. We will also add |
| 8 |
# command authorization, where the commands entered by the |
| 9 |
# administrator are run through a virtual server before |
| 10 |
# they are executed. |
| 11 |
# |
| 12 |
# For now, anyone who has permission to connect to the socket |
| 13 |
# has nearly complete control over the server. Be warned! |
| 14 |
# |
| 15 |
# This functionality is NOT enabled by default. |
| 16 |
# |
| 17 |
# See also the "radmin" program, which is used to communicate |
| 18 |
# with the server over the control socket. |
| 19 |
# |
| 20 |
# $Id: 97ba9ef972539af80dcaf84090b55d991095a93e $ |
| 21 |
# |
| 22 |
###################################################################### |
| 23 |
listen { |
| 24 |
# |
| 25 |
# Listen on the control socket. |
| 26 |
# |
| 27 |
type = control |
| 28 |
|
| 29 |
# |
| 30 |
# Socket location. |
| 31 |
# |
| 32 |
# This file is created with the server's uid and gid. |
| 33 |
# It's permissions are r/w for that user and group, and |
| 34 |
# no permissions for "other" users. These permissions form |
| 35 |
# minimal security, and should not be relied on. |
| 36 |
# |
| 37 |
socket = ${run_dir}/${name}.sock |
| 38 |
|
| 39 |
# |
| 40 |
# Peercred auth |
| 41 |
# |
| 42 |
# By default the server users the peercred feature of unix |
| 43 |
# sockets to get the UID and GID of the user connecting to |
| 44 |
# the socket. You may choose to disable this functionality |
| 45 |
# and rely on the file system for enforcing permissions. |
| 46 |
# |
| 47 |
# On most Unix systems, the permissions set on the socket |
| 48 |
# are not enforced, but the ones on the directory containing |
| 49 |
# the socket are. |
| 50 |
# |
| 51 |
# To use filesystem permissions you should create a new |
| 52 |
# directory just to house the socket file, and set |
| 53 |
# appropriate permissions on that. |
| 54 |
# |
| 55 |
# peercred = no |
| 56 |
# socket = ${run_dir}/control/${name}.sock |
| 57 |
|
| 58 |
# |
| 59 |
# The following two parameters perform authentication and |
| 60 |
# authorization of connections to the control socket. |
| 61 |
# |
| 62 |
# If not set, then ANYONE can connect to the control socket, |
| 63 |
# and have complete control over the server. This is likely |
| 64 |
# not what you want. |
| 65 |
# |
| 66 |
# One, or both, of "uid" and "gid" should be set. If set, the |
| 67 |
# corresponding value is checked. Unauthorized users result |
| 68 |
# in an error message in the log file, and the connection is |
| 69 |
# closed. |
| 70 |
# |
| 71 |
|
| 72 |
# |
| 73 |
# Name of user that is allowed to connect to the control socket. |
| 74 |
# |
| •75 |
# uid = freerad |
| 76 |
|
| 77 |
# |
| 78 |
# Name of group that is allowed to connect to the control socket. |
| 79 |
# |
| •80 |
# gid = freerad |
| 81 |
|
| 82 |
# |
| 83 |
# Access mode. |
| 84 |
# |
| 85 |
# This can be used to give *some* administrators access to |
| 86 |
# monitor the system, but not to change it. |
| 87 |
# |
| 88 |
# ro = read only access (default) |
| 89 |
# rw = read/write access. |
| 90 |
# |
| 91 |
# mode = rw |
| 92 |
} |