Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Linux Magazine - Missing Anything?

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 70 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here



     ssh-keyconvert [-a] [-o output_file] authorization_file ...


     ssh-keyconvert converts RSA public and private keys used for public key
     based user authentication with protocol version 1 to the format used with
     protocol version 2.

     When using RSA user authentication with SSH protocol version 1, the
     client uses the private key from $HOME/.ssh/identity to provide its iden­
     tity to the server. The server grants or denies access based on whether
     the public part of this key is listed in $HOME/.ssh/authorized_keys.

     SSH protocol version 2 supports both DSA and RSA keys, but the way RSA
     keys are stored are differently. On the client, the default file name is
     .ssh/id_rsa rather than .ssh/identity, and the file's format is different
     as well. On the server, the public porting of the key can still be stored
     in .ssh/authorized_keys, but the key notation has changed as well.
     Therefore, when switching from protocol version 1 to version 2, you
     either have to create a new identity key using ssh-keygen(1) and add that
     key to the server's authorized_keys file, or you need to convert your
     keys using ssh-keyconvert.

     By default, ssh-keyconvert will try to guess the type of file that is to
     be converted.  If it fails to guess correctly, you can tell if what type
     of conversion to perform by specifying the -k option to convert the pri­
     vate key, or the -a option to convert an authorisation file.

     When converting your private keys stored in .ssh/identity, ssh-keyconvert
     will read the private key, prompting you for the pass phrase if the key
     is protected by a pass phrase. If the -o option is given, it will write
     the private key to the specified file, using version 2 syntax. If the key
     was protected by a pass phrase, it will use the same pass phrase to pro­
     tect the new file.  It will also write the public portion of the key to a
     second file, using the specified file name with ``.pub'' appended.  If
     the -o option was not given, private and public key will be written to
     id_rsa and id_rsa.pub, respectively, relative to the directory of the
     input key file.

     If the destination file already exists, ssh-keyconvert will prompt the
     user for confirmation before overwriting the file, unless the -f option
     is given.

     When converting your authorized_keys file, ssh-keyconvert will ignore any
     keys in SSH version 2 format. Any public keys in version 1 format will be
     converted and appended to the output file using the new syntax. If the -o
     option is given, keys are appended to the specified file. If it is not
     given, ssh-keyconvert will append all keys to the input file.

     Note that ssh-keyconvert does not check for duplicate keys, so if you run
     it on .ssh/authorized_keys more several times, the converted keys will
     show up several times.

     -f      When converting a key file, and the output file already exists,
             ssh-keyconvert will ask the user whether to overwrite the file.
             Using this option forces overwriting.


     OpenSSH is a derivative of the original and free ssh 1.2.12 release by
     Tatu Ylonen.  Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, Theo
     de Raadt and Dug Song removed many bugs, re-added newer features and cre­
     ated OpenSSH.  ssh-keyconvert was contributed by Olaf Kirch.


     ssh(1), ssh-add(1), ssh-agent(1), sshd(8)

     J. Galbraith and R. Thayer, SECSH Public Key File Format, draft-ietf-
     secsh-publickeyfile-01.txt, March 2001, work in progress material.

BSD                            February 2, 2002                            BSD
Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds