login process

[henry78]

on a 10.20 K class server, login on tty, telnet or rlogin is impossible. System ask for user name but bring back the login prompt without asking for the password.
ftp login works.
I'am looking for the different step of the logging process to find out whitch process doesn't succeed.

thanks

[Pete Randall]

I would guess that the system is having problems resolving the user's home directory. Either that or there is something illegal in a login script (.profile, .dtprofile, etc.) that is causing login to fail.


Pete

[Anshumali]

If i am right, FTP login doesn't use a shell and no profile is executed.
If thats not happening for root, you can check for the both above as your FTP works fine.
May be the shell is invalid or the profile contains something which is causing that.

Anshu

[henry78]

thanks for your ideas, It could not be a problem of profile :

The system DOESNOT prompt for a password
whenever a user is entered or just return

I would like to know what login does between
be username is entered and the password prompt is returned

[john korterman]

Hi Henry,

keep in mind that ftp does not perform a "normal" login.

In a "normal" login the /etc/init process finds an entry in /etc/inittab telling it to fork a command asking for "login:"

As you are prompted for "login:" your system apparently executes this step. However, the next step should be that the same process that was forked for the above command should then exec /bin/login, using the users's entry as parameter - this should result in the prompting for the password.

Your system seems not to be able to perform this step. There can be many reasons. Has anyone executed a chmod/chown command? Does /bin/login have these permissions:
-r-sr-xr-x 1 root bin 53248 Sep 13 2002 /bin/login


regards,
John K.

[OldSchool]

i would suspect either permissions issue on /usr/bin/login (as noted prev) or missing/corrupted /etc/password file

[Bill Hassell · Accepted solution]

Check the permissions on both the login and passwd commands as well as the passwd file. Did anyone try to 'improve' the security on your system by changing permissions? Can you login using the console (the real console using a serial cable)? If not, you'll probably have to reboot the machine using the console and ctrl-b to talk to the processor ROMs. Then interrupt the boot process when it gives you 10 seconds to do so. Boot into single user mode with hpux -is command. Then fix the permissions and boot back to multi-user mode.

If indeed some permissions were changed, you might have to check everything. Use swverify to look at everything.

[henry78]

Thanks for your help.
Using swverify I manage to point out a wrong cksum for /usr/bin/login.
This file was restored and users can log in using telnet or rlogin.
Using an Hex editor, I saw the very begining of the file ok and the rest erased.

Happy new year