Ssh-3-keypair Attempt To Generate Server Keys Failed

| 08-05-2021
[RAND-1-100] Comments

  1. Ssh-3-keypair Attempt To Generate Server Keys Failed Server
  2. Ssh-3-keypair Attempt To Generate Server Keys Failed Download
  3. Ssh-3-keypair Attempt To Generate Server Keys Failed Windows 10

So a single point of reference for generating SSH keys is Generating SSH Keys for SFTP Adapters – Type 1 – Process Integration – SCN Wiki.

Feb 07, 2019.LINK FOR VIDEO I USED TO SET UP MY SERVER BEFOR. Skip navigation. Failed to getinfo server after 3 attempts issue in FiveM. How To Get a LICENSE KEY for a FXServer (FiveM server.

  • It is not directly possible to add keypair to the VM without knowing its password atleast. But I wont say it's impossible because we can use tool like guestfish to enter into the VHD of VM and do add the keygen file which will reflect in next boot of the VM.
  • SSH keys can serve as a means of identifying yourself to an SSH server using public-key cryptography and challenge-response authentication. The major advantage of key-based authentication is that in contrast to password authentication it is not prone to brute-force attacks and you do not expose valid credentials.

Recent observations from multiple projects where people create SSH public key and give to SFTP server team and mysteriously it connect then. It all left me searching here and there solve the problem. The causes of this are –

1. SAP PI Developer not aware whether keys are valid or not?

2. SFTP server administrator may just believe key provided are correct?

3. Basis team may not may also be unaware how the end ssh key should be? Is it uploaded at the correct place? Are the permissions correct.

So here I am, making an attempt to bridge the gap and provide you the “KEY for Key Generation”. Let us first know what all we may need, the so called –

Â

PRE-REQUISITES

1. WinScp (you may have other tools, but this one is simple and easily available 🙂 )

2. Cygwin installed with openSSH and openSSL packages

Video – https://www.youtube.com/watch?v=hh-V6el8Oxk

              Text – Installing Cygwin/X

3. Putty (FAMOUS) – this and WinScp can be combined.

4. NWA keystore access to create keystores

The above is enough to generate the keys and have it ready for the development. But, we PI consultants end up getting erroneous results for a new configuration. So to make sure we give the tested keys to client here is a tutorial to create the SFTP server on your local windows machine.

Apart from the links in the Part2, I will explain hand-picked steps out of the tutorial to set up sftp server correctly and quickly in the first attempt ( 😉 ) . So enough of reading let us start with the configuration.

1. Start Winscp -> Click on Tools -> Run PuTTygen

2. Select Parameters – SSH-2 RSA and Enter number of bits -2048. Click Generate.

3. Now you need to save the PrivateKey (ppk), PublicKey and PublicKey to be saved in SFTP server.

Note- i) The public key saved from “Save Public Key” and the “Public Key” to be saved in SFTP server can’t be same. The public key                                        saved starts with —- BEGIN SSH2 PUBLIC KEY —-, but the key to be pasted in SFTP server starts with ssh-rsa.

 ii) In the file authorized_keys, each line refers to a separate public key. So we also need to make sure there are no new line                                              characters in our key. So an authorized_keys file will look as below-

Â

4. Below are the Keys generated. Please follow the instruction in screenshots carefully.

Once the keys are generated, click on Save Private Key, Save Public Key and copy paste the key to be pasted in authorized_keys file and save.

Now, you will have 3 files generated. PPK private key, SSH public Key, SSH Public key to be pasted on to SFTP server. I have named 3 files as privateKey_SFTP.ppk, publicKey_SFTP.pub and publicKey_SSH.pub. Files will look as below.

5.Now sendpublicKey_SSH.pub file to SFTP server team to install via mail. If you want to test it with a local SFTP server, refer part 2 or video link embedded above.

Â

Ssh-3-keypair Attempt To Generate Server Keys Failed

6. Before we put the key to SAP PO NWA KeyStore we must make sure our keys are set up correctly. To test this we can use WinScp or PuTTy.

Â

Testing With WinScp

Â

Â

In Advanced->Click Authentication under SSH -> Select the ppk private key

Â

Â

Â

Â

When you login for the first time, you will get a warning with the server’s fingerprint. This is a good sign showing it is able to reach the SFTP server. Just click Yes.

Â

Â

If you have chosen Passphrase while generating the key it will ask the passphrase else it will connect.

Â

And that is it, you will be placed at the SFTProot folder.

Â

Â

This must be your Hurray! moment. After this the task is easy. We need to convert PPK to PKCS12 and import in NWA. Lets see how to do that too.

Â

6. Now we need to convert privateKey_SFTP.ppk to pkcs12 format for SAP PO to import in NWA key store. For this Cygwin must be installed with openssl package

Â

  i) We will generate a PEM private key. I am naming it as privateKey_SFTP.pem. So again launch WinSCP->Tools->Run PuttYgen

  ii) Click on File->Load Private Key and choose your PPK key (privateKey_SFTP.ppk)

Â

  Â

      iii) Once the key is loaded, I recommend remove the passphrase this time and click Conversions->Export Open SSH Key, it will give warnign for blank passphrase. Just click YES and proceed. Name it as <yourname>.pem (privateKey_SFTP.pem)

Â

It will look like

Â

Â

    iv) Now launch cygwin as administrator . Right click -> run as administrator. Now run change directory ( cd) command to move to directory where you kept you pem file. for the ease place it in any drve G: , D: . This will save us to struggle with CD command 😉

v) use OpenSSL package commands to create X.509 certificate

Ssh-3-keypair Attempt To Generate Server Keys Failed Server

    openssl req -new-x509 -days 3650-key privateKey_SFTP.pem -out x509_certificateSFTP.pem

Â

Â

Â

      Â

Â

                v) Now we will create PKCS 12 key to be imported in NWA with a password. Continuing in the CYGWIN enter following command

Â

            openssl pkcs12 -export -in x509_certificateSFTP.pem -inkey privateKey_SFTP.pem -out sftp_keystore.p12

Â

Â

Â

Ssh-3-keypair Attempt To Generate Server Keys Failed Download

7. Now login to NWA of SAP PO/PI .. http://<host>:<port>/nwa…… Configuration->Certificates and keys

Â

      i) Click on Add View-> Give View Name

Â

       ii) choose SFTP_KeyStore -> Import Entry-> PKCS#12 and click choose file to select the p12 generated. Provide the password which we set in cygwin while generating P12 and click import

Â

Â

Â

Â

This is all. Now you can select the above private key in your SFTP channel and continue with your development.

Ssh-3-keypair Attempt To Generate Server Keys Failed Windows 10

Â

Â

In the Part 2, I will show how to test the connection with PuTTy (already shown with WinScp) and also how to set up the local SFTP server. Stay Tuned for Part2

Â

Â

How to Generate a Public/Private KeyPair for Use With Solaris Secure Shell

Users must generate a public/private key pair when their site implementshost-based authentication or user public-key authentication. For additionaloptions, see the ssh-keygen(1) manpage.

Before You Begin

Determine from your system administrator if host-based authenticationis configured.

  1. Start the key generation program.


    where -t is the type of algorithm, one of rsa, dsa, or rsa1.

  2. Specify the path to the file that will hold the key.

    Bydefault, the file name id_rsa, which represents an RSAv2 key, appears in parentheses. You can select this file by pressing the Return key. Or, you can type an alternative file name.


    The file name of the public key is created automatically by appendingthe string .pub to the name of the private key file.

  3. Type a passphrase for using your key.

    This passphraseis used for encrypting your private key. A null entry is stronglydiscouraged. Note that the passphrase is not displayed when youtype it in.


  4. Retype the passphrase to confirm it.


  5. Check the results.

    Check that the path to the keyfile is correct.


    At this point, you have created a public/private key pair.

  6. Choose the appropriate option:

    • If your administrator has configuredhost-based authentication, you might need to copy the local host's publickey to the remote host.

      You can now log in to the remote host.For details, see How to Log In to a Remote Host With Solaris Secure Shell.

      1. Type the command on one line with no backslash.


      2. When you are prompted, supply your login password.


    • If your site uses user authentication with public keys, populateyour authorized_keys file on the remote host.

      1. Copy your public key to the remote host.

        Type thecommand on one line with no backslash.


      2. When you are prompted, supply your login password.

        Whenthe file is copied, the message “Key copied” is displayed.


  7. (Optional) Reduce the prompting for passphrases.

    For a procedure, see How to Reduce Password Prompts in Solaris Secure Shell. For more information, see the ssh-agent(1) and ssh-add(1) man pages.

Example 19–2 Establishing a v1 RSA Key for a User

In the following example, the user cancontact hosts that run v1 of the Solaris Secure Shell protocol. To be authenticated by v1hosts, the user creates a v1 key, then copies the public key portion to theremote host.