Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #227005 > unrolled thread

cron consolekit pam_ck_connector.so: no such file

Started byBeco <rcb@beco.cc>
First post2020-09-15 16:30 +0200
Last post2020-09-15 21:00 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.debian.user


Contents

  cron consolekit pam_ck_connector.so: no such file Beco <rcb@beco.cc> - 2020-09-15 16:30 +0200
    Re: cron consolekit pam_ck_connector.so: no such file Reco <recoverym4n@enotuniq.net> - 2020-09-15 16:40 +0200
      Re: cron consolekit pam_ck_connector.so: no such file Beco <rcb@beco.cc> - 2020-09-15 21:00 +0200

#227005 — cron consolekit pam_ck_connector.so: no such file

FromBeco <rcb@beco.cc>
Date2020-09-15 16:30 +0200
Subjectcron consolekit pam_ck_connector.so: no such file
Message-ID<APk81-8oy-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Dear debians,

Is this pam module deprecated? I can't find the package that provides it on
debian buster.

And I get a lot of logs:

CRON: PAM adding faulty module: pam_ck_connector.so
SSHD: PAM adding faulty module: pam_ck_connector.so
unable to dlopen(pam_ck_connector.so): /lib/security/pam_ck_connector.so:
cannot open shared object file: No such file or directory


What is the correct secure approach? Should I just remove the optional
session line from PAM config?

I can't even find consolekit for buster.

Maybe this is old news (gentoo reports no activity on this since 2017), but
I'm only reading about it now.

Thanks in advance.


-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Essa mensagem é destinada exclusivamente ao seu destinatário e pode conter
informações confidenciais, protegidas por sigilo profissional, direitos
autorais reservados, ou cuja divulgação seja proibida por lei. O uso não
autorizado de tais informações é proibido e está sujeito às penalidades
cabíveis.

This message is intended exclusively for its addressee and may contain
information that is confidential and protected by a professional privilege,
reserved copyright, or whose disclosure is prohibited by law. Unauthorized
use of such information is prohibited and subject to applicable penalties.

[toc] | [next] | [standalone]


#227006

FromReco <recoverym4n@enotuniq.net>
Date2020-09-15 16:40 +0200
Message-ID<APkhH-8rD-11@gated-at.bofh.it>
In reply to#227005
	Hi.

On Tue, Sep 15, 2020 at 11:19:39AM -0300, Beco wrote:
> Is this pam module deprecated?

Yes, it was removed from main archive back in 2018 - [1].

> I can't find the package that provides it on
> debian buster.

There's no package in buster that provides the PAM module or ConsoleKit
itself, see above.

> What is the correct secure approach? Should I just remove the optional
> session line from PAM config?

Strictly speaking, deinstallation of "libpam-ck-connector" (I'm assuming
it was installed on this system at some point) should have done that.
But no package is bug-free, and ConsoleKit was not the best package in
this regard.

So, removing offending lines from the PAM configuration is the best
course of action.

Reco

[1] https://tracker.debian.org/pkg/consolekit

[toc] | [prev] | [next] | [standalone]


#227012

FromBeco <rcb@beco.cc>
Date2020-09-15 21:00 +0200
Message-ID<APolk-2lB-3@gated-at.bofh.it>
In reply to#227006

[Multipart message — attachments visible in raw view] — view raw

Thanks Reco,

I don't know how you keep up after all these years seen you here on the
debian list.

Congrats.

Beco.





On Tue, 15 Sep 2020 at 11:36, Reco <recoverym4n@enotuniq.net> wrote:

>         Hi.
>
> On Tue, Sep 15, 2020 at 11:19:39AM -0300, Beco wrote:
> > Is this pam module deprecated?
>
> Yes, it was removed from main archive back in 2018 - [1].
>
> > I can't find the package that provides it on
> > debian buster.
>
> There's no package in buster that provides the PAM module or ConsoleKit
> itself, see above.
>
> > What is the correct secure approach? Should I just remove the optional
> > session line from PAM config?
>
> Strictly speaking, deinstallation of "libpam-ck-connector" (I'm assuming
> it was installed on this system at some point) should have done that.
> But no package is bug-free, and ConsoleKit was not the best package in
> this regard.
>
> So, removing offending lines from the PAM configuration is the best
> course of action.
>
> Reco
>
> [1] https://tracker.debian.org/pkg/consolekit
>
>

-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Essa mensagem é destinada exclusivamente ao seu destinatário e pode conter
informações confidenciais, protegidas por sigilo profissional, direitos
autorais reservados, ou cuja divulgação seja proibida por lei. O uso não
autorizado de tais informações é proibido e está sujeito às penalidades
cabíveis.

This message is intended exclusively for its addressee and may contain
information that is confidential and protected by a professional privilege,
reserved copyright, or whose disclosure is prohibited by law. Unauthorized
use of such information is prohibited and subject to applicable penalties.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web