Re: sshd fatal - no matching cipher found -- MIDRANGE-L

Subject: Re: sshd fatal - no matching cipher found
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Wed, 19 Feb 2020 19:04:08 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello Steve,

Am 19.02.2020 um 17:03 schrieb Steve Richter <stephenrichter@xxxxxxxxx>:

getting this message in QSYSOPR:

Message . . . . : sshd[128117]: fatal: ssh_dispatch_run_fatal: Connection
to
185.202.1.240: no matching cipher found

That's quite normal if your machine is exposed to the internet. I see these and a lot more kind of tries to "hack" into ssh with numerous different users, password guesses, binary fuzzing, …

Unfortunately, I don't know how to suppress this message in IBM i.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: sshd fatal - no matching cipher found , Jack Woehr
Re: sshd fatal - no matching cipher found , Steve Richter

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.