--- /dev/null
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-common: extended-description-is-probably-too-short
+
+# There are a lot of these that should probably be tidied up, but
+# it's not a great priority.
+freeradius-common: hyphen-used-as-minus-sign
freeradius-config: breaks-without-version
freeradius-config: package-relation-with-self
+
+# There are example python scripts in the config, but it's the freeradius
+# package that includes dependencies on the python libraries.
freeradius-config: python-script-but-no-python-dep etc/freeradius/mods-config/python/*.py
+
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-config: extended-description-is-probably-too-short
-freeradius-dhcp: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-dhcp: extended-description-is-probably-too-short
freeradius-iodbc: binary-or-shlib-defines-rpath
+
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-iodbc: extended-description-is-probably-too-short
-freeradius-krb5: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-krb5: extended-description-is-probably-too-short
-freeradius-ldap: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-ldap: extended-description-is-probably-too-short
-freeradius-memcached: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-memcached: extended-description-is-probably-too-short
--- /dev/null
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-mysql: extended-description-is-probably-too-short
freeradius-postgresql: binary-or-shlib-defines-rpath
+
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-postgresql: extended-description-is-probably-too-short
-freeradius-redis: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-redis: extended-description-is-probably-too-short
--- /dev/null
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-rest: extended-description-is-probably-too-short
+++ /dev/null
-freeradius-utils: binary-or-shlib-defines-rpath
-freeradius-yubikey: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+freeradius-yubikey: extended-description-is-probably-too-short
freeradius: binary-or-shlib-defines-rpath
+
+# There's just too much documentation to register, and most of it isn't a
+# "book" or similar that really makes sense anyway. The lintian check is just
+# reporting a single file that happens to be .html in a sea of .txt and .rst
+# files...
+freeradius: possible-documentation-but-no-doc-base-registration
-libfreeradius3: binary-or-shlib-defines-rpath
+# There's plenty in the description of this package to identify
+# what it does.
+libfreeradius3: extended-description-is-probably-too-short
colon is specified, the second file will be used to filter the
responses to requests from the first. The number of requests and
filters must be the same. A summary of filter results will be displayed
-if -s is passed.
+if \-s is passed.
.IP \-F
Print the file name, packet number and reply code.
.IP \-h
.IP \-n\ \fInum_requests_per_second\fP
Try to send \fInum_requests_per_second\fP, evenly spaced. This option
allows you to slow down the rate at which radclient sends requests.
-When not using -n, the default is to send packets as quickly as
+When not using \-n, the default is to send packets as quickly as
possible, with no inter-packet delays.
Due to limitations in radclient, this option does not accurately send
The directory that contains the RADIUS configuration files. Defaults to
\fI/etc/raddb\fP.
.IP \-F\ \fIradutmp_file\fP
-The file that contains the radutmp file. If this is specified, -d is
+The file that contains the radutmp file. If this is specified, \-d is
not necessary.
.IP \-i
Shows the session ID instead of the full name.
.SH OPTIONS
.IP -d
-Enable printing of debugging informations.
+Enable printing of debugging information.
.IP nas-type
Type of port/NAS. Can be one of:
..
.TH radrelay.conf 5 "27 May 2005" "" "FreeRADIUS configuration file"
.SH NAME
-radrelay.conf \- configuration file for the FreeRADIUS server "radrelay" personality
+radrelay.conf - configuration file for the FreeRADIUS server "radrelay" personality
.SH DESCRIPTION
The \fBradrelay.conf\fP file resides in the radius database directory,
by default \fB/etc/raddb\fP. It defines the global configuration for
.SH "BUFFERING FOR HIGH-LOAD SERVERS"
If the RADIUS server suddenly receives a many accounting packets,
there may be insufficient CPU power to process them all in a timely
-manner. This problem is especially noticable when the accounting
+manner. This problem is especially noticeable when the accounting
packets are going to a back-end database.
Similarly, you may have one database that tracks "live" sessions, and
Then, start the server via the following command:
-$ radiusd -n radrelay
+$ radiusd \-n radrelay
The server should start up, read the detail file, and process
accounting packets from it.
use '\fIradclient\fP to send the following packet to the server:
.PP
.DS
-$ radclient -f digest localhost auth testing123
+$ radclient \-f digest localhost auth testing123
.DE
Where 'digest' is a file containing:
.PP
To add an attribute to the RADIUS request (as though it had been sent
by the NAS), prefix the attribute name in the "format" string with the
-'~' character.
+\(aq~' character.
.PP
To add an attribute to the RADIUS reply (to be sent back to the NAS),
prefix the attribute name in the "format" string with the '='
The "session-state" list is primarily used for EAP. Attributes put
into the "session-state" list are saved for the next packet in the
-session. They are automatically retreived when the next packet is
+session. They are automatically retrieved when the next packet is
received.
The only contents permitted in an "update" section are attributes and
with a tab, and a (possibly empty) list of reply items. Each item in
the check or reply item list is an attribute of the form \fBname =
value\fP. Multiple items may be placed on one line, in which case
-they must be seperated by commas. The reply items may be specified
+they must be separated by commas. The reply items may be specified
over multiple lines, in which case each line must end with a comma,
and the last line of the reply items must not end with a comma.
.SH OPTIONS
-.IP "-d --des"
+.IP "\-d --des"
Use a DES (Data Encryption Standard) hash (default).
Ignored if performing a password check.
-.IP "-m --md5"
+.IP "\-m --md5"
Use a MD5 (Message Digest 5) hash.
Ignored if performing a password check.
-.IP "-c --check"
+.IP "\-c --check"
Perform a validation check on a password hash to verify if it matches
the plantext password.
.nf
$ radcrypt foobar
HaX0xn7Qy650Q
-$ radcrypt -c foobar HaX0xn7Qy650Q
+$ radcrypt \-c foobar HaX0xn7Qy650Q
Password OK
.fi
.SH SEE ALSO
Note that there are limitations to this check. Due to the
complexities involved in \fIalmost\fP starting a RADIUS server, these
checks are necessarily incomplete. The server can return a zero
-status code when run with -C, but may still exit with an error when
+status code when run with \-C, but may still exit with an error when
run normally.
See the output of
-.B "radiusd -XC"
+.B "radiusd \-XC"
for an informative list of which modules are checked for correct
configuration, and which modules are skipped, and therefore not checked.
.IP "\-d \fIconfig directory\fP"
.IP \-v
Print server version information and exit.
.IP \-X
-Debugging mode. Equivalent to "-sfxx -l stdout". When trying to
-understand how the server works, ALWAYS run it with "radiusd -X".
+Debugging mode. Equivalent to "\-sfxx \-l stdout". When trying to
+understand how the server works, ALWAYS run it with "radiusd \-X".
For production servers, use "raddebug"
.IP \-x
Finer-grained debug mode. In this mode the server will print details
of every request on it's \fBstdout\fP output. You can specify this
-option multiple times (-x -x or -xx) to get more detailed output.
+option multiple times (\-x \-x or \-xx) to get more detailed output.
.SH DEBUGGING
The default configuration is set to work in the widest possible
circumstances. It requires minimal changes for your system.
proceeding via the following steps:
.PP
1) Always run the server in debugging mode (
-.B radiusd -X
+.B radiusd \-X
) after making a configuration change. We cannot emphasize this
enough. If you are not running the server in debugging mode, you
\fIwill not\fP be able to see what is doing, and you \fIwill not\fP be
.br
.br
d) Start the server in debugging mode (
-.B radiusd -X
+.B radiusd \-X
), and start testing.
.in -0.3i
.PP
5) Ask questions on the mailing list
(freeradius-users@lists.freeradius.org). When asking questions,
include the output from debugging mode (
-.B radiusd -X
+.B radiusd \-X
). This information will allow people to help you. If you do not
include it, the first response to your message will be "post the
output of debug mode".
.PP
The access server also sends login and logout records to the \fBradius\fP
server so accounting can be done. These records are kept for each terminal
-server seperately in a file called \fBdetail\fP, and in the \fIwtmp\fP
+server separately in a file called \fBdetail\fP, and in the \fIwtmp\fP
compatible logfile \fB/var/log/radwtmp\fP.
.SH CONFIGURATION
\fBRadiusd\fP uses a number of configuration files. Each file has it's
marks escaped inside of the string.
Only one debug condition can be active at a time.
-.IP debug\ condition\ '((User-Name\ ==\ "bob")\ ||\ (Packet-Src-IP-Address\ ==\ 192.0.2.22))'
+.IP "debug condition '((User-Name == ""bob"") || (Packet-Src-IP-Address == 192.0.2.22))'"
A more complex condition that enables debugging output for requests
containing User-Name "bob", or requests that originate from source IP
address 192.0.2.22.
.SH "BUFFERING FOR HIGH-LOAD SERVERS"
If the RADIUS server suddenly receives a many accounting packets,
there may be insufficient CPU power to process them all in a timely
-manner. This problem is especially noticable when the accounting
+manner. This problem is especially noticeable when the accounting
packets are going to a back-end database.
Similarly, you may have one database that tracks "live" sessions, and
.SH NOTES
.SS Oracle driver
-The command "radsqlrelay -d oracle -b db.domain.tld sql-relay" reads the
+The command "radsqlrelay \-d oracle \-b db.domain.tld sql-relay" reads the
database description stored in $TNS_ADMIN/tnsnames.ora:
.PP
.DS
* Other projects seem to use endian.h and variants, but these are
* in non standard locations, and may mess up cross compiling.
*
- * Here at least the endianess can be set explicitly with
+ * Here at least the endianness can be set explicitly with
* -DLITTLE_ENDIAN or -DBIG_ENDIAN.
*/
#if !defined(FR_LITTLE_ENDIAN) && !defined(FR_BIG_ENDIAN)
* Convert AF. If unknown, discard packet.
*/
if (!fr_sockaddr2ipaddr(&src, sizeof_src, src_ipaddr, src_port)) {
- FR_DEBUG_STRERROR_PRINTF("Unkown address family");
+ FR_DEBUG_STRERROR_PRINTF("Unknown address family");
rad_recv_discard(sockfd);
return 1;
*/
start = now->tv_sec - ((home->zombie_period + 3) / 4);
if (home->last_packet_recv >= start) {
- DEBUG("Recieved reply from home server %d seconds ago. Might not be zombie.",
+ DEBUG("Received reply from home server %d seconds ago. Might not be zombie.",
(int) (now->tv_sec - home->last_packet_recv));
return;
}
talloc_free(versions);
- DEBUG3("Endianess:");
+ DEBUG3("Endianness:");
#if defined(FR_LITTLE_ENDIAN)
DEBUG3(" little");
#elif defined(FR_BIG_ENDIAN)
return RLM_MODULE_FAIL;
case CACHE_OK:
- RDEBUG("Commited entry, TTL %d seconds", ttl);
+ RDEBUG("Committed entry, TTL %d seconds", ttl);
cache_free(inst, &c);
return RLM_MODULE_UPDATED;
projects / freeradius.git / commitdiff