Control: affects -1 =
Control: reassign -1 xterm 261-1
Control: tags -1 moreinfo
On 2019-10-05 11:28 +0200, Christian Göttsche wrote:
> Am Sa., 5. Okt. 2019 um 07:59 Uhr schrieb Sven Joachim <svenj...@gmx.de>:
>>
>> Control: reassign -1 libutempter0
>> Control: affects -1 xterm screen tmux
>>
>> On 2011-01-29 17:02 -0500, Jeffrey Sheinberg wrote:
>>
>> > Package: xterm
>> > Version: 261-1
>> > Severity: normal
>> >
>> > Hi,
>> >
>> > First of all, please note that I currently have xterm Version: 235-2
>> > installed.
>> >
>> > With xterm Version: 261-1 installed, when I run this command,
>> >
>> > $ exec login USER
>> >
>> > the xterm immediately exits. This problem does not occur with prior
>> > versions of xterm installed, eg, Version: 235-2.
>>
>> The reason is that starting with version 247-1 xterm is no longer setgid
>> but uses libutemper to update /var/run/utmp. The same behavior can be
>> seen in screen and tmux which also terminate immediately upon
>> "exec login USER".
>
> I do not quite understand the problem.
> Yes, xterm exits when running 'exec login USER' as non-root.
> That is because 'login USER' fails as non-root and 'exec' exits on failure.
> Test 'exec /bin/false'.
Err, of course, sorry for the noise. I should have had more coffee this
morning and read the bug report more carefully. The bug submitter had a
suid /bin/login, but even after "chmod 4755 /bin/login" I cannot use
that to actually login:
,----
| $ LANG=C exec login sven
| No utmp entry. You must exec "login" from the lowest level "sh"
`----
And this happens even at the Linux console, so libutempter is out of the
question. Running login as root with 'exec su -c "login sven"' succeeds,
though (with a double password prompt from su and login).
Reassigning back to xterm for now, but I don't see xterm doing anything
wrong. And it is definitely not going back to setgid utmp.
Cheers,
Sven
