uirements are generally pretty simple: its used to
> > > > > > > associate a context with a login shell.
> > > > > > >
> > > > > > > With systemd things have becomes a bit more complicated.
> > > > > > >
> >
ext with a login shell.
> > > > > >
> > > > > > With systemd things have becomes a bit more complicated.
> > > > > >
> > > > > > systemd uses pam_selinux to associate a context with both a login
> > > > > >
; > > On Thu, 2017-09-07 at 11:05 +0200, Dominick Grift wrote:
> > > > > pam_selinux requirements are generally pretty simple: its used to
> > > > > associate a context with a login shell.
> > > > >
> > > > > With systemd things have
> pam_selinux requirements are generally pretty simple: its used to
> > > > associate a context with a login shell.
> > > >
> > > > With systemd things have becomes a bit more complicated.
> > > >
> > > > systemd uses pam_selinux to
t; > associate a context with a login shell.
> > >
> > > With systemd things have becomes a bit more complicated.
> > >
> > > systemd uses pam_selinux to associate a context with both a login
> > > shell (via container-shell@.service) as well as with a syst
ngs have becomes a bit more complicated.
> >
> > systemd uses pam_selinux to associate a context with both a login
> > shell (via container-shell@.service) as well as with a systemd --user
> > instance.
> >
> > Ideally one would not associate a login shell cont
On Thu, 2017-09-07 at 11:05 +0200, Dominick Grift wrote:
> pam_selinux requirements are generally pretty simple: its used to
> associate a context with a login shell.
>
> With systemd things have becomes a bit more complicated.
>
> systemd uses pam_selinux to associate a
pam_selinux requirements are generally pretty simple: its used to associate a
context with a login shell.
With systemd things have becomes a bit more complicated.
systemd uses pam_selinux to associate a context with both a login shell (via
container-shell@.service) as well as with a systemd
