Your browser does not allow storing cookies. We recommend enabling them.

SSH

Using Public-Key Authentication

Public-key authentication is based on the use of digital signatures. To use public-key authentication, you must first create a key pair on the client, and upload the public key to the server. For instructions, see User Authentication with Public Keys.

At connection establishing phase, the server sends Tectia ConnectSecure a challenge. Sign the challenge with the passphrase of your private key. After the server has successfully completed user authentication, the Secure Shell connection to the server is opened.

The Connection Broker operates automatically as an authentication agent. It offers an easy method for utilizing also digital certificates and smart cards. The authentication forwarding functionality allows the forwarding of public-key authentication over several Secure Shell connections. The Connection Broker is started automatically when you start Tectia ConnectSecure.


 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now