03-28-2012
Help!! trying to connect to linux SSH from windows putty client
Hi,
i am trying to connect my Putty session on a windows box to a linux SSH, i have generated private and public key pairs using puttygen, i have set the public one to be in an OPENSSH format... and have put this in my authorized_keys file in linux, when i connect i get the following errors:
Server refused our key,
and then a popup window that says...
Disconnected: no supported authentication methods available (server sent: publickey,gssapi-with-mic)
any ideas what this could be?
***
managed to find a reason for this...
by looking at /var/log/secure it said that the directory previous to the .ssh directory had the wrong permissions...
so /home/.ssh was 700
but /home was 777 :S
so i changed /home to 700 and then this worked OK
thanks for all the views!
Last edited by Jtyreman; 03-28-2012 at 12:01 PM..
10 More Discussions You Might Find Interesting
1. AIX
Hi Everybody,
I have 2 Servers (AIX 4.3), recently I installed SSH in both servers successfuly. I can connect from one server to another using SSH. My problem is when I tried to connect from Windows workstation to one of these servers the connection timed out. I'm using PUTTY to connect to the... (12 Replies)
Discussion started by: aldowsary
12 Replies
2. Red Hat
Friends,
I have installed Putty in my windows xp pc. I am connecting the RHEL
AS 3 server using putty from my windows xp. My printer is connected to
my windows xp.
Now, i want to print text.txt of RHEL AS 3.0 in my windows xp printer
through putty.
For Example:
my pc ip is 117.23.2.55... (3 Replies)
Discussion started by: sathyguy
3 Replies
3. Windows & DOS: Issues & Discussions
Dear All ,
I want to Access my office computer form the home.
The enviourment is like the following :
1- From my home I connect for the office via VPN connection to Unix server lets say it's IP is 11.11.11.11 and till now every thing is OK and I can access the machine normally .
2- In my... (3 Replies)
Discussion started by: habuzahra
3 Replies
4. Red Hat
Is there any Better FREE SSH client similar to Secure CRT ?
We are working on cluster db servers. PROD/DEV/UAT/QA/TEST server hostnames are just one letter differences. it always confuse me to which one I am logging in.
So I am looking for a free SSH client, for windows where I can store... (4 Replies)
Discussion started by: johnveslin
4 Replies
5. AIX
I am a new user and i wish to connect to a unix(AIX) server from a windows client using ssh.A detailed solution would be highly appreciated. (1 Reply)
Discussion started by: ajayb3004
1 Replies
6. What is on Your Mind?
I am curious about the most popular ssh client on Windows environment. Talking about me, I use PuTTY most of the time coupled with WinSCP to transfer files. But, I like Tera Term too. It has great drag-drop feature where you can drag a file/folder and drop on the window and it will transfer the... (14 Replies)
Discussion started by: admin_xor
14 Replies
7. Shell Programming and Scripting
I am trying to connect to Windows server via Linux server through a script and run two commands " cd and ls " But its giving me error saying " could not start the program" followed by the command name i specify e g : "cd"
i am trying in this manner "
ssh username@servername "cd... (5 Replies)
Discussion started by: sunil seelam
5 Replies
8. UNIX for Advanced & Expert Users
Hi,
I am facing problems whie trying to do a passwordless ssh to Unix box from windows. Public key was generated using F-secure. When the F-secure client attempts it connects without password but when I try to use sftp2 in command line it prompts for password.
I have tried several options and... (0 Replies)
Discussion started by: dhrajj
0 Replies
9. Linux
Hi,
I am facing problems whie trying to do a passwordless ssh to Unix box from windows. Public key was generated using F-secure. When the F-secure client attempts it connects without password but when I try to use sftp2 in command line it prompts for password.
I have tried several options and... (3 Replies)
Discussion started by: dhrajj
3 Replies
10. Windows & DOS: Issues & Discussions
I ssh from Windows to Linux server and execute a few commands. I have ssh keys setup between them and works fine.
The commands get executed on the Linux server however I wish to stay on the Linux terminal that was opened by putty.exe. However, the terminal simply does the job and closes.
... (10 Replies)
Discussion started by: mohtashims
10 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