• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Deprecated pam_stack module called from service "proftpd"

JuanCar

Regular Pleskian
Why does this message appears in my secure log?
And ... how can I fix it?

I can find any useful answers by anywhere

Thanks
 
You don't mention which OS you are using :-(

But with thanks to users aus-city and Kalimari on the Atomic discussion forum, which is where this info comes from, try the following:

Centos 5:
FILE: /etc/pam.d/proftpd
Code:
#%PAM-1.0
session optional pam_keyinit.so force revoke
auth required pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
auth required pam_shells.so
auth include system-auth
account include system-auth
# Comment the following line if you are having PAM issues with chrooted users
#session include system-auth
session required pam_loginuid.so

Centos 6:
FILE: /etc/pam.d/proftpd

Code:
#%PAM-1.0
auth required pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
auth include system-auth
auth required pam_shells.so
account include system-auth
session required pam_loginuid.so
 
Oh, yes my OS is Centos 5
With this config all Pam messages dissapear!! Including messages about closing sesión, there is only the "login successful" message.
If uncomment
#session include system-auth

the message "pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory" appears, due to chrooted FTP user.

but the message about closing session does appear.

Thank you
 
Back
Top