Selinux prevents NetworkManager-ssh connecting to remote ports that are not 22

Reproducible: Always

Steps to Reproduce:
1. Create a connection with a custom port (not 22)
2. Try to connect
Actual Results:  
Connection fails with selinux logs:
Mar 27 12:57:19 fed setroubleshoot[665036]: SELinux is preventing ssh from name_connect access on the tcp_socket port 40111. For complete SELinux messages run: sealert -l 627431f3-51ef-4ab7-b2fc-e88d3a87c3ee
Mar 27 12:57:19 fed setroubleshoot[665036]: SELinux is preventing ssh from name_connect access on the tcp_socket port 40111.#012#012*****  Plugin catchall_boolean (89.3 confidence) suggests   ******************#012#012If you want to allow system to run with NIS#012Then you must tell SELinux about this by enabling the 'nis_enabled' boolean.#012#012Do#012setsebool -P nis_enabled 1#012#012*****  Plugin catchall (11.6 confidence) suggests   **************************#012#012If you believe that ssh should be allowed name_connect access on the port 40111 tcp_socket by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'ssh' --raw | audit2allow -M my-ssh#012# semodule -X 300 -i my-ssh.pp#012

Expected Results:  
Connection should succeed, and not be blocked by selinux

Upstream 1.3.1 solves that problem