On 25 November 2016 at 09:45, Phil Shafer wrote:
Hey,
>>Someone is brute-forcing Your router password, and that is very common
>>nowadays. Good loopback filter would prevent this.
>
> Amen to this and all your other points, esp re: avoiding telnet in
> favor of ssh.
Agreed, SSH all the way, but
Alexander Arseniev writes:
>Someone is brute-forcing Your router password, and that is very common
>nowadays. Good loopback filter would prevent this.
Amen to this and all your other points, esp re: avoiding telnet in
favor of ssh.
Also you can use "system services ssh no-passwords;" to prevent
Hi Aaron,
When a telnet session is established, the process is not a telnetd dameon
after the process pass to cli process. You should be filter with grep
comand looking for "cli". Check my example:
***
tecnologia@MX240-2_LAB-RE0> show system
Always a good reference:
http://www.team-cymru.org/templates.html
http://www.cymru.com/gillsr/documents/junos-template.pdf
--
Hugo Slabbert | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E | also on Signal
On Thu 2016-Nov-24 11:07:45 +, Alexander Arseniev
wrote:
Hello,
Hello,
Someone is brute-forcing Your router password, and that is very common
nowadays. Good loopback filter would prevent this.
In addition:
1/ You can only do "request system logout" for sessions that passed
authentication+login+got TTY assigned. If You see "unsuccessful login"
it means t
I have an unauthorized telnet session attached to my router but it does not
show up under "show system users" and they have not successfully logged so
it doesn't seem that I can do the "request system logout.." thing
I do however so unsuccessful login attempts in syslog
How do I kill/discon
6 matches
Mail list logo
