Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
10.4.0-1
Description
Buggy PAM modules can currently crash the server. See MDEV-10361 for example. Should auth_pam isolate PAM modules somehow to prevent problems like this from taking down the whole server? Is it feasible for auth_pam to use sandboxes for PAM modules, or would that cripple performance and slow down authentication too much?
Attachments
Issue Links
- causes
-
MDEV-19876 pam v2: auth_pam_tool_dir and auth_pam_tool permissions are wrong in RPMs
- Closed
-
MDEV-19877 pam v2: auth_pam_tool input format is not user friendly for debugging
- Open
-
MDEV-19878 pam v2: pam password authentication doesn't work at all
- Closed
-
MDEV-19880 pam v1: pam password authentication doesn't work at all in MariaDB 10.4
- Closed
-
MDEV-19881 pam plugin from MariaDB 10.3 doesn't work with MariaDB 10.4
- Open
-
MDEV-19882 pam v2: auth_pam_tool truncates passwords that are not null-terminated
- Closed
-
MDEV-21385 PAM v2 plugin produces lots of zombie processes
- Closed
-
MDEV-22459 pam v2 should log an error if auth_pam_tool exec fails
- Closed
-
MDEV-22482 pam v2: mysql_upgrade doesn't fix the ownership/privileges of auth_pam_tool
- Open
-
MXS-2633 Pam authentication doesn't work with server 10.4
- Closed
- is blocked by
-
MDEV-7032 new pam plugin with a suid wrapper
- Closed
- relates to
-
MDEV-16813 Document PAM updates
- Open
-
MDEV-18311 Change default PAM service name to mariadb
- Open
-
MXS-3753 Add option to run PAM authentication in a suid sanbox
- Closed
-
MDEV-10361 auth_pam + RSA SecurID PAM module + SQLyog causes server crash
- Closed