I am reviewing the patches used by Debian to build amanda 3.3.9 and updating them for amanda 3.4.1. I think some of them are not specific to Debian. My plan is to present the patches here so they can be reviewed for adoption or not.
The first batch are about small English mistakes in documentation that lintian complains. In attach there is 3 patches. Kind regards Jose M Calhariz -- -- Erro de usuário: Troque o usuário e pressione qualquer tecla para continuar.
Description: Fix miss spelling that are pointed by lintian. Author: Jose M Calhariz <[email protected]> Index: amanda-3.4.1/man/amanda-auth.7 =================================================================== --- amanda-3.4.1.orig/man/amanda-auth.7 2017-01-08 17:17:49.620890682 +0000 +++ amanda-3.4.1/man/amanda-auth.7 2017-01-08 17:21:24.089181439 +0000 @@ -673,7 +673,7 @@ Besides user keys, SSH uses host keys to 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)\&. .SS "Authenticated Peer Hostnames with SSH Authentication" .PP -When accepting an incoming conneciton, the SSH daemon gives Amanda information about the remote system in the $SSH_CONNECTION environment variable\&. Amanda parses this information to determine the remote address, and then performs a similar check to that done by the BSD authentications: the forward and reverse DNS entries for the remote host must match\&. As such, while SSH authentication can cryptographically ensure that the remote system is recognized (since it had a recognized secret key), its assurances about the remote host\*(Aqs identity are weaker and depend on the integrity of the DNS\&. +When accepting an incoming connection, the SSH daemon gives Amanda information about the remote system in the $SSH_CONNECTION environment variable\&. Amanda parses this information to determine the remote address, and then performs a similar check to that done by the BSD authentications: the forward and reverse DNS entries for the remote host must match\&. As such, while SSH authentication can cryptographically ensure that the remote system is recognized (since it had a recognized secret key), its assurances about the remote host\*(Aqs identity are weaker and depend on the integrity of the DNS\&. .SH "SSL COMMUNICATION AND AUTHENTICATION" .PP See Index: amanda-3.4.1/man/amanda-changers.7 =================================================================== --- amanda-3.4.1.orig/man/amanda-changers.7 2017-01-08 17:17:49.620890682 +0000 +++ amanda-3.4.1/man/amanda-changers.7 2017-01-08 17:17:49.620890682 +0000 @@ -132,7 +132,7 @@ define changer aggregate { tpchanger "aggregate" .fi .PP -This changer driver allow to use two or more changers or standalone drive in sequence\&. +This changer driver allow one to use two or more changers or standalone drive in sequence\&. .SS "Properties" .PP LOCK\-TIMEOUT Index: amanda-3.4.1/man/amanda-devices.7 =================================================================== --- amanda-3.4.1.orig/man/amanda-devices.7 2017-01-08 17:17:49.620890682 +0000 +++ amanda-3.4.1/man/amanda-devices.7 2017-01-08 17:17:49.620890682 +0000 @@ -778,7 +778,7 @@ INDIRECT .RS 4 (read\-write) The default in "yes"\&. You can set it to "no" if the ndmp server -allow to set a window length to 0\&. +allow one to set a window length to 0\&. .RE .PP NDMP_AUTH
fix-lintian-miss-spelling-amanda.conf.5.xml
Description: XML document
fix-lintian-miss-spelling-amanda-changers.7.xml
Description: XML document
signature.asc
Description: Digital signature
