CC'ing the bug report, for historical reference..:)
Quoting Stefan Pfetzing ([EMAIL PROTECTED]): > Hi Christian, > > as said on #debian-devel, here is the lsh-utils template and the link > to the bug ;) OK, let's try, with some comments where I can Template: lsh-server/random_seed Type: note _Description: New versions of lsh require random seed file In new versions of lsh-server (1.3.6 and above), a random seed file is required for lshd or lsh_proxy to run. This file is generated by running "lsh-make-seed --server". lsh-make-seed requires you to enter random keystrokes for its random number generator. You will need to run this command in order for the lsh server to work. This seed only needs to be created once. . For security reasons, lsh-make-seed really needs to be run from the console of the system you are running it on. If you run lsh-make-seed using a remote shell, the timing information lsh-make-seed uses for its random seed creation is likely to be screwed. If need be, you can generate the random seed on a different system than that which it will eventually be on, by installing the lsh-utils package and running "lsh-make-seed -o my-other-server-seed-file". You may then transfer the seed to the destination system as using a secure connection with lsh or ssh (store it as /var/spool/lsh/yarrow-seed-file). . If the file /var/spool/lsh/yarrow-random-seed already exists on your system, (for example if you have already successfully configured lsh-server 1.3.6 on your system), you can safely ignore this note. That one is fine but way too long, IMHO. I think it probably more pertains to a README or README.Debian, or NEWS.Debian file. Several people call this "debconf abuse". This actually depends on the priority used for the question. If you insist on keeping it, then try making it fit in a 80x25 screen. And, even after doing that, try translating it to German AND having it still fit on one screen...which will be fun, I guess...:) You can test a PO file for debconf with the podebconf-display-po utility. Template: lsh-server/ssh1_migration Type: note _Description: Migrating from SSH1/OpenSSH to lsh As SSH1 and OpenSSH (hereafter referred to as simply "SSH1") and lshd all use the same default port (22), you will need to choose one of the following strategies to have the SSH1 and lshd daemons working together on the same machine/network interface. . The default option is to have lshd running on port 2222. This can be changed to any unused port you want. With this option you will need to pass the option "-p <port number>" to lshc to specify what port the server is running on (eg. -p 2222). . Having to give lshc the `-p 2222' option can get very annoying, so you may want to run lshd on the default ssh port of 22. This means that you will *not* be able to run any other ssh daemon as normal on port 22. . Please note that if you have any of the ssh2, ssh-nonfree or ssh-socks packages installed and you want run lshd on port 22, you need to manually disable the ssh daemon in that package from starting (or make it start on a different port). To do this, you will need to edit /etc/init.d/<packagenamewhere <packagenameis ssh2, ssh-nonfree or ssh-socks (depending on which one you've got installed), and put "exit 0" as the second line in the file (after the "#!/bin/sh") Same remark here. For the same reasons, I don't think it's worth entering a complex correction process. I suggest moving this elsewhere, outside debconf. Template: lsh-server/lshd_port Type: string Default: 2222 _Description: lsh server port: The default port for lshd is 2222. If you would like lshd to run on a different port, please specify the alternative port here. If you specify 22, you will need to manually disable any other ssh servers you have running on port 22, other than OpenSSH (from the `ssh' package). That one is fine. Template: lsh-server/sftp Type: boolean Default: false _Description: Enable the sftp subsystem? If you want to use sftp with lsh, you will need this subsytem. Please bear in mind, that its still experimental. Therefore the default is disabled. I can enable this for you or you can manually change /etc/default/lsh-server to enable this later on. . Do you want to use the EXPERIMENTAL sftp suppport? I suggest rewriting as (remove first person use and double questioning): Template: lsh-server/sftp Type: boolean Default: false _Description: Enable the sftp subsystem? If you want to use sftp with lsh, you will need this subsytem. Please bear in mind, that its still experimental. Therefore the default is disabled but can be enabled now or later by manually changing /etc/default/lsh-server. . Please choose whether you want to use the EXPERIMENTAL sftp support now. Template: lsh-server/purge_hostkey Type: boolean Default: false _Description: Remove host key on purge? When this package is installed, a host key is generated to authenticate your host. This host key is not purged with the rest of the package by default, if you want to purge it when the package is removed then you must specify that here. . Do you want lsh's host key to be automatically removed when this package is purged? I suggest rewriting as (remove first person use and double questioning): Template: lsh-server/purge_hostkey Type: boolean Default: false _Description: Remove host key on purge? When this package is installed, a host key is generated to authenticate your host. This host key is not purged with the rest of the package by default. . Please choose whether you want to purge the host key when the package is removed. Btw, I personally think the last questions are the most questionable. *grin* ;) You were right..:-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
