Hi friends,
I've just setup Postfix Dovecot on my VPS Debian Jessie and from the
first day I've seen this logon attempt:
Nov 15 20:27:32 server postfix/smtpd[7086]: warning: hostname
212-129-49-213.rev.poneytelecom.eu does not resolve to address
212.129.49.213: Name or service not known
Nov 15
Hi Nick, and very very thanks for your kind help..
Nick Howitt ha scritto:
> Hi Davide,
>
> Rather than a login attempt, it is a connection attempt
certainlyyou're absolutely right! :-)
> and you're going
> to get a lot of those if you run your own mailserver.
..huh,I guess!
> The postfix
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
Il 2017-08-08 21:55 Bill Shirley ha scritto:
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've open the 115 port both with Shorewall and PROFTPD (and restart),
but with no luck.
Now I open
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 to
Hi Friends,
is it possible to change globally the SSHd port?
I've different configuration files, where the following parameter is
present:
port = ssh
How is it possible to change globally this value?
Is it possible to keep this parameter in the configuration files and
change it only in a
Il 2020-01-22 17:59 Mike ha scritto:
[...]
It depends upon the OS you're using
Hoops! Sure, Debian!
but it's often in
/etc/ssh/sshd_config
or somethere thereabouts
What you mean is that changing "/etc/sshd_config", fail2ban through
parameter "ssh" automatically detects the port?
Il 2020-01-22 18:32 Mike ha scritto:
[...]
What you mean is that changing "/etc/sshd_config", fail2ban through
parameter "ssh" automatically detects the port?
Assuming you haven't already configured sshd to run on an alternate
port, you'll have to do that first.
Well!
And no, if you move
Ah, well.
So changing the port number in my sshd_config plus changing *only*
fail2ban/jail.local ssh port,
this should be enough to say fail2ban, that in every configuration file
where the "ssh" parameter is present, reference is made to the "x" value
set in fail2ban/jail.local.
Right?
Tha
Perfect!
Many thanks Mike!
Il 2020-01-27 18:39 Mike ha scritto:
Yes that is correct. I've done that same thing. It works well.
1. change the sshd port in sshd_config
2. change the port= in the [sshd] section of jail.local (or wherever
you have it)
___
10 matches
Mail list logo