Eelco Dolstra ffedee6ed5 Start ssh-agent as a user unit ... This has some advantages: * You get ssh-agent regardless of how you logged in. Previously it was only started for X11 sessions. * All sessions of a user share the same agent. So if you added a key on tty1, it will also be available on tty2. * Systemd will restart ssh-agent if it dies. * $SSH_AUTH_SOCK now points to the /run/user/<uid> directory, which is more secure than /tmp. For bonus points, we should patch ssh-agent to support socket-based activation...		2014-04-18 00:45:26 +02:00
..
config	Start ssh-agent as a user unit	2014-04-18 00:45:26 +02:00
hardware	mesa: have all output on /run/opengl-driver{,-32}	2014-04-14 21:38:23 +02:00
installer	nixos-rebuild: Fallback for upgrading Nix	2014-04-15 12:07:34 +02:00
misc	nixos: add spiped service module	2014-04-15 03:33:47 -05:00
profiles	no-x-libs.nix: Disable su xauth forwarding, and X11 dependency in dbus	2014-04-16 16:58:06 +02:00
programs	Start ssh-agent as a user unit	2014-04-18 00:45:26 +02:00
security	Apply pam_loginuid before pam_systemd	2014-04-17 11:35:18 +02:00
services	Start ssh-agent as a user unit	2014-04-18 00:45:26 +02:00
system	Add support for user units	2014-04-18 00:38:40 +02:00
tasks	Allow upstream systemd units to be extended	2014-04-17 18:52:31 +02:00
testing	Rewrite ‘with pkgs.lib’ -> ‘with lib’	2014-04-14 16:26:48 +02:00
virtualisation	Drop ALSA dependency in containers	2014-04-16 01:44:43 +02:00
module-list.nix	nixos: add spiped service module	2014-04-15 03:33:47 -05:00
rename.nix	Start ssh-agent as a user unit	2014-04-18 00:45:26 +02:00