Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Mar 2020 11:37:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 244844] Cron does not support PAM sessions
Message-ID:  <bug-244844-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244844

            Bug ID: 244844
           Summary: Cron does not support PAM sessions
           Product: Base System
           Version: 12.1-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: kevin@lyda.ie

Some distributions of Linux have configured and activated pam_env[0] from t=
he
LinuxPAM project. The OpenPAM project lacks this module but it's easy enoug=
h to
write.  It sets environment variables for an authenticated session from a f=
ile
named /etc/environment by default.

A similar module for OpenPAM works just fine for ssh and several other case=
s,
but not for cron.  Checking the diff between do_command.c in FreeBSD cron[1]
and the current Vixie cron[2], it's clear that the pam_open_session and
pam_close_session calls are missing in FreeBSD cron.

Would there be any interest in patches to fix this?

[0] http://www.linux-pam.org/Linux-PAM-html/sag-pam_env.html
[1]
https://github.com/freebsd/freebsd/blob/master/usr.sbin/cron/cron/do_comman=
d.c
[2] https://github.com/svagner/vixie-cron/blob/master/do_command.c

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244844-227>