unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Adam Pribyl <pribyl@lowlevel.cz>
Cc: guix-devel@gnu.org
Subject: Re: Advice needed on gcc error
Date: Mon, 24 Nov 2014 21:17:00 +0100	[thread overview]
Message-ID: <87zjbg9ww3.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1411232147370.26870@sandbox.cz> (Adam Pribyl's message of "Sun, 23 Nov 2014 21:55:39 +0100 (CET)")

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

Adam Pribyl <pribyl@lowlevel.cz> 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’.


[-- Attachment #2: Type: text/x-patch, Size: 2761 bytes --]

commit aba747bda84d99fc7dc7b5ff40562217d6d304dc (HEAD, refs/heads/master)
Author: Ludovic Courtès <ludo@gnu.org>
Date:   Mon Nov 24 21:15:40 2014 +0100

    doc: Add xrefs to the lsh manual.
    
    Suggested by Adam Pribyl <pribyl@lowlevel.cz>.
    
    * 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."


      reply	other threads:[~2014-11-24 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 21:32 Advice needed on gcc error Saul Hazledine
2014-11-21  9:21 ` Ludovic Courtès
2014-11-22 17:52   ` Saul Hazledine
2014-11-22 21:00     ` Ludovic Courtès
2014-11-22 21:10       ` Adam Pribyl
2014-11-22 22:09         ` Ludovic Courtès
2014-11-23 10:17           ` Adam Pribyl
2014-11-23 20:22             ` Ludovic Courtès
2014-11-23 20:55               ` Adam Pribyl
2014-11-24 20:17                 ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zjbg9ww3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pribyl@lowlevel.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).