PuTTY doesn't natively support the private key format (.pem) generated by Amazon EC2. You must convert your private key into a.ppk file before you can connect to your instance using PuTTY. You can use the PuTTYgen tool for this conversion. This tool, available for both Windows and Unix operating system, can convert keys. I running this command to create key-pair in aws: aws ec2 create-key-pair -key-name MyKeyPair The command is works. But no pem file is generate. In the docs there is no reference for how to do that. After I run the command I get the pem content file in json structure to the console. The.pem file would have been downloaded when the key pair was created. You cannot get it again. If you have lost it, you're out of luck. You cannot use a.pem file that you generated yourself unless you imported that key into AWS before the instance was launched and assigned it to the instance. Generate pem file from key pair. Oct 02, 2019 As a token of my gratitude here is a library designed to generate a public/private key pair and store them in PEM format to ESP’s SPIFFS file system. Please feel free to take a look and let me know if I’m missing anything or if there are any issues with it you can see. Generate a key pair with a third-party tool of your choice. Save the public key to a local file. For example, /.ssh/my-key-pair.pub (Linux) or C:keysmy-key-pair.pub. Save the private key to a different local file that has the.pem extension.
Thank you so much for your help. I tried what you've suggested. It works! I am so happy for that. But there is still some warnings.
What I've done as below:
My redhat is a new server running redhat enterprise server 6. There isn't ssh2_config file. So like what I did yesterday, I uncommented a line contains 'X11Forwarding yes' in sshd_conf.
Back to Mac, in terminal, type 'xterm&'. In a X terminal, using ssh login to redhad, as Rod suggested. I can login but got two warnings:
Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.
Although I got those warnings, I still typed xterm& and opened a new xterm which comes from redhat. Then try 'xclock&'. It displayed!! So great!
Now, I have an other question. I opened 'firefox' from xterm. Firefox was also booted up, but the letters on menu and top bar were blurred. And the warnings I got were:
Xlib: extension 'RANDR' missing on display 'localhost:10.0'.
Xlib: extension 'RANDR' missing on display 'localhost:10.0'.
Xlib: extension 'RANDR' missing on display 'localhost:10.0'.
Have you ever met such problem?
This is a new problem. But I already feel so happy that you help me solved a problem which had bothered me for more than three days! Thanks all your help!
Untrusted X11 Forwarding Setup Failed: Xauth Key Data Not Generated File
Jul 29, 2016 Warning: untrusted X11 forwarding setup failed: xauth key data not generated Warning: No xauth data; using fake authentication data for X11 forwarding. X11 forwarding request failed on channel 0 conq: repository access denied. Fatal: Could not read from remote repository. Running on OSX and using bash. Any ideas or help would be appreciated. Logging in with X11 via ssh gives the warnings Warning: untrusted X11 forwarding setup failed: xauth key data not generated Warning. Stack Exchange Network Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their. Warning: untrusted X11 forwarding setup failed: xauth key data not generated Warning: No xauth data; using fake authentication data for X11 forwarding. I have previously (as in last week, ending 11/1/2008) been able to use x11 forwarding from the machine I'm trying to connect to.
