2015-05-07 16:49:01 +01:00
|
|
|
{ config, lib, pkgs, ... }:
|
|
|
|
|
|
|
|
with lib;
|
|
|
|
|
|
|
|
let
|
|
|
|
cfg = config.services.taskserver;
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
|
|
|
|
taskd = "${pkgs.taskserver}/bin/taskd";
|
|
|
|
|
|
|
|
mkVal = val:
|
|
|
|
if val == true then "true"
|
|
|
|
else if val == false then "false"
|
|
|
|
else if isList val then concatStringsSep ", " val
|
|
|
|
else toString val;
|
|
|
|
|
|
|
|
mkConfLine = key: val: let
|
|
|
|
result = "${key} = ${mkVal val}";
|
|
|
|
in optionalString (val != null && val != []) result;
|
|
|
|
|
|
|
|
needToCreateCA = all isNull (with cfg; [
|
|
|
|
server.key server.cert server.crl caCert
|
|
|
|
]);
|
|
|
|
|
|
|
|
configFile = pkgs.writeText "taskdrc" ''
|
|
|
|
# systemd related
|
|
|
|
daemon = false
|
|
|
|
log = -
|
|
|
|
|
|
|
|
# logging
|
|
|
|
${mkConfLine "debug" cfg.debug}
|
|
|
|
${mkConfLine "ip.log" cfg.ipLog}
|
|
|
|
|
|
|
|
# general
|
|
|
|
${mkConfLine "ciphers" cfg.ciphers}
|
|
|
|
${mkConfLine "confirmation" cfg.confirmation}
|
|
|
|
${mkConfLine "extensions" cfg.extensions}
|
|
|
|
${mkConfLine "queue.size" cfg.queueSize}
|
|
|
|
${mkConfLine "request.limit" cfg.requestLimit}
|
|
|
|
|
|
|
|
# client
|
|
|
|
${mkConfLine "client.cert" cfg.client.cert}
|
|
|
|
${mkConfLine "client.allow" cfg.client.allow}
|
|
|
|
${mkConfLine "client.deny" cfg.client.deny}
|
|
|
|
|
|
|
|
# server
|
|
|
|
server = ${cfg.server.host}:${toString cfg.server.port}
|
|
|
|
${mkConfLine "server.crl" cfg.server.crl}
|
|
|
|
|
|
|
|
# certificates
|
2016-04-05 15:09:12 +01:00
|
|
|
${mkConfLine "trust" cfg.server.trust}
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
${if needToCreateCA then ''
|
2016-04-04 21:55:39 +01:00
|
|
|
ca.cert = ${cfg.dataDir}/keys/ca.cert
|
|
|
|
server.cert = ${cfg.dataDir}/keys/server.cert
|
|
|
|
server.key = ${cfg.dataDir}/keys/server.key
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
'' else ''
|
2016-04-04 21:55:39 +01:00
|
|
|
ca.cert = ${cfg.caCert}
|
|
|
|
server.cert = ${cfg.server.cert}
|
|
|
|
server.key = ${cfg.server.key}
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
''}
|
|
|
|
'';
|
|
|
|
|
2015-05-07 16:49:01 +01:00
|
|
|
in {
|
|
|
|
|
|
|
|
options = {
|
|
|
|
services.taskserver = {
|
|
|
|
|
2015-09-27 18:30:02 +01:00
|
|
|
enable = mkEnableOption "the Taskwarrior server";
|
2015-05-07 16:49:01 +01:00
|
|
|
|
|
|
|
user = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.str;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = "taskd";
|
2015-09-27 18:30:02 +01:00
|
|
|
description = "User for Taskserver.";
|
2015-05-07 16:49:01 +01:00
|
|
|
};
|
|
|
|
|
2015-09-27 14:35:42 +01:00
|
|
|
group = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.str;
|
2015-09-27 14:35:42 +01:00
|
|
|
default = "taskd";
|
2015-09-27 18:30:02 +01:00
|
|
|
description = "Group for Taskserver.";
|
2015-09-27 14:35:42 +01:00
|
|
|
};
|
|
|
|
|
2015-05-07 16:49:01 +01:00
|
|
|
dataDir = mkOption {
|
|
|
|
type = types.path;
|
2015-09-27 18:30:02 +01:00
|
|
|
default = "/var/lib/taskserver";
|
|
|
|
description = "Data directory for Taskserver.";
|
2015-05-07 16:49:01 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
caCert = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.nullOr types.path;
|
|
|
|
default = null;
|
|
|
|
description = "Fully qualified path to the CA certificate.";
|
2015-05-07 16:49:01 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
ciphers = mkOption {
|
2016-04-05 15:12:55 +01:00
|
|
|
type = types.nullOr types.str;
|
2015-09-27 18:30:02 +01:00
|
|
|
default = null;
|
|
|
|
example = "NORMAL";
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
List of GnuTLS ciphers to use. See the GnuTLS documentation for full
|
|
|
|
details.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
confirmation = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.bool;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = true;
|
|
|
|
description = ''
|
|
|
|
Determines whether certain commands are confirmed.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
debug = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.bool;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = false;
|
|
|
|
description = ''
|
|
|
|
Logs debugging information.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
extensions = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.nullOr types.path;
|
|
|
|
default = null;
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
Fully qualified path of the Taskserver extension scripts.
|
|
|
|
Currently there are none.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
ipLog = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.bool;
|
|
|
|
default = false;
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
|
|
|
Logs the IP addresses of incoming requests.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
queueSize = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.int;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = 10;
|
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
Size of the connection backlog, see <citerefentry>
|
|
|
|
<refentrytitle>listen</refentrytitle>
|
|
|
|
<manvolnum>2</manvolnum>
|
|
|
|
</citerefentry>.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
requestLimit = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.int;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = 1048576;
|
|
|
|
description = ''
|
|
|
|
Size limit of incoming requests, in bytes.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
client = {
|
|
|
|
|
|
|
|
allow = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.listOf types.str;
|
|
|
|
default = [];
|
|
|
|
example = [ "[Tt]ask [2-9]+" ];
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
A list of regular expressions that are matched against the reported
|
|
|
|
client id (such as <literal>task 2.3.0</literal>).
|
|
|
|
|
|
|
|
The values <literal>all</literal> or <literal>none</literal> have
|
|
|
|
special meaning. Overidden by any entry in the option
|
|
|
|
<option>services.taskserver.client.deny</option>.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
cert = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.nullOr types.path;
|
|
|
|
default = null;
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
Fully qualified path of the client cert. This is used by the
|
|
|
|
<command>client</command> command.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
deny = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.listOf types.str;
|
|
|
|
default = [];
|
|
|
|
example = [ "[Tt]ask [2-9]+" ];
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
A list of regular expressions that are matched against the reported
|
|
|
|
client id (such as <literal>task 2.3.0</literal>).
|
|
|
|
|
|
|
|
The values <literal>all</literal> or <literal>none</literal> have
|
|
|
|
special meaning. Any entry here overrides these in
|
|
|
|
<option>services.taskserver.client.allow</option>.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
server = {
|
|
|
|
host = mkOption {
|
2016-04-05 15:12:55 +01:00
|
|
|
type = types.str;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = "localhost";
|
|
|
|
description = ''
|
2016-04-05 15:16:14 +01:00
|
|
|
The address (IPv4, IPv6 or DNS) to listen on.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
port = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.int;
|
2015-05-07 16:49:01 +01:00
|
|
|
default = 53589;
|
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
Port number of the Taskserver.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
2016-04-05 15:16:14 +01:00
|
|
|
fqdn = mkOption {
|
|
|
|
type = types.str;
|
|
|
|
default = "localhost";
|
|
|
|
description = ''
|
|
|
|
The fully qualified domain name of this server.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
2015-05-07 16:49:01 +01:00
|
|
|
cert = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.nullOr types.path;
|
|
|
|
default = null;
|
2015-05-07 16:49:01 +01:00
|
|
|
description = "Fully qualified path to the server certificate";
|
|
|
|
};
|
|
|
|
|
|
|
|
crl = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.nullOr types.path;
|
|
|
|
default = null;
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
2015-09-27 18:30:02 +01:00
|
|
|
Fully qualified path to the server certificate revocation list.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
key = mkOption {
|
2015-09-27 18:30:02 +01:00
|
|
|
type = types.nullOr types.path;
|
|
|
|
default = null;
|
2015-05-07 16:49:01 +01:00
|
|
|
description = ''
|
|
|
|
Fully qualified path to the server key.
|
|
|
|
|
2015-09-27 18:30:02 +01:00
|
|
|
Note that reloading the <literal>taskserver.service</literal> causes
|
|
|
|
a configuration file reload before the next request is handled.
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
};
|
2016-04-05 15:09:12 +01:00
|
|
|
|
|
|
|
trust = mkOption {
|
|
|
|
type = types.enum [ "allow all" "strict" ];
|
|
|
|
default = "strict";
|
|
|
|
description = ''
|
|
|
|
Determines how client certificates are validated.
|
|
|
|
|
|
|
|
The value <literal>allow all</literal> performs no client
|
|
|
|
certificate validation. This is not recommended. The value
|
|
|
|
<literal>strict</literal> causes the client certificate to be
|
|
|
|
validated against a CA.
|
|
|
|
'';
|
|
|
|
};
|
2015-05-07 16:49:01 +01:00
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
config = mkIf cfg.enable {
|
|
|
|
|
|
|
|
environment.systemPackages = [ pkgs.taskserver ];
|
|
|
|
|
2015-09-27 14:35:42 +01:00
|
|
|
users.users = optional (cfg.user == "taskd") {
|
|
|
|
name = "taskd";
|
|
|
|
uid = config.ids.uids.taskd;
|
|
|
|
description = "Taskserver user";
|
|
|
|
group = cfg.group;
|
|
|
|
};
|
|
|
|
|
|
|
|
users.groups = optional (cfg.group == "taskd") {
|
|
|
|
name = "taskd";
|
|
|
|
gid = config.ids.gids.taskd;
|
|
|
|
};
|
|
|
|
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
systemd.services.taskserver-ca = mkIf needToCreateCA {
|
|
|
|
requiredBy = [ "taskserver.service" ];
|
|
|
|
after = [ "taskserver-init.service" ];
|
|
|
|
description = "Initialize CA for TaskServer";
|
|
|
|
serviceConfig.Type = "oneshot";
|
|
|
|
serviceConfig.UMask = "0077";
|
|
|
|
|
|
|
|
script = ''
|
|
|
|
mkdir -m 0700 -p "${cfg.dataDir}/keys"
|
|
|
|
chown root:root "${cfg.dataDir}/keys"
|
|
|
|
|
|
|
|
if [ ! -e "${cfg.dataDir}/keys/ca.key" ]; then
|
|
|
|
${pkgs.gnutls}/bin/certtool -p \
|
|
|
|
--bits 2048 \
|
|
|
|
--outfile "${cfg.dataDir}/keys/ca.key"
|
|
|
|
${pkgs.gnutls}/bin/certtool -s \
|
|
|
|
--template "${pkgs.writeText "taskserver-ca.template" ''
|
2016-04-05 15:16:14 +01:00
|
|
|
cn = ${cfg.server.fqdn}
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
cert_signing_key
|
|
|
|
ca
|
|
|
|
''}" \
|
|
|
|
--load-privkey "${cfg.dataDir}/keys/ca.key" \
|
|
|
|
--outfile "${cfg.dataDir}/keys/ca.cert"
|
|
|
|
|
|
|
|
chgrp "${cfg.group}" "${cfg.dataDir}/keys/ca.cert"
|
|
|
|
chmod g+r "${cfg.dataDir}/keys/ca.cert"
|
|
|
|
fi
|
2015-05-07 16:49:01 +01:00
|
|
|
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
if [ ! -e "${cfg.dataDir}/keys/server.key" ]; then
|
|
|
|
${pkgs.gnutls}/bin/certtool -p \
|
|
|
|
--bits 2048 \
|
|
|
|
--outfile "${cfg.dataDir}/keys/server.key"
|
|
|
|
|
|
|
|
${pkgs.gnutls}/bin/certtool -s \
|
|
|
|
--template "${pkgs.writeText "taskserver-cert.template" ''
|
2016-04-05 15:16:14 +01:00
|
|
|
cn = ${cfg.server.fqdn}
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
tls_www_server
|
|
|
|
encryption_key
|
|
|
|
signing_key
|
|
|
|
''}" \
|
|
|
|
--load-ca-privkey "${cfg.dataDir}/keys/ca.key" \
|
|
|
|
--load-ca-certificate "${cfg.dataDir}/keys/ca.cert" \
|
|
|
|
--load-privkey "${cfg.dataDir}/keys/server.key" \
|
|
|
|
--outfile "${cfg.dataDir}/keys/server.cert"
|
|
|
|
|
|
|
|
chgrp "${cfg.group}" "${cfg.dataDir}/keys/server.key"
|
|
|
|
chmod g+r "${cfg.dataDir}/keys/server.key"
|
|
|
|
chmod a+r "${cfg.dataDir}/keys/server.cert"
|
|
|
|
fi
|
|
|
|
|
|
|
|
chmod go+x "${cfg.dataDir}/keys"
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
systemd.services.taskserver-init = {
|
|
|
|
requiredBy = [ "taskserver.service" ];
|
|
|
|
description = "Initialize Taskserver Data Directory";
|
2015-05-07 16:49:01 +01:00
|
|
|
|
|
|
|
preStart = ''
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
mkdir -m 0770 -p "${cfg.dataDir}"
|
|
|
|
chown "${cfg.user}:${cfg.group}" "${cfg.dataDir}"
|
2015-05-07 16:49:01 +01:00
|
|
|
'';
|
|
|
|
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
script = ''
|
|
|
|
${taskd} init
|
|
|
|
echo "include ${configFile}" > "${cfg.dataDir}/config"
|
|
|
|
touch "${cfg.dataDir}/.is_initialized"
|
|
|
|
'';
|
|
|
|
|
|
|
|
environment.TASKDDATA = cfg.dataDir;
|
|
|
|
|
|
|
|
unitConfig.ConditionPathExists = "!${cfg.dataDir}/.is_initialized";
|
|
|
|
|
|
|
|
serviceConfig.Type = "oneshot";
|
|
|
|
serviceConfig.User = cfg.user;
|
|
|
|
serviceConfig.Group = cfg.group;
|
|
|
|
serviceConfig.PermissionsStartOnly = true;
|
|
|
|
};
|
|
|
|
|
|
|
|
systemd.services.taskserver = {
|
|
|
|
description = "Taskwarrior Server";
|
|
|
|
|
|
|
|
wantedBy = [ "multi-user.target" ];
|
|
|
|
after = [ "network.target" ];
|
|
|
|
|
|
|
|
environment.TASKDDATA = cfg.dataDir;
|
2015-05-07 16:49:01 +01:00
|
|
|
|
|
|
|
serviceConfig = {
|
nixos/taskserver: Refactor module for CA creation
Now the service starts up if only the services.taskserver.enable option
is set to true.
We now also have three systemd services (started in this order):
* taskserver-init: For creating the necessary data directory and also
includes a refecence to the configuration file in
the Nix store.
* taskserver-ca: Only enabled if none of the server.key, server.cert,
server.crl and caCert options are set, so we can
allow for certificates that are issued by another
CA.
This service creates a new CA key+certificate and a
server key+certificate and signs the latter using
the CA key.
The permissions of these keys/certs are set quite
strictly to allow only the root user to sign
certificates.
* taskserver: The main Taskserver service which just starts taskd.
We now also log to stdout and thus to the journal.
Of course, there are still a few problems left to solve, for instance:
* The CA currently only signs the server certificates, so it's
only usable for clients if the server doesn't validate client certs
(which is kinda pointless).
* Using "taskd <command>" is currently still a bit awkward to use, so
we need to properly wrap it in environment.systemPackages to set the
dataDir by default.
* There are still a few configuration options left to include, for
example the "trust" option.
* We might want to introduce an extraConfig option.
* It might be useful to allow for declarative configuration of
organisations and users, especially when it comes to creating client
certificates.
* The right signal has to be sent for the taskserver service to reload
properly.
* Currently the CA and server certificates are created using
server.host as the common name and doesn't set additional certificate
information. This could be improved by adding options that explicitly
set that information.
As for the config file, we might need to patch taskd to allow for
setting not only --data but also a --cfgfile, which then omits the
${dataDir}/config file. We can still use the "include" directive from
the file specified using --cfgfile in order to chainload
${dataDir}/config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-09-27 20:52:55 +01:00
|
|
|
ExecStart = "@${taskd} taskd server";
|
2015-05-07 16:49:01 +01:00
|
|
|
User = cfg.user;
|
2015-09-27 14:35:42 +01:00
|
|
|
Group = cfg.group;
|
2015-05-07 16:49:01 +01:00
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
}
|