rlogin

[abcd7]

Hi,

I have 2 HP IA systems. I could do rlogin b/w them as root.

Howerver, when I try to do rlogin from one user of system A to another user of system B, it is asking for password.

Those user ID's do not exists on the other systems.

My .rhosts entry reads like this

On Sys A




On Sys B



Thanks in Advance

Doug

[Tim Nelson]

users must exist on both systems.

If not then just about anyone could log in and what would be the need of having any form of security.

BTW, trusting system to system authentication is anti-security.

[abcd7]

Hi,

As per the man page, .rhosts should work, even if the user doesn't exist locally. I want to try this out. Doesn't it work, at all?


Regards

Doug

[Steven Schweda]

This would all be clearer if you stopped
trying to hide all the useful details. To
a (this) casual reader, the difference, if
any, between "" and "user name>" is not immediately obvious. Nor
is it clear (to me) what "My" or "local"
means in this situation.

Which user accounts exist where?

What, exactly, is in each user's ".rhosts"
file?

Ownership and permissions on those ".rhosts"
files and the home directories ("ls -l"
output)?

[Rasheed Tamton]

Hi,

It should work with different user if you put the hostname and the username correctly in the destination .rhosts file.

But as mentioned above, the main culprit might be the permission of the .rhosts file or the dir of the user. If you are testing and you do the test as root most probably the owner of those is still root.

Just change the permissions and it should work.

Regards,
Rasheed Tamton

[Jeeshan]

you must have to have .rhosts file in all users home dorectory along with its user name.

[SUDHAKAR_18]

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1212487593404+28353475&threadId=1210256

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1212487796091+28353475&threadId=356231

Hope This Helps.

[abcd7]

Hi,

I do have the required entries..

Let me explain it in detail.


Sys A : users A & C

Sys B : users B & C

User A doesn't exist on Sys B

User B doesn't exist on Sys A

when I enable rlogin for user C, it works without asking for a password.

when I enable b/w users A & B, it asks for a password. Moreover it doesnt accept the password. I have to key in the username & the password..



Thanks

Doug

[Steven Schweda]

> Let me explain it in detail.

Who's stopping you? When can we expect this
detailed explanation to begin?

> when I enable b/w users A & B, it asks for
> a password.

How, exactly, do you "enable b/w users
A & B"? ("b/w"? Black and white?)

What, exactly, are you doing when "it asks
for a password"?

See earlier questions for requests for more
missing details.

[abcd7]

Sorry about the confusion.


B/W : Between

Added entries in the .rhosts file.

SYS A : ~A/.rhosts

+ B

SYS B : ~B/.rhosts

+ A

I tried replacing "+" with the FQDN / short names / host names that I see when I telnet from A to B under 'who -um'. No use.



It works without a password when I try using user C.

SYS A : ~C/.rhosts

+ C

SYS B : ~C/.rhosts

+ C

Was succesfull even if I use FQDN or shortnames of the hosts in place of "+" for user C

When it asks for a password, I enter the password. Not accpeted. Goes for login retry. Gives me a nornal login prompt, like telnet / ssh. Accepts username & password, like any other system & login method.

[Patrick Wallek]

When doing a remsh are you using the syntax 'remsh host -l '?

In your case if from SYSA

# remsh sysb -l b

[abcd7]

It says "remshd: Login incorrect."

[Dennis Handly]

>when I try to do rlogin from one user of system A to another user of system B, it is asking for password.

I had no problem. I assume you are using from A in SYSA:
rlogin SYSB -l B

>Added entries in the .rhosts file.
>SYS A : ~A/.rhosts
>SYS B : ~B/.rhosts

Can you do "ll" on these two files so we can check ownership and permissions.

> I tried replacing "+" with the FQDN / short names / host names

I just used my short name. Have you tried using the IP address?

>Accepts username & password, like any other system & login method.

It's almost as if it has the wrong user name.
Can you look at lastb(1) to see what user had a bad login and what the password was.

[abcd7]

when I explictly specify username with option -l, rlogin & remsh are working from Sys A.

Sys B is still asking for a password.

The Perms of ~/.rhosts 600

I tried with IP, FQDN / Short name & "+". No luck.

[abcd7]

when I look at the lastb output, user B tops System A & user A tops System B.

As you are aware, user B doesn't exist on System A & vice versa.

[Dennis Handly]

>when I explicitly specify username with option -l, rlogin & remsh are working from Sys A.

Why are you using the word "when" here? You MUST use "-l username" when changing users. I.e. If you are A on SYSA, you tell rlogin you want be B on SYSB.
It then looks in ~B/.rhosts and finds "A" is allowed from SYSA.

Also, what is "working from Sys A"?

Do you have the lastb(1) data?

[abcd7]

Thanks Dennis !!!

When I use -l, r commands are working without a password from System A.

Sys B is still prompting for a password.


I cant disclose the hostname & usernames, as per our org policy..

[Dennis Handly]

>when I look at the lastb output, user B tops System A & user A tops System B.
>As you are aware, user B doesn't exist on System A & vice versa.

That's why you must use "-l other-username", even if A & B existed on both machines.
That's what Patrick and I have been telling you.

>When I use -l, r commands are working without a password from System A.

From A to B?

>Sys B is still prompting for a password.

From B to B or B to A or what?

>I cant disclose the hostname & usernames, as per our org policy..

(I missed your translated reply.)

For more details, you could use: lastb -R -x

[abcd7]

Thank U very much.

I could do rlogin without a password, from both the machines.


"-l" did the trick.



Thankz once again to you all.

[Steven Schweda]

> "-l" did the trick.

Actually revealing (at long last, like
pulling teeth) what you were doing had a lot
to do with it.

[abcd7]

We had DNS changes happening around the same time, which compounded my problems..

anyway, "all is well that ends well"

Good Day / Good Night to you wherever you are.


Cheers

Doug

[abcd7]

Thanks to all.

[Steven Schweda]

> 0 pts

You're breaking my heart.

Now, ask yourself what would have happened if
you had included in your first posting your
actual "rlogin" command, which might/must
have looked something like this:

rlogin sys_B_Name

where, you apparently expected system B to
intuit which user name you wanted it to use,
instead of something like this:

rlogin -l user_B sys_B_Name

along, of course, with the info about which
users existed where, where you were when you
gave that command, and all those other
missing details.

Now try to estimate how much time of how many
people was wasted chasing wild geese because
of all the useful information about this
problem which you failed to provide until it
was eventually dragged out.

Please try to keep in mind this example of
how not to pose a question the next time you
have a question.

[Dennis Handly]

>Steven: instead of something like this:
> rlogin -l user_B sys_B_Name

Or more like this: :-)
rlogin sys_B_Name -l user_B