Adam Pribyl <[email protected]> skribis: > I would suggest improving the > http://www.gnu.org/software/guix/manual/guix.html#Using-the-Configuration-System > example and incorporating most of the options in the configuration > example as e.g. starting lsh-service without [#:initialize? #f] for > the first time makes no sense. Also it could be present in the config > template in the distribution itself. > > This would help most of us not very familiar with all the details to > do a fluent installation.
I was uneasy having #:initialize? default to #t. That would work, but I’d rather have people create key handle that explicitly by themselves, because it’s pretty sensitive, #:initialize? runs ‘lsh-make-seed’ with --sloppy, which is not so great, and they might want to reuse existing keys, etc. To begin with, I’ve clarified the documention, with links to the lsh manual (patch below.) Thanks for the suggestion, Ludo’.
commit aba747bda84d99fc7dc7b5ff40562217d6d304dc (HEAD, refs/heads/master) Author: Ludovic Courtès <[email protected]> Date: Mon Nov 24 21:15:40 2014 +0100 doc: Add xrefs to the lsh manual. Suggested by Adam Pribyl <[email protected]>. * gnu/services/ssh.scm (lsh-service): Update docstring with xrefs to the lsh manual. Fix typos. * doc/guix.texi (Networking Services): Synchronize. Modified doc/guix.texi diff --git a/doc/guix.texi b/doc/guix.texi index a2f881f..3d49f7d 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -4033,12 +4033,17 @@ When @var{initialize?} is true, automatically create the seed and host key upon service activation if they do not exist yet. This may take long and require interaction. +When @var{initialize?} is false, it is up to the user to initialize the +randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to create +a key pair with the private key stored in file @var{host-key} (@pxref{lshd +basics,,, lsh, LSH Manual}). + When @var{interfaces} is empty, lshd listens for connections on all the network interfaces; otherwise, @var{interfaces} must be a list of host names or addresses. -@var{allow-empty-passwords?} specifies whether to accepts log-ins with empty -passwords, and @var{root-login?} specifies whether to accepts log-ins as +@var{allow-empty-passwords?} specifies whether to accept log-ins with empty +passwords, and @var{root-login?} specifies whether to accept log-ins as root. The other options should be self-descriptive. Modified gnu/services/ssh.scm diff --git a/gnu/services/ssh.scm b/gnu/services/ssh.scm index 5fc98e9..2b52c77 100644 --- a/gnu/services/ssh.scm +++ b/gnu/services/ssh.scm @@ -91,12 +91,17 @@ When @var{initialize?} is true, automatically create the seed and host key upon service activation if they do not exist yet. This may take long and require interaction. +When @var{initialize?} is false, it is up to the user to initialize the +randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to create +a key pair with the private key stored in file @var{host-key} (@pxref{lshd +basics,,, lsh, LSH Manual}). + When @var{interfaces} is empty, lshd listens for connections on all the network interfaces; otherwise, @var{interfaces} must be a list of host names or addresses. -@var{allow-empty-passwords?} specifies whether to accepts log-ins with empty -passwords, and @var{root-login?} specifies whether to accepts log-ins as +@var{allow-empty-passwords?} specifies whether to accept log-ins with empty +passwords, and @var{root-login?} specifies whether to accept log-ins as root. The other options should be self-descriptive."
