From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <jmd@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add Kerberos client service.
Date: Wed, 23 Nov 2016 23:01:20 +0100 [thread overview]
Message-ID: <87shqh500f.fsf@gnu.org> (raw)
In-Reply-To: <1479837137-12251-1-git-send-email-jmd@gnu.org> (John Darrington's message of "Tue, 22 Nov 2016 18:52:17 +0100")
Hi!
John Darrington <jmd@gnu.org> skribis:
> * doc/guix.texi: New subsubheading: Krb5 Service
> * gnu/services/kerberos.scm: New variable: krb5-service-type.
Please see ‘git log’ on how to introduce new sections and variables.
> +@subsubheading Krb5 Service
> +
> +The krb5 service provides the configuration for Kerberos clients, using
> +the MIT implementation of the Kerberos protocol version@tie{}5.
Maybe add: “ (the @code{mit-krb5} package).”
Also it would be good to add one or two sentences of context, like:
Programs using the client library of @code{mit-krb5} expect such
configuration files in @file{/etc/something} and read them to set up
their Kerberos frobbing thingie. System administrators typically
define the appropriate configuration based on the network's Kerberos
foobar.
Well, something like that. :-)
> +@defvr {Scheme Variable} krb5-service-type
> +A service type for Kerberos 5 clients.
s/Kerberos 5/@code{mit-krb5}/
> +@lisp
> +(service krb5-service-type (krb5-configuration
> + (default-realm "EXAMPLE.COM")
Please move the ‘krb5-configuration’ to the next line where it will be
aligned below ‘krb5-service-type’. This will ensure correct PDF/PS/DVI
output as well as below-80 Info lines.
> +@item @code{allow-weak-crypto?} (default: @code{#f})
> +If this flag is #t then services which only offer encryption algorithms
@code{#t}
> +(define-syntax define-configuration
> + (lambda (stx)
> + (define (id ctx part . parts)
Nack! We already have two copies of that one, we won’t add a third
one. :-)
Fortunately, Julien submitted a patch to factorize it, so hopefully you
can use the factorize ‘define-configuration’ in a day or two.
> +;; For a more detailed explanation of these fields see man 5 krb5.conf
> +(define-configuration krb5-realm
> + (name
> + (string #f)
> + "The name of the realm.")
Really cool.
> +;; LocalWords: Guix
Maybe we can avoid that, but no big deal.
So OK with changes along these lines when Julien’s factorization has
landed.
Thank you!
Ludo’.
next prev parent reply other threads:[~2016-11-23 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 19:58 [PATCH] gnu: Add kerberos service John Darrington
2016-11-18 15:23 ` John Darrington
2016-11-18 22:51 ` Ludovic Courtès
2016-11-19 6:57 ` John Darrington
2016-11-21 8:59 ` Ludovic Courtès
2016-11-22 17:52 ` [PATCH] gnu: Add Kerberos client service John Darrington
2016-11-23 22:01 ` Ludovic Courtès [this message]
2016-11-29 18:39 ` John Darrington
2016-11-29 18:39 ` John Darrington
2016-11-30 13:09 ` Ludovic Courtès
2016-11-30 13:44 ` John Darrington
2016-11-30 13:52 ` Andy Wingo
2016-12-03 12:27 ` John Darrington
2016-12-03 15:13 ` Ludovic Courtès
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=87shqh500f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
/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).