passwordless login issue with ssh keys Post: 302479716

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

failed ssh login with keys

Hi all, i have generated a pair of keys so that i can login via SSH without entering my password. I am using putty to login. After putting the public key on the server,then logging through putty, i get the message "Server refused our key" on screen. At the same time, /var/log/secure is...

2. Solaris

ssh login issue after patching

Hi Everybody, Recently i applied patch cluster dated (2009.11.03) for solaris 10 sparc machine(Generic_138888-06) I successfully applied and rebooted the machine , no errors received. But after patching it was not allowing me to login through ssh while telnet was working fine.Logs showed me ...

3. HP-UX

Unable To Perform A "Passwordless" SSH Login To A Server

Greetings! I am trying to perform a passwordless SSH login from a HPUX 11.31 client to a HPUX 11.31 server. Whenever I do a "ssh -l root serverA" from the client, I am prompted for a password. Giving the password, I am able to successfully login. However I am trying to accomplish a...

4. Shell Programming and Scripting

issue while auto login using .ssh for HPUX

Hi, While trying to supress password prompt using ssh. I have added .ssh folder manually and generated public key and added to authorized_keys file in the remote machine. But still it's prompting for passwords with the following message: Permission denied...

5. Emergency UNIX and Linux Support

SSH password login issue

Hi All, I am facing issue in setting up passwordless login through ssh on two Solaris-10 boxes. user-id ravrwa from server tsapiq04-zrwdq01 should be able to login to server tsbrit03 as cpsuserq, which is not happening. I am not sure where is the problem, while keys are already all set. Here is...

6. UNIX for Advanced & Expert Users

Intermitent issue with passwordless login

Hi, I have two users login on my HPUX i.e user1 and user2. Inorder to switch from user1 to user2 without password I generated key pair using keygen command for user id user1 and copied the its public key to the .ssh/authorized_keys file of user2. ssh-keygen -b 2048 -t rsa This...

7. Solaris

[solved] Ssh passwordless login not working

This is Solaris 10 and sorce+destination are non root user. Somehow it is broke and I am not able to fix it. Already checked permissions on both servers and authorized_keys entry of destination is same as id_rsa.pub of source server. I can not regenerate keys on source server because I do not know,...

8. Shell Programming and Scripting

Expect script ssh passwordless login

how can i use an expect script to do a passwordless ssh login and run a script on a bunch of remote hosts? I do not want to use public key authentication as this would require me to setup the keys on the clients etc....

9. Red Hat

SSH login issue

Dear All , recently i have configured sftp for a user for which i have done chroot. but after this , sftp is working fine . but ssh is not working when we connect to the server. When we try to ssh <user>@<server ip> , the below is the error message that we get and not able to login. ...

LEARN ABOUT HPUX

hp9000s200

machid(1)						      General Commands Manual							 machid(1)

NAME

       machid: hp9000s200, hp9000s300, hp9000s400, hp9000s500, hp9000s700, hp9000s800, hp-mc680x0, hp-pa, pdp11, u370, u3b, u3b10, u3b2, u3b5, vax
       - provide truth value about processor type

SYNOPSIS

DESCRIPTION

       The following commands return a true value (exit code 0) if the a processor type matches the command name.  Otherwise a false  value  (exit
       code  nonzero)  is returned.  These commands are commonly used within makefiles and shell procedures to improve portability of applications
       (see make(1)).

				       +-----------+-------------------------++--------+--------------------------+
				       |Command    | True for		     ||Command | True for		  |
				       +-----------+-------------------------++--------+--------------------------+
				       |hp9000s200 | Series 200 	     ||pdp11   | PDP-11/45 or PDP-11/70   |
				       |hp9000s300 | Series 300 	     ||u3b     | 3B20 computer		  |
				       |hp9000s400 | Series 400 	     ||u3b2    | 3B2 computer		  |
				       |hp9000s500 | Series 500 	     ||u3b5    | 3B5 computer		  |
				       |hp9000s700 | Series 700 	     ||u3b10   | 3B10 computer		  |
				       |hp9000s800 | Series 800 or 700	     ||u370    | IBM System/370 computer  |
				       |hp-mc680x0 | Series 200, 300, or 400 ||vax     | VAX-11/750 or VAX-11/780 |
				       |hp-pa	   | Series 700 or 800	     ||        |			  |
				       +-----------+-------------------------++--------+--------------------------+
EXAMPLES

       Given a shell script that must behave differently when run on an HP 9000 Series 700 or 800 system, select the correct code  segment  to	be
       executed:

WARNINGS

       always  returns	true on both Series 800 and Series 700 systems.  Therefore, when using this command in scripts to determine hardware type,
       always use both and in the appropriate sequence to ensure correct results (see

       machid(1) will no longer provide support for future machines beyond the Series 800 and Series 700 systems.  Decisions should  be  based	on
       the hardware and software configuration information returned by getconf(1).

SEE ALSO

       getconf(1), make(1), sh(1), test(1), true(1).

																	 machid(1)