Monday, August 11, 2003, 2:38:58 PM, you wrote:
>> Won't screen work without suid bit correctly? I remember that I used
>> screen without suid and it was working correctly.
> It depends on how you define "correctly" ;)
> Without suid bit set screen can't chown(2) ttys, it can't update utmp
> (type 'w' and see) and can't read system password after ^A-x (but one
> can always set password in his ~/.screenrc).
> The problem i've described in my previous mail looks for me like a bug
> in cerb's code - the policy before the last commit was working properly,
> that is degraded screen's euid to users ruid in case it has suid bit set
> and then it was giving screen some capabilities. And now we've got screen
> working as it was without any policy...
I don't know screen much, but what advantages does give screen when is
able to change owner of ttys?
I know that screen was working fine for me without suid-root.
Maybe we should create define that will allow to turn euid cheating
(and other suid-root actions) it on or off.
SCSA, SCNA, LPI, CCNA, MCP certified