Re: [systemd-devel] The whole su/pkexec session debate

2013-12-10 Thread Martin Pitt
Lennart Poettering [2013-12-11 3:17 +0100]: > I am pretty sure that screen should not get the right to escape here. > [..] > The kill-on-logout thing really is something that explicitly should > kill screen too, otherwise it would not be so useful. Not only "not so useful", it would be rendered e

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-10 Thread Martin Pitt
Lennart Poettering [2013-12-11 3:11 +0100]: > I used to believe that screen should set up a new session, but I don't > think so anymore. > > Nowadays think they should do exactly what they currently do: fork and > stay around. This will cause the session to stay in "closing" state when > the user

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-10 Thread Lennart Poettering
On Mon, 02.12.13 10:00, Colin Guthrie (gm...@colin.guthr.ie) wrote: > > 'Twas brillig, and Martin Pitt at 02/12/13 05:48 did gyre and gimble: > >> > This way, screen will keep an "active" reference to the session and > >> > systemd-logind will not mark it as "closing". > > > > But that screen pro

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-10 Thread Lennart Poettering
On Sun, 01.12.13 16:57, David Herrmann (dh.herrm...@gmail.com) wrote: > > Hi > > >>> But in the case of screen I'm specifically asking for a new, stand alone > >>> session. > >> > >> I'd agree; but the fix would be fairly invasive for screen. I think > >> it'd have to become setuid root, so it

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-10 Thread Lennart Poettering
On Wed, 20.11.13 09:49, Colin Walters (walt...@verbum.org) wrote: > > On Wed, 2013-11-20 at 10:16 +, Colin Guthrie wrote: > > > How do we fix this? > > There are a lot of cases - "screen" is just one of them. I think to > make forward progress on this we'll have to enumerate the cases, > e

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-10 Thread Lennart Poettering
On Wed, 20.11.13 10:16, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Hi, > > One other thing occurred this morning while pondering the latest patches > from Martin and Colin on this topic. > > What should (in an ideal world) apps like screen do? I used to believe that screen should set up a ne

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-05 Thread David Herrmann
Hi On Mon, Dec 2, 2013 at 8:17 PM, Colin Walters wrote: > On Mon, 2013-12-02 at 14:37 +0100, David Herrmann wrote: > >> But then gnome-session should simply call ReleaseSession() on the bus >> itself.. > > I'd rather have some sort of API where a particular process is the > "session leader", and

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-02 Thread Colin Walters
On Mon, 2013-12-02 at 14:37 +0100, David Herrmann wrote: > But then gnome-session should simply call ReleaseSession() on the bus itself.. I'd rather have some sort of API where a particular process is the "session leader", and its exit implies closing. Something like a pid file in /run/systemd/s

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-02 Thread David Herrmann
Hi On Mon, Dec 2, 2013 at 11:00 AM, Colin Guthrie wrote: > 'Twas brillig, and Martin Pitt at 02/12/13 05:48 did gyre and gimble: >>> > This way, screen will keep an "active" reference to the session and >>> > systemd-logind will not mark it as "closing". >> >> But that screen process would still

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-02 Thread Colin Guthrie
'Twas brillig, and Martin Pitt at 02/12/13 05:48 did gyre and gimble: >> > This way, screen will keep an "active" reference to the session and >> > systemd-logind will not mark it as "closing". > > But that screen process would still be running in the user's logind > session cgroup, so logind can s

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-01 Thread Martin Pitt
David Herrmann [2013-12-01 16:57 +0100]: > Screen can be fixed to call: > pam_start(&pamh) > pam_open_session(pamh) > > and during shutdown: > pam_close_session(pamh) > pam_end(pamh) Please not; screen has no business interfering with the PAM stack, it does not start login sessions by its

Re: [systemd-devel] The whole su/pkexec session debate

2013-12-01 Thread David Herrmann
Hi >>> But in the case of screen I'm specifically asking for a new, stand alone >>> session. >> >> I'd agree; but the fix would be fairly invasive for screen. I think >> it'd have to become setuid root, so it could request a new session. > > Yeah that was my fear too. > > Although perhaps this is

Re: [systemd-devel] The whole su/pkexec session debate

2013-11-20 Thread Colin Guthrie
Hi! 'Twas brillig, and Colin Walters at 20/11/13 14:49 did gyre and gimble: > On Wed, 2013-11-20 at 10:16 +, Colin Guthrie wrote: > >> How do we fix this? > > There are a lot of cases - "screen" is just one of them. I think to > make forward progress on this we'll have to enumerate the case

Re: [systemd-devel] The whole su/pkexec session debate

2013-11-20 Thread Colin Walters
On Wed, 2013-11-20 at 10:16 +, Colin Guthrie wrote: > How do we fix this? There are a lot of cases - "screen" is just one of them. I think to make forward progress on this we'll have to enumerate the cases, evaluate the problems with each, then for each problem, evaluate a fix - and make sur

[systemd-devel] The whole su/pkexec session debate

2013-11-20 Thread Colin Guthrie
Hi, One other thing occurred this morning while pondering the latest patches from Martin and Colin on this topic. What should (in an ideal world) apps like screen do? I have a screen session on my server running a little python irc bot. I ssh in to the server, start screen, start my bot, detatc