* Using libpam with systemd but without systemd-logind
@ 2018-10-26 15:24 Matt Spinler
2018-10-27 10:36 ` Peter Kjellerstedt
0 siblings, 1 reply; 4+ messages in thread
From: Matt Spinler @ 2018-10-26 15:24 UTC (permalink / raw)
To: openembedded-devel
Hi,
Our embedded system uses systemd and libpam, but doesn't use systemd's
logind package.
The libpam recipe,
https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-extended/pam/libpam_1.3.0.bb#L149,
will add pam_systemd.so to common-session if it detects systemd is used.
However, systemd will only even build pam_systemd.so if the logind
package is enabled, shown here:
https://github.com/systemd/systemd/blob/15b1180945f2cfa0f7938626ff060c8b52606a1a/meson.build#L1747
So in our case, since we are explicitly disabling logind, pam will
complain
in the journal about not being able to find pam_systemd.so.
As logind isn't a systemd distro feature, I'm not sure how libpam can
really know
that it doesn't need to add pam_systemd.so to common-session?
Does anyone have any ideas on ways to handle this?
Thanks,
Matt
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [oe] Using libpam with systemd but without systemd-logind
2018-10-26 15:24 Using libpam with systemd but without systemd-logind Matt Spinler
@ 2018-10-27 10:36 ` Peter Kjellerstedt
0 siblings, 0 replies; 4+ messages in thread
From: Peter Kjellerstedt @ 2018-10-27 10:36 UTC (permalink / raw)
To: Matt Spinler, OE Core (openembedded-core@lists.openembedded.org)
[ This discussion really belongs on the openembedded-core mailing list
since it concerns libpam and systemd, both of which are part of OE-Core,
so that is where I am responding. However, I have kept openembeded-devel
as bcc: to inform of this move. ]
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org <openembedded-
> devel-bounces@lists.openembedded.org> On Behalf Of Matt Spinler
> Sent: den 26 oktober 2018 17:25
> To: openembedded-devel@lists.openembedded.org
> Subject: [oe] Using libpam with systemd but without systemd-logind
>
> Hi,
>
> Our embedded system uses systemd and libpam, but doesn't use systemd's
> logind package.
>
> The libpam recipe,
> https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-extended/pam/libpam_1.3.0.bb#L149,
> will add pam_systemd.so to common-session if it detects systemd is
> used.
>
> However, systemd will only even build pam_systemd.so if the logind
> package is enabled, shown here:
> https://github.com/systemd/systemd/blob/15b1180945f2cfa0f7938626ff060c8b52606a1a/meson.build#L1747
>
> So in our case, since we are explicitly disabling logind, pam will
> complain in the journal about not being able to find pam_systemd.so.
>
> As logind isn't a systemd distro feature, I'm not sure how libpam can
> really know that it doesn't need to add pam_systemd.so to common-session?
>
> Does anyone have any ideas on ways to handle this?
>
> Thanks,
> Matt
I am by no means any PAM expert, but prefixing the line inserted into
/etc/pam.d/common-session with a '-' should make libpam not output
anything to the logs if pam_systemd.so does not exist.
//Peter
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using libpam with systemd but without systemd-logind
@ 2018-10-27 10:36 ` Peter Kjellerstedt
0 siblings, 0 replies; 4+ messages in thread
From: Peter Kjellerstedt @ 2018-10-27 10:36 UTC (permalink / raw)
To: Matt Spinler, OE Core (openembedded-core@lists.openembedded.org)
[ This discussion really belongs on the openembedded-core mailing list
since it concerns libpam and systemd, both of which are part of OE-Core,
so that is where I am responding. However, I have kept openembeded-devel
as bcc: to inform of this move. ]
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org <openembedded-
> devel-bounces@lists.openembedded.org> On Behalf Of Matt Spinler
> Sent: den 26 oktober 2018 17:25
> To: openembedded-devel@lists.openembedded.org
> Subject: [oe] Using libpam with systemd but without systemd-logind
>
> Hi,
>
> Our embedded system uses systemd and libpam, but doesn't use systemd's
> logind package.
>
> The libpam recipe,
> https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-extended/pam/libpam_1.3.0.bb#L149,
> will add pam_systemd.so to common-session if it detects systemd is
> used.
>
> However, systemd will only even build pam_systemd.so if the logind
> package is enabled, shown here:
> https://github.com/systemd/systemd/blob/15b1180945f2cfa0f7938626ff060c8b52606a1a/meson.build#L1747
>
> So in our case, since we are explicitly disabling logind, pam will
> complain in the journal about not being able to find pam_systemd.so.
>
> As logind isn't a systemd distro feature, I'm not sure how libpam can
> really know that it doesn't need to add pam_systemd.so to common-session?
>
> Does anyone have any ideas on ways to handle this?
>
> Thanks,
> Matt
I am by no means any PAM expert, but prefixing the line inserted into
/etc/pam.d/common-session with a '-' should make libpam not output
anything to the logs if pam_systemd.so does not exist.
//Peter
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [oe] Using libpam with systemd but without systemd-logind
2018-10-27 10:36 ` Peter Kjellerstedt
(?)
@ 2018-10-28 8:40 ` Richard Purdie
-1 siblings, 0 replies; 4+ messages in thread
From: Richard Purdie @ 2018-10-28 8:40 UTC (permalink / raw)
To: Peter Kjellerstedt, Matt Spinler,
OE Core (openembedded-core@lists.openembedded.org)
On Sat, 2018-10-27 at 10:36 +0000, Peter Kjellerstedt wrote:
>
> > Our embedded system uses systemd and libpam, but doesn't use
> > systemd's logind package.
> >
> > The libpam recipe,
> >
https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-extended/pam/libpam_1.3.0.bb#L149
> > ,
> > will add pam_systemd.so to common-session if it detects systemd is
> > used.
> >
> > However, systemd will only even build pam_systemd.so if the logind
> > package is enabled, shown here:
> >
https://github.com/systemd/systemd/blob/15b1180945f2cfa0f7938626ff060c8b52606a1a/meson.build#L1747
> >
> > So in our case, since we are explicitly disabling logind, pam will
> > complain in the journal about not being able to find
> > pam_systemd.so.
> >
> > As logind isn't a systemd distro feature, I'm not sure how libpam
> > can
> > really know that it doesn't need to add pam_systemd.so to common-
> > session?
> >
> > Does anyone have any ideas on ways to handle this?
>
> I am by no means any PAM expert, but prefixing the line inserted
> into
> /etc/pam.d/common-session with a '-' should make libpam not output
> anything to the logs if pam_systemd.so does not exist.
The best way I can think of is if each recipe have their own
PACKAGECONFIG entries as appropriate and then your distro configures
both recipes to do the right thing?
Cheers,
Richard
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-10-28 8:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-26 15:24 Using libpam with systemd but without systemd-logind Matt Spinler
2018-10-27 10:36 ` [oe] " Peter Kjellerstedt
2018-10-27 10:36 ` Peter Kjellerstedt
2018-10-28 8:40 ` [oe] " Richard Purdie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.