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

SSH Tectia

Settings on the Client Side

For example, the following configuration can be used in the ssh-broker-config.xml file:

<profile name="sftexa"
              id="id1"
              host="sftexa.ssh.com"
              port="12345"
              connect-on-startup="no"
              user="sftuser">
       <ciphers>
         <cipher name="crypticore128@ssh.com" />
       </ciphers>
       <macs>
         <mac name="crypticore-mac@ssh.com" />
       </macs>
       <transport-distribution num-transports="4">
       </transport-distribution>
       <authentication-methods>
         <authentication-method name="publickey" />
       </authentication-methods>
       <compression name="none"/>
       <server-banners visible="no" />
</profile>

To enable non-interactive authentication, the private key on the Client is stored with a NULL passphrase. It is important that the key directory and the key file have the correct permissions (for example, 700). For more information, see User Authentication with Public Keys.



Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps