Mercurial > notdcc
view homedir/ids @ 3:b689077d4918
Ignore old patches
author | Peter Gervai <grin@grin.hu> |
---|---|
date | Tue, 10 Mar 2009 14:31:24 +0100 |
parents | c7f6b056b673 |
children |
line wrap: on
line source
# Sample DCC server IDs and passwords as well as client IDs and passwords # See dccd(8) # Each ID must have at least one password. A second password can be present # to ease changing passwords. Either password is always acceptable. # One password can be the secret currently used and the other can be the # previous or future secret. # Every DCC server must have a unique server-ID. A server ID is a number # between 100 and 32767. A DCC server is a system running dccd. # Clients use client-IDs, which are the anonymous client-ID 1 and numbers # starting at 32768. DCC clients are systems that process mail and # Server passwords or the passwords associated with server-IDs are used in # two areas. First, the cdcc program uses them to authenticate its commands # to a server. Passwords and IDs used for this purpose should be guarded # carefully. Second, passwords are used to are used to authenticate floods # of checksums among DCC servers. # # Client-IDs are used by servers to identify and authenticate clients. # Servers can be configured to give better service to clients not # using the anonymous client-ID or to give reduced or no service # to anonymous clients. # It is handy to reserve a server-ID for inter-server flooding, and call it # a "passwd-ID." That way the people running the DCC server on # dcc1.domain.com do not need to know the password that the people running # the dcc2.example.com server use to control that server, and vice versa. # If they knew each other's secret passwords, then each could control each # other's server with `cdcc`. ###################################################### # Every DCC client organization should have a unique client-ID. # Client programs and computers within an organization can share client-IDs. # sample client-ID # This password is generated by the installation script, and so may not be # as secret as necessary. This password must be the same as the password # in the map file. `make install` replaces "secret1" with a suitable # password here and in the map file. 32768 secret1 # server-IDs 1000 # auto local greylist server-ID # The preceding line is used by /var/dcc/libexec/start-grey # and /var/dcc/libexec/stop-dccd to find the following line containing # the password generated by the installation script: 32702 secret2 # Rhyolite Software DCC 1.3.103-1.26 $Revision$