Correct way to handle SELinux for a systemd-started SSH VPN

[Chris Adams]

I am starting an SSH VPN connection with a systemd service.  It's just a
simple service, with an ExecStart to run ssh.  If I wrap it with a shell
(ExecStart=/bin/sh -c "/usr/bin/ssh %i"), it runs; if I take out the
shell wrap (ExecStart=/usr/bin/ssh %i), it fails due to SELinux not
allowing it.  If I set permissive mode, there's a whole lot of different
things that init_t is not allowed to do. :)

So obviously I can just run with the shell wrapper, but is there a more
proper way to do this?
-- 
Chris Adams <linux(a)cmadams.net&gt;