background preloader

Admin Environment

Facebook Twitter

Public keys with putty. Previous | Contents | Index | Next 8.1 Public key authentication - an introduction Public key authentication is an alternative means of identifying yourself to a login server, instead of typing a password.

Public keys with putty

It is more secure and more flexible, but more difficult to set up. In conventional password authentication, you prove you are who you claim to be by proving that you know the correct password. The only way to prove you know the password is to tell the server what you think the password is. Public key authentication solves this problem. So you generate a key pair on your own computer, and you copy the public key to the server. There is a problem with this: if your private key is stored unprotected on your own computer, then anybody who gains access to that will be able to generate signatures as if they were you. There is more than one public-key algorithm available. 8.2 Using PuTTYgen, the PuTTY key generator. SSH Config File. Overview By creating a local configuration file for SSH, you can create shortcuts for servers you frequently access, in addition to configuring more advanced options.

SSH Config File

This article will demonstrate how to create a shortcut to your DV server, including how to keep your connection active. Requirements This article has the following dependencies: Please make sure you have a basic understanding of SSH and have configured access for the root user or a domain user. This article is provided as a courtesy. Instructions 1.

On OS X, this is located at /Applications/Utilities/Terminal.app. Touch /Users/username/.ssh/config Your .ssh directory is automatically created when you use the ssh command for the first time. Mkdir /Users/username/.ssh && chmod 700 /Users/username/.ssh 2. Vi /Users/username/.ssh/config 3. Host dv HostName example.com User domainuser 4. ServerAliveInterval 30 ServerAliveCountMax 120. Manage SSH known_hosts entries. Manage SSH host keys. Posted by Steve on Fri 2 Mar 2007 at 11:28 When connecting to a new OpenSSH server for the first time you'll be prompted to accept its host key - but how do you know if it is valid?

Manage SSH host keys

How do you manage SSH keys for multiple machines? As part of the package installation the openssh, and openssh-server will generate "host key" which is used when communicating with clients. The first time you connect to a server you'll see a message similar to this: steve@steve:~$ ssh localhost The authenticity of host 'localhost (127.0.0.1)' can't be established. This allows you to test that the key is valid, by showing you the a fingerprint (which is a hash of the full key) and prompting you to confirm its validity.

Once accepted this fingerprint will be stored in the file ~/.ssh/knownhosts either in plain text, or if you're running a recent version of OpenSSH it will be stored in a hashed format. The real question now is how do you know whether the key is valid? Build up a global fingerprint list. Installer sa clé SSH sur un serveur distant. Qui n'a jamais pesté d'avoir à constamment taper et se souvenir de dizaines de mots de passe, quand on utilise plusieurs serveurs différents ?

Installer sa clé SSH sur un serveur distant

Moi, en tous cas. Le principe est simple : générer une clé privée et une clé publique, toutes deux cryptées, et d'ajouter votre clé publique à la liste des clés autorisées du serveur distant afin de permettre l'authentification automatique sur ce dernier. Ainsi, vous pouvez définir une seule et même passphrase (mot de passe) pour vous logguer à toutes vos machines Voici la procédure : d'abord - et si ce n'est déjà fait - il vous faut installer le client openSSH : $ sudo apt-get update $ sudo apt-get install openssh-client Il faudra de même disposer de ssh-server sur la machine distante.

Ceci fait, il vous faut générer vos clés publiques et privées : $ ssh-keygen -t dsa -b 1024 Generating public/private dsa key pair.

Linux on windows