SSH Keys Management

Edit page

You can upload an SSH private key into a project via the TeamCity web interface and then use it in VCS roots configuration or in SSH Agent build feature.

Supported Key Format

TeamCity supports keys in the PEM format only. If your private key uses a different format, it has to be converted to PEM. For example, the Putty private key format (*.ppk), not supported by TeamCity, can be converted to the PEM format using PuTTY Key Generator: use the menu Conversions | Export OpenSSH key.

tip

Recent versions of OpenSSH no longer generate keys in PEM format by default. Unfortunately the new OpenSSH format is not yet supported by TeamCity (see TW-53615). Use the following command to generate TeamCity compatible keys: ssh-keygen -t rsa -m PEM.

Uploading SSH Key to TeamCity Server

  1. In Project Settings, click SSH Keys.

  2. On the SSH Keys page, click Upload SSH Key.

  3. In the "Upload SSH Key" dialog, select a private key (usually stored in <USER_HOME>/.ssh/id_rsa or <USER_HOME>/.ssh/id_dsa).

When you upload an SSH key for a project, it is stored in <TeamCity Data Directory>/config/projects/<project>/pluginData/ssh_keys. TeamCity tracks this folder and is able to pick up new keys on-the-fly. The key will be available in the current project and its subprojects.

note

The access to the TeamCity Data Directory must be kept secure, as the keys are stored in an unmodified/unencrypted form on the file system.

Once the key is uploaded, a VCS root can be configured to use this uploaded key.

SSH Key Usage

See SSH Agent for usage from within the build scripts.

The uploaded key can be used in a VCS root. SSH key is used on the server and is also passed to the agent in case agent-side checkout is configured.

During the build with agent-side checkout, the Git plugin downloads the key from the server to the agent. It temporarily saves the key on the agent's file system and removes it after git fetch/clone is completed.

note

The key is removed for security reasons: for example, the tests executed by the build can leave some malicious code that will access the build agent file system and acquire the key. However, tests cannot get the key directly since it is removed by the time they are running. It makes it harder but not impossible to steal the key. Therefore, the agent must also be secure.

To transfer the key from the server to the agent, TeamCity encrypts it with a DES symmetric cipher. For a more secure way, configure an HTTPS connection between agents and the server.