nixlib - Alyssa's collection of Nix expressions

	Commit message (Collapse)	Author	Age
*	strongswan-swanctl: actually removed the strongswan parameter files	Bas van Dijk	2018-03-26
\|
*	strongswan-swanctl: fixed type of 'file' options	Bas van Dijk	2018-02-28
\|
*	strongswan-swanctl: disable the structured strongswan config for now in ↵	Bas van Dijk	2018-02-28
\| \| \| \| \| \|	favour of a literal config This reduces the number of option by over 600.
*	strongswan-swanctl: support strongswan-5.6.2 configuration options	Bas van Dijk	2018-02-28
\|
*	strongswan-swanctl: don't generate options for charon	Bas van Dijk	2018-02-28
\| \| \| \|	This reduces the number of options from 1152 to 756.
*	strongswan-swanctl: support strongswan-5.6.1 configuration options	Bas van Dijk	2018-02-28
\| \| \| \| \| \| \| \|	I determined which options got changed by executing the following commands in the strongswan repository: git diff -U20 5.6.0..5.6.1 src/swanctl/swanctl.opt git diff -U20 5.6.0..5.6.1 conf
*	nixos: add the strongswan-swanctl service	Bas van Dijk	2018-02-28
	The strongswan-swanctl systemd service starts charon-systemd. This implements a IKE daemon very similar to charon, but it's specifically designed for use with systemd. It uses the systemd libraries for a native integration. Instead of using starter and an ipsec.conf based configuration, the daemon is directly managed by systemd and configured with the swanctl configuration backend. See: https://wiki.strongswan.org/projects/strongswan/wiki/Charon-systemd Note that the strongswan.conf and swantctl.conf configuration files are automatically generated based on NixOS options under services.strongswan-swanctl.strongswan and services.strongswan-swanctl.swanctl respectively.