So normally vmware runs setuid root, which means that the 'real' uid and gid will be the normal user, as opposed to the root user. '0x4' on FreeBSD would constitute R_OK -- a quick glance at my local Linux box demonstrates that it has the same meaning there. If you run the 'access' command with similar arguments on /home/hunter/gwk/.Xauthority, what do you get back?
An interesting experiment might be to write a short program invoking access(2) with the same arguments, compiled under both ABIs, and then experimented with and without setuid-root. A glance at the linux_access() implementation looks right to me, but maybe there's something going on relating to preserving real/saved uids/gids and the process credential. Or alternatively, maybe your .Xauthority file isn't readable :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Mon, 8 Oct 2001, Georg-W. Koltermann wrote: > No, I wan't using linux_kdump, thanks for the education. > > Today I've installed linux_kdump from the package on > jp.current.freebsd.org, and now I get > > 1207 vmware CALL linux_access(0xbfbff759,0x4) > 1207 vmware NAMI "/compat/linux/home/hunter/gwk/.Xauthority" > 1207 vmware NAMI "/home/hunter/gwk/.Xauthority" > 1207 vmware RET linux_access -1 errno 13 Permission denied > > which looks a little more meaningful (no negative errno any more, and > a linux_* syscall is listed). > > Still needs debugging, which I'll attempt to do when I get a little > time. > > -- > Regards, > Georg. > > > At Sun, 7 Oct 2001 > 19:28:35 -0400 (EDT), Robert Watson wrote: > > > > > > On Sun, 7 Oct 2001, Georg-W. Koltermann wrote: > > > > [...] > > > I ran the vmware command through ktrace(1) (had to do that as root since > > > it won't trace a SUID program for a normal user), and it does get an > > > error return from an access(2) on .Xauthority: > > > > > > 1207 vmware CALL access(0xbfbff759,0x4) > > > 1207 vmware NAMI "/compat/linux/home/hunter/gwk/.Xauthority" > > > 1207 vmware NAMI "/home/hunter/gwk/.Xauthority" > > > 1207 vmware RET access -1 errno -13 Unknown error: -13 > > > > > > It seems I am going to debug the access() call next. > > > > I'm a little surprised that they're calling access(). Are you using the > > linux_kdump from the ports collection, btw? Otherwise the system calls > > aren't listed right, due to differences in system call number. > > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > > [EMAIL PROTECTED] NAI Labs, Safeport Network Services > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
