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

SSH

Using the Authorization File

Tectia Server 4.x (and earlier) required an authorization file that listed the user public keys that are authorized for login. Using the authorization file with Tectia Server 5.0 and later is optional. If the file does not exist, Tectia Server looks for authorized public keys in the authorized-keys directory (as described in User Authentication with Public Keys above), and if that fails, in the default directory for user public-keys.

The default location for the authorization file is $HOME/.ssh2/authorization on Unix, and %USERPROFILE%\.ssh2\authorization on Windows. The file location can be changed with the authorization-file attribute in the ssh-server-config.xml file. See auth-publickey.

The authorization file contains a list of public key filenames each preceded by the keyword Key. If there is more than one Key, they are all authorized for login. For more information on the syntax of the authorization file, see $HOME/.ssh2/authorization (user-specific) under the section called “Files”.

Tectia Client on Windows can upload the public keys and edit the authorization file automatically.


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more