SSH must not be allowed in the main worker process apparmor profile

[okurz]

I consider this a bad idea and this was the reason why we even have the containerized s390x and ipmi worker instances. If we allow to ssh out from the main worker process already then apparmor doesn't do much anymore

Originally posted by @okurz in #7249 (comment)

[Vogtinator]

The worker needs to be able to ssh for ssh consoles.

[Martchus]

Maybe we can somehow constrain what machines it is allowed to connect to? Although I'm wondering: Isn't the worker constrained anyway by what credentials it has (or where its key is deployed)?

[Vogtinator]

Even without running /usr/bin/ssh, the worker could just connect to anywhere using perl code. So allowing execution of /usr/bin/ssh is confinement-wise a noop.

[okurz]

Even without running /usr/bin/ssh, the worker could just connect to anywhere using perl code.

yes, but we should trust the openQA worker code more than test code.