On Tue, 24.06.14 14:40, Alexander Vladimirov
([email protected]) wrote:
> Seems like remote command execution was broken somewhere around systemd 213
>
> Remote access to systemd 212 host:
> [root@host1 ~]# systemctl --version
> systemd 212
> +PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
> +SECCOMP -APPARMOR
>
> $ systemctl -H idkfa@host1 status
> Enter passphrase for key '/home/idkfa/.ssh/id_rsa':
> ● idkfa@host1
> State: degraded
> Jobs: 0 queued
> Failed: 3 units
> Since: Вт 2014-06-10 17:58:32 KRAT; 1 weeks 6 days ago
> CGroup: /
>
> Remote access to systemd 214 host (same with systemd 213):
> [root@host2 ~]# systemctl --version
> systemd 214
> +PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
> +SECCOMP -APPARMOR
>
> $ systemctl -H idkfa@host2 status
> Failed to read server status: Connection timed out
>
> Both hosts have the same authorized ssh key installed and systemd with
> default configuration.
Fixed in git!
And as special gimmick while I did this I also added a new trick to the code:
$ systemctl -H root@foobar:waldo
This will connect as root to host "foobar", and then enter the container
"waldo" there.
Lennart
--
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
