Message-ID: <2099074234.4188.1711699821259.JavaMail.confluence@unimus-dev1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4187_1552210947.1711699821258" ------=_Part_4187_1552210947.1711699821258 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html SSH key types and formats

SSH key types and formats

Please note we have update our SSH client starting with Unimus 2= .2.3. The table below applies to version 2.2.3 or newer.

Unimus currently only supports SSH keys without passwords, so the key be= ing imported into Unimus must not be password-protected.The SSH keys imported into Unimus are stored encrypted in the Unimus DB (= using the encryption key configured during the Deployment Wizard).

Supported key types:

=20
ssh-ed2=
5519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521,
rsa-sha2-512, rsa-sha2-256, ssh-rsa, ssh-dss, ssh-dsa
=20

SSH private keys in the following formats are currently supported:

  rsa dsa ecdsa ed25519
PEM yes yes yes yes
PKCS8 yes yes yes yes
OpenSSH
(RFC4716)
yes yes yes yes

Different versions of ssh-keygen (OpenSSH) use differen= t default key types and formats across the different OpenSSH versions.

= Key generation and conversion / transformation

If you have an existing key in OpenSSH format, you can use ssh-k= eygen to transform key formats. This command will transform an Ope= nSSH private key into a PEM encoded key:

=20
ssh-key=
gen -e -f /path/to/openssh.key -m PEM > /path/to/new_pem.key

-e read OpenSSH formatted key
-f read from file
-m export format
=20

Alternatively, you can generate a new key pair already formatted in a su= pported format:

=20
ssh-key=
gen -t ecdsa -m PEM -f /path/to/key

-t use ecdsa type
-m use PEM format
-f output to file
=20
------=_Part_4187_1552210947.1711699821258--