From: Evgeny Bushkov <zhen@dotcomltd.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where is pam_ldap now?
Date: Wed, 13 Nov 2024 18:34:08 +0300 [thread overview]
Message-ID: <08474539-c5a9-471c-aa24-c5e0505f424b@dotcomltd.ru> (raw)
In-Reply-To: <14082891.RDIVbhacDa@rogueboard>
On 13.11.2024 18:14, Michael wrote:
> On Wednesday 13 November 2024 15:12:06 GMT Eli Schwartz wrote:
>> On 11/13/24 8:48 AM, Evgeny Bushkov wrote:
>>> Hi ,
>>>
>>> somehow my ldap user became blocked from access to a ssh-server. It
>>> turns out pam can't find pam_ldap.so module anymore. Yes I remember I
>>> removed it at recent 'emerge --depclean' session but the portage tree
>>> doesn't have it anymore. I wonder where is sys-auth/pam_ldap now?
>>> There's no mentioning in news nor in web search. I managed to restore
>>> pam_ldap module from packages but now I'm in need for more reliable
>>> decision.
>> pam_ldap was masked and last rited on August 8, and deleted from
>>
>> ::gentoo on September 13. It wouldn't have been in the news.
>>
>> Here is the announcement:
>>
>> https://public-inbox.gentoo.org/gentoo-dev-announce/7f786219-b478-46b2-ab5c-> d2a805727063@gentoo.org/
>>
>> The recommended replacement was nss-pam-ldapd.
>>
>> You can keep using pam_ldap if you prefer, from a local overlay.
> The wiki suggests 'sys-auth/sssd' as a more recent alternative:
>
> https://wiki.gentoo.org/wiki/
> Centralized_authentication_using_OpenLDAP#Configuring_SSSD
>
> https://packages.gentoo.org/packages/sys-auth/sssd
Thanks! I'll take a look at manuals and choose sssd or nss-pam-ldapd for
substitution of pam_ldap.
prev parent reply other threads:[~2024-11-13 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 13:48 [gentoo-user] where is pam_ldap now? Evgeny Bushkov
2024-11-13 15:12 ` Eli Schwartz
2024-11-13 15:14 ` Michael
2024-11-13 15:25 ` Eli Schwartz
2024-11-13 15:34 ` Evgeny Bushkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08474539-c5a9-471c-aa24-c5e0505f424b@dotcomltd.ru \
--to=zhen@dotcomltd.ru \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox