From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Domagoj Stolfa <ds815@gmx.com>
Cc: 48803-done@debbugs.gnu.org, guix-patches@gnu.org
Subject: bug#48803: [PATCH] gnu: Add strongswan service.
Date: Fri, 25 Jun 2021 01:17:43 +0200 [thread overview]
Message-ID: <87r1gqsvhk.fsf@nckx> (raw)
In-Reply-To: <YMYfhbU2sYobdunV@parenthesis>
[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]
Domagoj!
This is finally on master with the following changes:
Domagoj Stolfa 写道:
> * gnu/services/vpn.scm (strongswan-configuration): New record
> type.
> (charon-plugins, strongswan-configuration-file)
> (strongswan-shepherd-service, strongswan-service-type): New
> variables.
I don't know where this extra spacing came from but removed it.
> +@subheading StrongSwan
I'm sure some style guides disapprove, but I changed all usage of
‘StrongSwan’ to upstream's ‘strongSwan’.
> +Currently, the StrongSwan service only provides legacy-style
> configuration with
> +ipsec.conf and ipsec.secrets files.
We have cool @file{} mark up so I used it.
> +@defvr {Scheme Variable} strongswan-service-type
> +A service type for StrongSwan configuration.
Added a very brief ‘IPsec VPN’ context.
> +@lisp
> +(service strongswan-service-type
> + (strongswan-configuration
> + (ipsec-conf "/etc/ipsec.conf")
> + (ipsec-secrets "/etc/ipsec.secrets")))
Fixed the indentation.
> +@item @code{ipsec-conf} (default: @code{#f})
> +The path to an ipsec.conf file. If set to @code{#f},
> @code{ipsec-secrets} will
> +also be ignored.
Reworded this to match the exception I added below. Added moar
@file{}.
> @c %end of automatic openvpn-server documentation
This indicates that the author of the previous OpenVPN section
automated the docs somehow. I moved it back.
> @subsubheading Wireguard
> diff --git a/gnu/services/vpn.scm b/gnu/services/vpn.scm
> index 2bcbf76727..691cc3c05a 100644
> --- a/gnu/services/vpn.scm
> +++ b/gnu/services/vpn.scm
> @@ -26,6 +26,7 @@
> #:use-module (gnu services shepherd)
> #:use-module (gnu system shadow)
> #:use-module (gnu packages admin)
> + #:use-module (gnu packages networking)
Oops, noticed this only now… I don't think it's needed anymore.
Can you confirm?
‘guix system’ & friends will now throw an inelegant error if
ipsec-conf & ipsec-secrets are incongruent. I couldn't get
meaningful location data out of CONFIG. This does the job:
+ (throw 'error
+ (G_ "strongSwan ipsec-conf and ipsec-secrets must
\
+both be (un)set")))))
> +(define strongswan-service-type
> + (service-type
> + (name 'strongswan)
> + (extensions
> + (list (service-extension shepherd-root-service-type
> + strongswan-shepherd-service)))))
I added a default-value so people can simply write
(service strongswan-service-type)
and a short description.
Thank you very much!
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-06-24 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 22:11 [bug#48803] [PATCH] strongswan: provide a service definition and configuration interface Domagoj Stolfa
2021-06-13 12:41 ` Tobias Geerinckx-Rice via Guix-patches via
2021-06-13 13:04 ` Domagoj Stolfa
2021-06-13 12:45 ` Tobias Geerinckx-Rice via Guix-patches via
2021-06-13 15:08 ` [bug#48803] [PATCH] gnu: Add strongswan service Domagoj Stolfa
2021-06-24 23:17 ` Tobias Geerinckx-Rice via Guix-patches via [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=87r1gqsvhk.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=48803-done@debbugs.gnu.org \
--cc=ds815@gmx.com \
--cc=me@tobias.gr \
/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).