Mercurial > notdcc
comparison homedir/ids @ 0:c7f6b056b673
First import of vendor version
| author | Peter Gervai <grin@grin.hu> |
|---|---|
| date | Tue, 10 Mar 2009 13:49:58 +0100 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:c7f6b056b673 |
|---|---|
| 1 # Sample DCC server IDs and passwords as well as client IDs and passwords | |
| 2 # See dccd(8) | |
| 3 | |
| 4 # Each ID must have at least one password. A second password can be present | |
| 5 # to ease changing passwords. Either password is always acceptable. | |
| 6 # One password can be the secret currently used and the other can be the | |
| 7 # previous or future secret. | |
| 8 | |
| 9 # Every DCC server must have a unique server-ID. A server ID is a number | |
| 10 # between 100 and 32767. A DCC server is a system running dccd. | |
| 11 # Clients use client-IDs, which are the anonymous client-ID 1 and numbers | |
| 12 # starting at 32768. DCC clients are systems that process mail and | |
| 13 | |
| 14 # Server passwords or the passwords associated with server-IDs are used in | |
| 15 # two areas. First, the cdcc program uses them to authenticate its commands | |
| 16 # to a server. Passwords and IDs used for this purpose should be guarded | |
| 17 # carefully. Second, passwords are used to are used to authenticate floods | |
| 18 # of checksums among DCC servers. | |
| 19 # | |
| 20 # Client-IDs are used by servers to identify and authenticate clients. | |
| 21 # Servers can be configured to give better service to clients not | |
| 22 # using the anonymous client-ID or to give reduced or no service | |
| 23 # to anonymous clients. | |
| 24 | |
| 25 # It is handy to reserve a server-ID for inter-server flooding, and call it | |
| 26 # a "passwd-ID." That way the people running the DCC server on | |
| 27 # dcc1.domain.com do not need to know the password that the people running | |
| 28 # the dcc2.example.com server use to control that server, and vice versa. | |
| 29 # If they knew each other's secret passwords, then each could control each | |
| 30 # other's server with `cdcc`. | |
| 31 | |
| 32 ###################################################### | |
| 33 # Every DCC client organization should have a unique client-ID. | |
| 34 # Client programs and computers within an organization can share client-IDs. | |
| 35 | |
| 36 | |
| 37 # sample client-ID | |
| 38 # This password is generated by the installation script, and so may not be | |
| 39 # as secret as necessary. This password must be the same as the password | |
| 40 # in the map file. `make install` replaces "secret1" with a suitable | |
| 41 # password here and in the map file. | |
| 42 32768 secret1 | |
| 43 | |
| 44 # server-IDs | |
| 45 1000 | |
| 46 | |
| 47 # auto local greylist server-ID | |
| 48 # The preceding line is used by /var/dcc/libexec/start-grey | |
| 49 # and /var/dcc/libexec/stop-dccd to find the following line containing | |
| 50 # the password generated by the installation script: | |
| 51 32702 secret2 | |
| 52 | |
| 53 | |
| 54 # Rhyolite Software DCC 1.3.103-1.26 $Revision$ |