Thanks all for the answers! However, it still doesn't work for some reason. I've added the link to authorized_keys2 and I've rebuild the keys (am now using rsa keys). I've checked the sshd_config file and I've checked the permissions and all, but still I get the same error:
I even get the error when trying to ssh to itself:
I've tried it on 3 servers already and everywhere I get the same result.
i keep getting the following error with the code segment below when i try to compile the program.
The code is from 'defs.h'
parse error before '('
parse error before ')'
stray '\' in program
this is the code segment and the error is on the second line of the segment
#define... (1 Reply)
HI, I just installed NetBSD i386 v. latest. I am having a few problems: For some reason X just won't start!? Another is I can't access My CDROM or Floppy.
Thanks in advance! (3 Replies)
Hi Guys,
I am trying to compare using if, but keep getting some strange results.
if ; then
keeps creating the file 1
if ; then
does not work at all
if ; then
does not work
if ; then
does not work
if ; then
does not work eihter.
I am using a ksh, on Solaris (9 Replies)
Hello
I created an application in c language for HP-UX operative system,and it runs on a 32 bits PARISC processor. My problem is that I have to run this same application but now in a 64 bits Parisc processor. But I am not able to compile the application with the 64 bit server, and I only could use... (1 Reply)
I'm trying to set up a secure and trusted connection between 2 boxes running solaris using ssh2.
I've run ssh-keygen2 on the local box and on the remote box, created the identification file ( IdKey id_dsa_2048_a ) on the local machine and copied across the public key file from the local to... (5 Replies)
I have a cronjob that I need to run everyday and it needs to have todays date inputed, here is what I have, but is not working as expected..........
23 02 * * * cd /path;./RequestSummaryReport.sh $(date +%Y-%m-%d)
the output from mail gives me.............
Date: Fri, 8 Feb 2008 02:12:07... (4 Replies)
Hello All
I have a set of files, each one containing some lines that follows that regex:
regex='disabled\,.*\,\".*\"'and here is what file says about each files:
file <random file>
<random file> ASCII text, with CRLF line terminatorsSo, as an example, here is what a file ("Daffy Duck - The... (3 Replies)
I am aware this question has been answered time and again. I feel I have tried everything I have seen on the net and really need help to get this working.
Same old story. Shell script, working from command but not from cron. I need my script to take values from a .properties file. Tried... (2 Replies)
What I have here is a pretty textbook recursive function. Its purpose right now is simply to display all folders that don't contain folders.
It works fine in all instances I can think of... except one. If there is a folder with a space in its name, the thing goes Kablooie.
AFAIK the problem comes... (5 Replies)
I am trying to make all the fields containing lower case letters upper case and the third field of a file display ** instead.
I have this:
awk '{printf "%s %s ** %d %d\n", $1, $2, $4, $5}' database.txt | tr '' '' < database.txt
And that only changes it to upper case, other... (4 Replies)
Discussion started by: Bungkai
4 Replies
LEARN ABOUT SUSE
ssh-keyconverter
SSH-KEYCONVER(1) BSD General Commands Manual SSH-KEYCONVER(1)NAME
ssh-keyconvert -- convert ssh v1 keys and authorization files
SYNOPSIS
ssh-keyconvert [-k] [-o output_file] identity_file ...
ssh-keyconvert [-a] [-o output_file] authorization_file ...
DESCRIPTION
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 con-
vert 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 private 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 protect 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.
OPTIONS -k Convert private key file(s). The default is to guess the type of file that should be converted.
-a Convert authorized_keys file(s). The default is to guess the type of file that should be converted.
-o outfile
Specify the name of the output file. When converting an authorization file, all public keys will be appended to this file. For pri-
vate key conversion, the private and public components of the key will be stored in outfile and outfile.pub, respectively. Note that
since every key must be stored in a separate file, you cannot use this option when you specify several input files.
-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.
AUTHORS
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 created OpenSSH. ssh-keyconvert was contributed by Olaf Kirch.
SEE ALSO 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