Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As far as i know there aren't that many exploits for ssh. I found somewhere in a forum that it could be " SSH CRC-32 Compensation Attack Detector Vulnerability "
I think someone is trying to find an old, insecure version of SSH they can exploit.
If I break off a connection with any client, say netcat, this will be in the logs. At a minimum you could say someone is banner grabbing, because you cannot determine what they are looking for.
is there any way of telling what sort of exploit they are trying from what syslog has said?
No, you can't. Install Snort.
The only issue I've found with SSH is when I run nessus it says to use protocol 2 rather then protocol 1. It seems protocol 1 is vulnerable in some way. Its very easy to change in the sshd_config file.
The only issue I've found with SSH is when I run nessus it says to use protocol 2 rather then protocol 1. It seems protocol 1 is vulnerable in some way. Its very easy to change in the sshd_config file. NEVER run protocol v1.
I thought so to, but i tested it on my machine and it didnt apear in the logs.
What sshd version/syslog setup?
I'm running 3.4p1 at loglevel info and direct <facility>.* to the log.
Btw, if you run sshd and do not want to allow access to it for everyone, restrict access for Allow/DenyGroups/Users in sshd_config and IP addresses/ranges in tcp wrappers and the firewall.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.