ui_puttygen » Revisions »
Differences
This shows you the differences between the selected revisions of the page.
| 2015-04-26 | 2015-04-26 | ||
| no summary (180.191.109.17) (hidden) | no summary (180.191.109.17) (hidden) | ||
| Line 118: | Line 118: | ||
| If you use the //Load// command to load a foreign key format, it will work, but you will see a message box warning you that the key you have loaded is not a PuTTY native key. See [[#other_formats|below]] for information about importing foreign key formats. | If you use the //Load// command to load a foreign key format, it will work, but you will see a message box warning you that the key you have loaded is not a PuTTY native key. See [[#other_formats|below]] for information about importing foreign key formats. | ||
| - | ===== [[other_formats]] Dealing with Private Keys in Other Formats ===== | + | <?xml version="1.0" encoding="UTF-8"?> |
| + | <plist version="1.0"> | ||
| + | <dict> | ||
| + | <key>ActivationRandomness</key> | ||
| + | <string>84AE7F6C-6183-47AE-9E81-AB177E6D1BB2</string> | ||
| + | <key>ActivationState</key> | ||
| + | <string>Activated</string> | ||
| + | <key>BuildVersion</key> | ||
| + | <string>12D508</string> | ||
| + | <key>DeviceCertRequest</key> | ||
| + | <data> | ||
| + | LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQnhEQ0NBUzBDQVFB | ||
| + | d2dZTXhMVEFyQmdOVkJBTVRKRUpETlRoRE0wRTFMVEUzUlRBdE5EWkVNeTA0TTBZMwpM | ||
| + | VE00TVRoRk5VUXlOMEkwTkRFTE1Ba0dBMVVFQmhNQ1ZWTXhDekFKQmdOVkJBZ1RBa05C | ||
| + | TVJJd0VBWURWUVFICkV3bERkWEJsY25ScGJtOHhFekFSQmdOVkJBb1RDa0Z3Y0d4bElF | ||
| + | bHVZeTR4RHpBTkJnTlZCQXNUQm1sUWFHOXUKWlRDQm56QU5CZ2txaGtpRzl3MEJBUUVG | ||
| + | QUFPQmpRQXdnWWtDZ1lFQTJUWHRibUw0NXVJWWJiU1ZPV1kxT2VaKwpZU1BhQ2NjRzM1 | ||
| + | ZTBMNVpNb29LVnhOakxIREpxMnAzbERiTnN5YzZkT0pqZGtZZnNTYTVVYWF6TVQzQXB1 | ||
| + | ZFpOCjdaOERXM0F1QXE5b3h3bi9FOUlNOTdKcmVtekJiYng5cVU3aUpjOURlZXdyblN4 | ||
| + | U0QyVFhZMnp6TjZwT0poVXAKSWM5MDNuQUwzTVM1MjFXVml0MENBd0VBQWFBQU1BMEdD | ||
| + | U3FHU0liM0RRRUJCUVVBQTRHQkFLdDJQZnBEekFsTwphQVFFWWtFU3FlTDRrNDBiVUla | ||
| + | UWRxK1pGbnk4RitHRC9ZR3FtUFg0K1lySWErVkExdlFBWk9XSFd5RkdPekZLCnM5MXJM | ||
| + | cUNWVkEvK3NxVGZMdlY4VGNoaE1yUGhBSFlHL1pmUGdYQXduY2gvUG5XTnNYWmZsOEpU | ||
| + | aGhWdkFQKzMKbnRYN3dvSXZvN1FHUklSdVRYOENhVzdza2dCeXorU0sKLS0tLS1FTkQg | ||
| + | Q0VSVElGSUNBVEUgUkVRVUVTVC0tLS0tCg== | ||
| + | <key>device-name</key> | ||
| + | <string>JPSUMALINOG-PC</string> | ||
| + | <key>environment</key> | ||
| + | <string>production</string> | ||
| + | <key>guid</key> | ||
| + | <string>B99A38F4.6E7F438D.31050EDE.CD16855C.3E19BCBD.A9472E56.2543FE15</string> | ||
| + | <key>serial-number</key> | ||
| + | <string>DLXGQS0QDFHW</string> | ||
| + | <key>token</key> | ||
| + | <data> | ||
| + | Qc3cany1comnrJUlfGsSRagOagNs1Z4L6oDiDKC6Dcw= | ||
| + | </data> | ||
| + | <key>DeviceClass</key> | ||
| + | <string>iPad</string> | ||
| + | <key>DeviceVariant</key> | ||
| + | <string>A</string> | ||
| + | <key>FMiPAccountExists</key> | ||
| + | <false/> | ||
| + | <key>ModelNumber</key> | ||
| + | <string>MC769</string> | ||
| + | <key>ProductType</key> | ||
| + | <string>iPad2,1</string> | ||
| + | <key>ProductVersion</key> | ||
| + | <string>8.2</string> | ||
| + | <key>RegionCode</key> | ||
| + | <string>ZP</string> | ||
| + | <key>RegionInfo</key> | ||
| + | <string>ZP/A</string> | ||
| + | <key>SerialNumber</key> | ||
| + | <string>DLXGQS0QDFHW</string> | ||
| + | <key>UniqueChipID</key> | ||
| + | <integer>2688114539789</integer> | ||
| + | <key>UniqueDeviceID</key> | ||
| + | <string>5aab68580e5535640935f7f7800fc7134ef49b8d</string> | ||
| + | </dict> | ||
| + | </plist>== ===== Level 5 Headline ===== | ||
| + | ''====== Code Text ====== | ||
| + | [[http://www.example.com|External Link]]'' == | ||
| - | Most SSH-1 clients use a standard format for storing private keys on disk. WinSCP uses this format as well; so if you have generated an SSH-1 private key using OpenSSH or ssh.com's client, you can use it with WinSCP, and vice versa. | ||
| - | |||
| - | However, SSH-2 private keys have no standard format. OpenSSH and ssh.com have different formats, and WinSCP's is different again. So a key generated with one client cannot immediately be used with another. | ||
| - | |||
| - | Using the //Import// command from the //Conversions// menu, PuTTYgen can load SSH-2 private keys in OpenSSH's format and ssh.com's format. Once you have loaded one of these key types, you can then save it back out as a PuTTY-format key (''*.PPK'') so that you can use it with the WinSCP. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change the key comment before you save the key, since OpenSSH's SSH-2 key format contains no space for a comment and ssh.com's default comment format is long and verbose. | ||
| - | |||
| - | PuTTYgen can also export private keys in OpenSSH format and in ssh.com format. To do so, select one of the //Export// options from the //Conversions// menu. Exporting a key works exactly like [[#saving_private|saving it]] - you need to have typed your passphrase in beforehand, and you will be warned if you are about to save a key without a passphrase. | ||
| - | |||
| - | Note that since only SSH-2 keys come in different formats, the export options are not available if you have generated an SSH-1 key. ((&puttydoccite)) | ||