What is the difference, on the SSH server side, in end user key authentication configuration between Tectia and OpenSSH?
asked Jul 26 '11 at 20:35
SSH KB ♦
On most Linux and Unix systems a version of OpenSSH comes installed by default. OpenSSH is an open source product based on code originally developed by the founder Tectia (formerly SSH Communications Security) who then released the code publicly while at the same time continuing to develop the commercial SSH version (i.e. central management, X509v3/PKI, smartcard/token support, Kerberos/SSO support plus other features)). More info on that can be found here.
OpenSSH uses a completely different approach to configure the end user key authentication on the SSH server side. Please notice that Tectia Server on Windows/Linux/Unix/zOS operating systems also supports similar OpenSSH type configuration syntax on top of the normal Tectia's "authorized_keys directory" approach.
Summary in brief:
In OpenSSH keys are stored in the authorized_keys file.
No other end user key authentication configuration methods in OpenSSH server
Tectia Server on Linux, Windows & Unix (not zOS)
Keys can be configured in one of 3 places:
For example on Windows this would be either:
Authorized_keys file (OpenSSH)
Tectia Server also supports OpenSSH’s authorized_keys file (yes, a file!)
See Authorized_keys file from OpenSSH configuration above