Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Mar 2001 11:07:44 -0800 (PST)
From:      Larry Librettez <lipshitz909@yahoo.com>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        freebsd-qa@freebsd.org, freebsd-questions@freebsd.org
Subject:   Re: 4.3-BETA won't su to root in X terminal
Message-ID:  <20010322190744.65221.qmail@web13203.mail.yahoo.com>
In-Reply-To: <Pine.NEB.3.96L.1010322124643.11543C-101000@fledge.watson.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
Here are the outputs, appropriately named.  I
concatenated the output for an rxvt window to the
'xterm' file. I hope this is helpful.


--- Robert Watson <rwatson@freebsd.org> wrote:
> 
> On Thu, 22 Mar 2001, Larry Librettez wrote:
> 
> > This also is strange - from within X (4.3-RC
> kernel + 4.3-RC userland),
> > if I start gnome-terminal, I CAN su to root in
> that terminal window.  If
> > I start xterm or rxvt, I cannot.  However, if I
> start rxvt or xterm from
> > WITHIN a gnome-terminal as regular user (i.e. 
> 'rxvt &' or 'xterm &'), I
> > CAN su to root from within that rxvt or xterm! 
> Strange! 
> 
> As I mentioned in my prior e-mail, it sounds like
> something about the
> credential/context of the shell is getting botched,
> resulting (for reasons
> unknown) in a failure of su.  I've written up a
> quick program that prints
> out the accessible process credential information to
> the terminal by
> calling a variety of get*() system calls.  If
> possible, I'd like to get
> you to run this in three different scenarios, saving
> the output to
> appropriately named files :-).  These would be the:
> at the shell prompt on
> the console prior to su, in an xterm prior to su,
> and in a gnome-terminal
> prior to su.  Then e-mail them back and we can take
> a look.  I've attached
> the program in source form as a tarball, just:
> 
>    tar -xzf test.tgz
>    cd test
>    make
> 
> And invoke as
> 
>    ./test
> 
> There are a couple of other aspects that may be
> relevant here, relating to
> Kerberos interference if you are running on a box
> where kerberos got
> installed due to a bug in sysinstall.  If the
> credential output doesn't
> give us any clues, we can follow up on that, and
> terminal-related issues. 
> 
> Thanks!
> 
> Robert N M Watson             FreeBSD Core Team,
> TrustedBSD Project
> robert@fledge.watson.org      NAI Labs, Safeport
> Network Services
> 
> 

> ATTACHMENT part 2 application/octet-stream
name=test.tgz





__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/
[-- Attachment #2 --]
pid:	306
ppid:	278
pgrp:	306
sid:	278

p_ruid:	1001
cr_uid:	1001
p_svuid:	1001

p_rgid:	1001
cr_gid:	1001
p_svgid:	1001

cr_ngroups:	4	cr_groups:	 1001 0 69

P_SUGID:	0

login:	earth

[-- Attachment #3 --]
pid:	375
ppid:	374
pgrp:	375
sid:	374

p_ruid:	1001
cr_uid:	1001
p_svuid:	1001

p_rgid:	1001
cr_gid:	1001
p_svgid:	1001

cr_ngroups:	4	cr_groups:	 1001 0 69

P_SUGID:	0

login:	earth

[-- Attachment #4 --]
[xterm]
pid:	391
ppid:	389
pgrp:	391
sid:	389

p_ruid:	1001
cr_uid:	1001
p_svuid:	1001

p_rgid:	1001
cr_gid:	1001
p_svgid:	1001

cr_ngroups:	4	cr_groups:	 1001 0 69

P_SUGID:	0

login:	earth

[rxvt]
pid:	386
ppid:	385
pgrp:	386
sid:	385

p_ruid:	1001
cr_uid:	1001
p_svuid:	1001

p_rgid:	1001
cr_gid:	1001
p_svgid:	1001

cr_ngroups:	4	cr_groups:	 1001 0 69

P_SUGID:	0

login:	earth
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010322190744.65221.qmail>