Message from OSSEC about fatal: no matching cipher found:

general

I've been get several emails about a Rule 1002 and it has to do with, sshd[31615]: fatal: no matching cipher found: client aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-cbc,aes128-cbc,arcfour128,arcfour,3des-cbc,none server aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com [preauth]

I'm not sure what it is or how I can fix it.

1 Reply

dwfreed 8 years ago

That's a common error triggered by SSH scanning bots and the like when you've configured sshd to only use modern ciphers, because they tend to use really ancient versions of libssh, or whatever SSH client is available on the compromised system they're running from. You can safely ignore those messages.

Reply

Description

Please enter an answer

Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Compute

Storage

Networking

Databases

Services

Developer Tools

Industries

Pricing

Community

Engage With Us

Message from OSSEC about fatal: no matching cipher found:

1 Reply

Reply

Tips: