Solaris 10 permission issue?

[reinstalled]

Hi,

I have a clean install of Solaris 10 8/07
I have set up a user. I have created a directory structure
created as root but owned by that user. When I try to rcp or delete I get permission denied. This is a standard build for us although only the second using Solaris 10. All permissions look correct and I have compared them to our other Solaris 10 installation and they look the same.

Am I missing something?

Thanks,

 

[SamBones]

We'd need to know more about the userid, it's group, the directories and their permissions, the files and their permissions. You need to be a little more specific.

 

[Mike042]

When we installed Solaris 10 (Release 11/06), I seem to remember that, by default, telnet & ftp (amongst others) were 'turned off' as part of the installation. Hence 'rcp' would not work even if ~<user>/.rhosts is set up correctly.

I am not familiar with 'delete' (one of the SunOS/BSD Compatibility Library Functions).

Perhaps you could give some actual examples of the commands and their error messages (rather than just a written description). Thanks.


I hope that helps.

Mike

 

[reinstalled]

username:x:100:10:User Name:/home/user:/bin/csh

Directory permissions: drwxrwxr-x User owned and member of group

Standard build is to first uncomment /etc/default/login CONSOLE line. That enables telnet. What's more is as root I can rcp.

Thanks,

 

[elgrandeperro]

First, lets determine if the Permission Denied is a file perm problem.

Can you "remsh" a command like /bin/who?

Can you "su - username" and touch a file in their homedir?
Is /home an automount? Is the automounter on, is /home in /etc/auto_master?

I find the easiest way to debug this is to use "truss -f -p PIDOFINETED, and see why it returns EPRERM.

eugene

 

[reinstalled]

I can touch files, I can create directories. I can delete created files and directories.


auto_master: /home auto_home -nobrowse

truss gives me the following after multiple tries:
truss: cannot trace set-id or unreadable object file:

I tried as root again with success so it appears a rcp thing with the user? If so this is new on me as this a standard procedure and I didn't see this issue on my other Sol 10 installation.

 

[elgrandeperro]

You trussed as superuser? You must be superuser to truss inetd.

What about remsh? Did you try that? That would rule out the filesystem as the culprit, if it failed.

Hey, I don't think you can have a writeable group home dir for
the user for rsh to work.

eugene

 

[reinstalled]

remsh does fail.

I have to admit I have never used truss before.
So, as root I ran truss -e -f 922
What after truss is going? Am I to run commands as that user in another window? do anything?
Sorry if these seem simple questions, I want to understand what I am doing.

I did a login in another window and truss spit out a ton of lines. What am i looking for?

Thanks,

 

[elgrandeperro]

I usually run "script" in the truss window to capture output.

Did you change the group perms so it isn't group writeable?

Truss is simply spitting out the system calls that inetd and any child is doing (you can't truss the rsh daemon because it only starts via inetd, so you might be getting extraneous output if the system is totally loaded.

I think the first thing I would look at is an execv for
the rshd binary. Just look for all execs, and it should have something like in.rshd as an argument. From there, you should be able to see the pid of in.rshd, that way you can grep out the calls only from in.rshd if needed.

I believe you need to search for EACCES, and I think that will appear as that in truss.

You should be able to see the open of /etc/hosts.equiv and your .rhosts. If it doesn't get that far, it is stopping prematurely. Look for stat to see if it is checking a directory.

That being said, there is only a few reasons you get this:

I believe it checks /etc/shells for valid shells. Your password line given is /bin/csh so that isn't it.

Permissions of .rhosts or any directory between it and /.

The naming problem. The easist way to figure out the primary name of your local machine is to ssh or telnet into the remote from the local and type "who". Who should display the correct name value (on the right) that should be in .rhosts, given what you have in /etc/nsswitch.conf, /etc/hosts, /etc/resolv.conf, NIS, etc.

eugene