Skip to main content

How To Disable SSH Server Weak Key Exchange Algorithm diffie-hellman-group1-sha1 in Oracle Linux 7

How To Disable SSH Server Weak Key Exchange Algorithm diffie-hellman-group1-sha1 in Oracle Linux

The diffie-hellman-group1-sha1 key exchange algorithm is considered a weaker algorithm.OpenSSH on Oracle Linux 7 currently supports and enables the algorithm that security/vulnerability scanners such as Qualys may detect as vulnerable.
To ensure optimal security, one should consider disabling weaker OpenSSH key exchange algorithms.
This document describes how to disable the diffie-hellman-group1-sha1 key exchange algorithm within on Oracle Linux 7.
The same process may also be used to disable other algorithms.

Steps to disable Oracle Linux 7 OpenSSH diffie-hellman-group1-sha1 key exchange algorithm

1. Check whether key exchange algorithm diffie-hellman-group1-sha1 is currently enabled:

# sshd -T | egrep -i ^kexalgorithms | grep diffie-hellman-group1-sha1; echo $?
or
# nmap --script ssh2-enum-algos -sV -p 22 127.0.0.1 | grep diffie-hellman-group1-sha1; echo $?


2. Backup original SSH server configuration file e.g.:

# cp -p /etc/ssh/sshd_config /etc/ssh/sshd_config.orig


3. Generate and output the default list of supported key exchange algorithms to the SSH server configuration file excluding the diffie-hellman-group1-sha1 algorithm e.g.:

# ssh -Q kex | grep -v 'diffie-hellman-group1-sha1' | tr '\n' ',' >> /etc/ssh/sshd_config


4. Correctly format the newly added entry to the SSH server configuration file i.e.:

  • prepend the resultant kex list with 'KexAlgorithms ' at the last line.
  • remove already deprecated algorithms from the list i.e. gss-gex-sha1-,gss-group1-sha1-,gss-group14-sha1-
  • remove any trailing comma (,) from the last entry in the list

The final entry should appear similar to the following:

# tail -n 1 /etc/ssh/sshd_config
KexAlgorithms diffie-hellman-group14-sha1,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,curve25519-sha256,curve25519-sha256@libssh.org


5. Restart the SSH server

# systemctl restart sshd


6. Verify the diffie-hellman-group1-sha1 key exchange algorithm is disabled now.

# sshd -T | egrep -i ^kexalgorithms | grep diffie-hellman-group1-sha1; echo $?
or
# nmap --script ssh2-enum-algos -sV -p 22 127.0.0.1 | grep diffie-hellman-group1-sha1; echo $?


7. Where applicable, re-run the security scan that originally detected the weakness - it should no longer be reported.

Same can also be done for Ciphers as well.


Reference:Oracle Linux: How To Disable SSH Server Weak Key Exchange Algorithm diffie-hellman-group1-sha1 (Doc ID 2803881.1)



If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...