Yves-Alexis,
On Sat, Oct 22, 2022 at 01:59:33PM +0200, Yves-Alexis Perez wrote:
> But if it seems that there is no breakage (and hopefully no bad side effects
> we don't see yet) I guess we'll be able to update the pam configuration to
> uses includes as well at some point.
A gentle reminder
> "Yves-Alexis" == Yves-Alexis Perez writes:
Yves-Alexis> I'm not sure other display managers handle the greeters
Yves-Alexis> the same way (running under their own uid and stuff
Yves-Alexis> like that), so I'm unsure if we can really compare
Yves-Alexis> that.
gdm does.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2022-10-16 at 11:49 +0100, Mark Hindley wrote:
> > My suspicion is that since this appears to be working for other display
> > managers, it's all fine.
>
> It seems that way to me as well.
I'm not sure other display managers handle the
Sam,
Thanks for this, very helpful.
I have again tested both approaches and they both work and I can find no
breakage.
On Tue, Oct 11, 2022 at 03:30:12PM -0600, Sam Hartman wrote:
> I think we want something there that allows people to get third-party
> packages into the pam config.
> If
> "Yves-Alexis" == Yves-Alexis Perez writes:
I think we want something there that allows people to get third-party
packages into the pam config.
If common-session isn't going to be good enough, then I guess we'd need
to create something on the PAM side.
But let's explore whether
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2022-10-11 at 10:02 -0600, Sam Hartman wrote:
> If including common-session will work, I think that's a good improvement
> for everyone.
> It is closer to best practice, and it means that as PAM profiles are
> added over time, they will work
Hi.
If including common-session will work, I think that's a good improvement
for everyone.
It is closer to best practice, and it means that as PAM profiles are
added over time, they will work for lightdm as well.
Whether that works depends on the architecture of the greeter.
If the greeter has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2022-10-09 at 13:22 +0100, Mark Hindley wrote:
> > It might be nice to have them chime in. Also not sure how this thing is
> > handled on other DM, any idea?
>
> A quick look shows most use '@include common-session'. AFAICS that is the
>
Yves-Alexis,
On Sun, Oct 09, 2022 at 01:46:56PM +0200, Yves-Alexis Perez wrote:
> for some reason it seems I never actually replied to this bug, sorry.
No worries.
> I might have replied on different bugs, but I'm not really keen on modifying
> pam files, especially for specific / non-default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2022-10-09 at 10:03 +0100, Mark Hindley wrote:
> Hi Yves-Alexis,
>
> With another user bumping into this issue, I am keen to have it resolved in
> bookworm.
>
> I think adding
>
> session optional pam_elogind.so
>
> to
Hi Yves-Alexis,
With another user bumping into this issue, I am keen to have it resolved in
bookworm.
I think adding
session optional pam_elogind.so
to /etc/pam.d/lighdm-greeter is the best and correct fix.
I know you have been reluctant in the past, but would you consider it again.
Hey there,
I highly agree with Mark on this suggestion, since I ran into the exact
same problem after the installation of an alternative init system on
Debian Bullseye via the chroot method using d-i (first sysvinit, then
OpenRC). After adding the proposed line to /etc/pam.d/lightdm-greeter
(and
Hello,
Just a gentle nudge on this.
On Sun, 14 Jul 2019 12:59:32 +0100 Mark Hindley wrote:
> Patches implementing both of these approaches are attached.
I would be grateful if you could adopt one or other of these so that they can be
more widely tested well in advance of the freeze.
Thanks
Package: lightdm
Severity: normal
Tags: patch
Yves-Alexis,
Many thanks for updating lightdm's dependencies to use the new logind virtual
packages in closing #922160.
However, the necessary adjustments to the PAM configuration for lightdm-greeter
are still outstanding.
My testing indicates that
14 matches
Mail list logo
