Date: Thu, 22 Mar 2001 12:50:27 -0500 (EST) From: Robert Watson <rwatson@freebsd.org> To: Larry Librettez <lipshitz909@yahoo.com> Cc: freebsd-qa@freebsd.org, freebsd-questions@freebsd.org Subject: Re: 4.3-BETA won't su to root in X terminal Message-ID: <Pine.NEB.3.96L.1010322124643.11543C-101000@fledge.watson.org> In-Reply-To: <20010322165331.97337.qmail@web13208.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1727467116-985283427=:11543 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 --0-1727467116-985283427=:11543 Content-Type: APPLICATION/octet-stream; name="test.tgz" Content-Transfer-Encoding: BASE64 Content-ID: <Pine.NEB.3.96L.1010322125027.11543D@fledge.watson.org> Content-Description: test.tgz H4sIAGI6ujoAA+2W32vbMBDH82r/FUdGi90mjZ3YCTTtYDAoe+hWVsoGbQnG llUx1zaSnFFG//fph5M6Wbf1Yele7gOxdLrT6SvrZCKJkKPeboEomMUx9ABg GoemhXBsW0sAMBvH02gSh8FUOYPZNOhBvGNdhkbIhAP0+PdEiqr8bZwKy/PX EPS6SH3+58k3krOC7GiNMAimUfSH859NOucfaWcUT3oQ7EjPBnj+8hj08yh1 HZqmMPySFAUMKzO48qQFScpj1+H3MMzNoOv+b+nIP8Dcf3vIO1vjL/d/HE7H 6/sfTGbaOQ4ivP+vwRtWpkWTETgRD2KkfgW7Z1Ic3b11N13yoSZmuDsuM1Zt hjYlU6MmbnTgwgFccFZKqBoJy4SzqhGQiJqkUkClPiR3BNKGc6JCal6lRAhI OcmUzZICkjLTKTgpEkkyELLJ8yM1MnJVTvc+YaWnkyecpgNI79Q5Hqj+8vrW d3+ojxnLFhIor5paXH88+/zp6uJycf7u6+185eOqGQAxT7FUjfI01tMYT2M9 jfHYBYqKslJZemGmQjiv+Nx1nVrvM/f6NcuOb+RedlPWnS7lddvtD4ASqVye b3u26zr6KmhbhXq+P3/KKNZpVrPViLdKokNdx8iAU+3kRCi93r7dwr7dw77Z hM7KcvBMtA/qHTm16Xv99cS+DnI4kQ0vwRuG2nzsbG+h87Z6Ur54MuqFWaMr 9Ze3+IxWarRSq5W2WukLtNKXaKVdrXRDK93Sul0L21ptIXmdQhq0xbUhFU5P QSnZFmwjnxf8pFiJLG2klSa16pXdb6tNT8rVQh5TwsI5MDhpyxDY4aGv123T wV7WX4m8ZrfdojK79ruFe7G4vDr78L77TpgQSio1ZaZDTe3bt2G6XjejGdGz hZlrTO131/sNlPmIfxsQBEEQBEEQBEEQBEEQBEEQBEEQZGf8BAoxz1oAKAAA --0-1727467116-985283427=:11543-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010322124643.11543C-101000>