Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Enabling SNC SSH to support newer and more secure cipher algorthms for the Discovery process (i.e AES 256 encryption) - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Enabling SNC SSH to support newer and more secure cipher algorthms for the Discovery process (i.e AES 256 encryption)
KB0748632

Enabling SNC SSH to support newer and more secure cipher algorthms for the Discovery process (i.e AES 256 encryption)


11062 Views Last updated : Apr 7, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

SNCSSH is a ServiceNow implementation of an SSH client and is active by default for all MID Servers on new instances, via a MID Server property. SNCSSH is part of the MID Server SSH Library and can be used in place of Legacy J2SSH. One of the advantages of using SNCSSH is its support for newer cipher algorithms compared to J2SSH. SNCSSH supports:

- Key Exchange Algorithms: diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha256, diffie-hellman-group1-sha1
- Signature Algorithms: ssh-dss, ssh-rsa
- Client-to-Server Cipher Algorithms: aes128-ctr, aes192-ctr, aes256-ctr, 3des-ctr, aes128-cbc, aes192-cbc, aes256-cbc, 3des-cbc, none
- Client-to-Server MAC Algorithms: hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512, hmac-md5, hmac-md5-96
- Client-to-Server Compression Algorithms: none


The mid.property.ssh.use_snc will determine if snc ssh will be used for probe-based discovery.
The mid.sa.ssh.use_sncssh will determine if snc ssh will be used for patterns-based discovery.

Customers who have upgraded from older versions where J2SSH was the default library will not be forced to use SNC SSH and will need to manually enable SNC SSH if they wish to use it.

Release

Available from Kingston onwards

Resolution

We recommend that you take the following actions to enable SNC SSH for discovery:

  1. Log into your instance as an admin
  2. Go to Mid Servers > Properties (/ecc_agent_property_list.do)
  3. Create/Configure the following properties:
    -mid.property.ssh.use_snc = true
    -mid.sa.ssh.use_sncssh = true

Related Links

Please see KB0594703 if you want to know how to force AES 256 encryption for the communication between the mid server and the instance. 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.