Il 2017-08-09 11:30 Darac Marjal ha scritto:
On Tue, Aug 08, 2017 at 03:55:52PM -0400, Bill Shirley wrote:
Looks like you haven't opened up sftp(port 115) in Shorewall. Post
on the
shorewall-us...@lists.sourceforge.net list. Tom Eastep is very
helpful.
[..]
I don't know if is Fail2ban
Hi,
There is a big difference between sftp (SSH file transfer) and ftps (FTP
over SSL).
For SFTP, port 115 seems to be reserved (but I believe most ssh
implementations just use the ssh port (22) for this).
For FTPS, ports 989 (data) and 990 are reserved. It depends on what you
configured in
Looks like you haven't opened up sftp(port 115) in Shorewall. Post on the
shorewall-us...@lists.sourceforge.net list. Tom Eastep is very helpful.
If it were fail2ban blocking traffic, you would see it in the log file.
Note if you're not using fail2ban with ipsets actions instead of iptables,
Hi friends,
I tell you immediately that I am not clear whether the matter concerns
Shorewall rather than Fail2ban, so you have pity for me :-)
I've configured ProFtpd to connect by tls (SSLv3 TLSv1 -> Letsencypt
certificate) and if I stop shorewall the "sftp" connection works fine,
but with
