/usr/sbin/sshd -D -oCiphers=aes256-gcm@op... what does it mean?

[formiche]

Hi to all!
I have the problem in object, I don't understand what it means.
The text in the object is the result of the command: ps xaf --sort -pcpu | grep sshd. The complete result is, for example, the following:

1001535 ? Ss 0:00 /usr/sbin/sshd -D -oCiphers=aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes256-cbc,aes128-gcm@openssh.com,aes128-ctr,aes128-cbc -oMACs=hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512 -oGSSAPIKexAlgorithms=gss-curve25519-sha256-,gss-nistp256-sha256-,gss-group14-sha256-,gss-group16-sha512-,gss-gex-sha1-,gss-group14-sha1- -oKexAlgorithms=curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-excha

I disabled access to server as root user. If I kill that process I keep connected.
Is it possibile it was nodejs that creates this problem?
I noticed that when this process is active the node process generate high usage level of cpu.
I'm looking for the network but I don't find explanation.
Thanks to all!

Mic

[TrevorH]

That process is your main sshd daemon and is perfectly normal. It almost certainly has nothing to do with whatever problem you are looking at. To confirm that it is the sshd process, run systemctl status sshd and it should list " Main PID: 1001535 (sshd)".