-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/27/2013 10:44 AM, Darr247 wrote:
On 2013-06-27 7:37 AM, Tim Verhoeven wrote:
> That is of course a easy workaround. But changing the port on the service
> IP would mean that the all customers would need to access SFTP over a
> non standard port and the purpose of the whole exercise was to provide a
> file transfer service over a simple standard port. Port 22 ticks all the
> boxes ;) And changing the port for the internal IP would mean that that
> server would be the only one running SSH over a different port, making it
> none standard and require a lot of custom work for all our management
> scripts.
I thought the "standard port" for FTP over SSL (ftps) was 989 ?
http://www.iana.org/assignments/service-names-port-numbers/service-names-...
-- selinux mailing list selinux(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux Looks like you are right.
Not sure why no one ever hit this before.
3e203bce34765e020591aca9a1c0b883c42d6122 fixes this in git.
Miroslav can you back port this to F18, F19, RHEL*.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlHMkUEACgkQrlYvE4MpobPv2QCePC1cQOsnHHmSZphPca20ktXl
ZLkAoIXD4FBQ+gPrp/73+ke6gwSCrNAl
=8vN1
-----END PGP SIGNATURE-----