X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=man%2Fxml-source%2Famanda-auth.7.xml;fp=man%2Fxml-source%2Famanda-auth.7.xml;h=1a97ad2b13ee13d62b56f8d3eb16ef99509e0266;hb=d5853102f67d85d8e169f9dbe973ad573306c215;hp=0fb1715b7ce3ed5da3a4a256785d1dd14679e0e8;hpb=b93e5b5a13be7e970bc333acbe885f5b518300e1;p=debian%2Famanda diff --git a/man/xml-source/amanda-auth.7.xml b/man/xml-source/amanda-auth.7.xml index 0fb1715..1a97ad2 100644 --- a/man/xml-source/amanda-auth.7.xml +++ b/man/xml-source/amanda-auth.7.xml @@ -3,7 +3,7 @@ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - + %global_entities; ]> @@ -18,7 +18,7 @@ amanda-auth - Communication/Authentication methods between &A; server and client + Communication/Authentication methods between Amanda server and client &author.jlm; @@ -29,15 +29,15 @@ DESCRIPTION - &A; offers 7 methods of communication between Amanda server (sometimes also called the tape server) and clients, each with its own authentication method. The desired communication method is specified by the auth parameter in the amanda.conf file (&amconf;) commonly as a dumptype. Valid values to the auth parameter are bsd, bsdudp, bsdtcp, krb4, krb5, local, rsh, and ssh. Please note that krb4 will be removed in the next release. The authentication and communication method is used during the backup process &amdump; (amdump(8)) as well as the recovery process &amrecover; (amrecover(8)). For detailed information, please see http://wiki.zmanda.com/index.php/Server/Client_authentication. +Amanda offers 7 methods of communication between Amanda server (sometimes also called the tape server) and clients, each with its own authentication method. The desired communication method is specified by the auth parameter in the amanda.conf file (&amconf;) commonly as a dumptype. Valid values to the auth parameter are bsd, bsdudp, bsdtcp, krb4, krb5, local, rsh, and ssh. Please note that krb4 will be removed in the next release. The authentication and communication method is used during the backup process &amdump; (amdump(8)) as well as the recovery process &amrecover; (amrecover(8)). COMPILATION AND GENERAL INFORMATION The communication method and thus type of authentication that will be used by the Amanda server is specified by the auth parameter in the dumptype for each disklist entry (DLE). The auth parameter thus may be easily and globally specified in the "global" dumptype. If auth is not specified, the bsd communication method is used. See &amconf; for more information on Amanda configuration and dumptypes, and &disklist; for more information on disklists. -On the client side, the Amanda daemon &amandad; validates the connection depending on the value of the auth argument passed to it (see &A;(8)). Also, when it comes to recovery, the auth parameter can be specified in the &amclientconf; file to specify the communication method to be used by the client to the server. +On the client side, the Amanda daemon &amandad; validates the connection depending on the value of the auth argument passed to it (see Amanda(8)). Also, when it comes to recovery, the auth parameter can be specified in the &amclientconf; file to specify the communication method to be used by the client to the server. - When &A; is being built from source code, desired communication and thus authentication methods (shown as "Authentication") must be specified as configure options at compilation time. + When Amanda is being built from source code, desired communication and thus authentication methods (shown as "Authentication") must be specified as configure options at compilation time. Authentication Configure option(s) bsd --with-bsd-security --with-amandahosts (pre-2.6) @@ -82,12 +82,16 @@ Authentication Configure option(s) BSD, BSDUDP, AND BSDTCP COMMUNICATION AND AUTHENTICATION -For more detail, see http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication. +For additional information including example configurations, see http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication. The bsd, bsdudp, and bsdtcp communication methods use either UDP, TCP, or both protocols operating as a network service to authenticate and exchange data between server and clients. - In addition to compilation and general configuration (see COMPILATION AND GENERAL INFORMATION above), the authentication method that the client is configured to receive is specified by the auth parameter in the network service configuration for &A;. The authentication method used by an Amanda client to reach the server during recovery is the authentication method specified by the auth parameter in the client's Amanda network service configuration or in its amanda-client.conf file (see amanda-client.conf(5)). - + In addition to compilation and general configuration (see COMPILATION AND GENERAL INFORMATION above), the authentication method that the client is configured to receive is specified by the auth parameter in the network service configuration for Amanda. The authentication method used by an Amanda client to reach the server during recovery is the authentication method specified by the auth parameter in the client's Amanda network service configuration or in its amanda-client.conf file (see amanda-client.conf(5)). + + By default, Amanda use the "amanda" service name and associated port set in /etc/services. It can be changed by setting the dumptype client_port option to a different port number or a different service name. + All examples are for the service name "amanda" that uses the default port 10080. + + .amandahosts file Servers and clients using the bsd, bsdudp, and bsdtcp authentication methods refer to the .amandahosts file to control access. Amanda should be compiled for this access control if one of these methods will be used and is the default compilation option for Amanda 2.6 (use --with-amandahosts when compiling pre-2.6 versions of Amanda). @@ -111,6 +115,8 @@ configuration file. amindexd, and amidxtaped. The last two services are required on a server for clients to connect to it using amrecover. +If service is omitted, it defaults to noop selfcheck sendsize sendbackup (which is equivalent to amdump). + Example of the .amandahosts file on an Amanda client @@ -521,15 +527,13 @@ If your server &amandad; path and client &amandad; path are different, you shoul As Amanda will not answer this question itself, you must manually make every connection (server to client and client to server) that you expect Amanda to make. Note that you must use the same username that Amanda will use (that is, ssh client and ssh client.domain.com are distinct). -SEE ALSO - -&amconf;, -&amclientconf;, -&disklist;, -&amdump;(8), -&amrecover;(8) - - - + + + + + + + +