Openssh.com Log Message

,
1

I have started receiving the following message repeating in my raw core log. I just started noticing after the most recent upgrade.

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

** WARNING: connection is not using a post-quantum key exchange algorithm.

** This session may be vulnerable to "store now, decrypt later" attacks.

** The server may need to be upgraded. See OpenSSH: Post-Quantum Cryptography

IMG4945
IMG49451226×770 47.2 KB

2

Is this being reported from an App, Custom Integration, or Core Integration?

3

I am unable to determine what is causing the messages. I stopped several of the apps that could possibly be utilizing ssh. The messages continued.

4

I may have found what is causing this.

I have a sensor that is updated via reoccurring SSH calls into my Synology. It looked like the Synology’s SSH daemon is behind on OpenSSH version. I am up to date on my Synology OS. I need to wait until Synology makes the update. For now it is just an annoying log message.