Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Network Configuration Manager (NCM) > NCM supported encryption protocols for SSH

NCM supported encryption protocols for SSH

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,788 Votes: 5 Revisions: 10

Overview

This article provides information on encryption protocols for SSH supported by NCM.

Environment

All NCM versions

Detail

NCM supports the following encryption protocols for SSH:

  • DES
  • 3DES (TripleDES)
  • AES
  • BLOWFISH
  • AES128
  • AES192
  • AES256
  • CAST128


While negotiating connection with device that NCM is attempting to use encryption algorithms for: 

  • SSH1

    NCM tries to negotiate the TripleDES algorithm first. If that fails, NCM tries Blowfish. If Blowfish is not available (on the remote server), NCM  falls-back to DES.
     
  • SSH2

    NCM tries to negotiate an AES algorithm first (any type). If that fails, NCM tries TripleDES. If TripleDES is not available, NCM tries Blowfish. If Blowfish fails, NCM drops the connection instead of trying DES, which most (new) servers don't support because of its poor security.
Last modified

Tags

Classifications

Public