[MDEV-7637] MariaDB 5.5 + pam + ldap + selinux Created: 2015-02-26 Updated: 2015-04-28 Resolved: 2015-04-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation, Plugin - pam |
| Affects Version/s: | 5.5.42, 10.0 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Eringa | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ldap, pam, selinux, verified | ||
| Environment: |
Centos 6.6 x86_64 |
||
| Description |
|
rpms involved
MariaDB
I've created the user in MariaDB and loaded the auth module with
And a valid /etc/pam_ldap.conf If I use setenforce Permissive all is well, I can log in as the user authenticated via the ldap AD. I've verified that the selinux permissions on the /etc/pam.d/mariadb appear to be valid Cheers Jan. |
| Comments |
| Comment by Elena Stepanova [ 2015-03-01 ] | ||
|
I can reproduce it.
Then I added policies to allow this. It helped to get rid of the error messages, but now connection just fails with Enforcing without any trace in audit logs at all, and works with Permissive. I installed latest system upgrades, but it didn't help. I also tried CentOS 7 to see if it works there, but couldn't get this far – it seems there was a bug related to PAM/LDAP, not to SELinux, and the fix hasn't been released yet. So, I didn't dig deep enough there, but at the first glance, if it weren't for that other bug, there would be the same problem with Enforcing/Permissive. serg, | ||
| Comment by Jan Eringa [ 2015-03-12 ] | ||
|
Guys ... any news / updates on this ? Cheers Jan. | ||
| Comment by Sergei Golubchik [ 2015-03-12 ] | ||
|
Not yet. Please wait till the next 5.5 release | ||
| Comment by Sergei Golubchik [ 2015-04-27 ] | ||
|
elenst, where is that image? Is it your local one or somewhere where I can boot it? | ||
| Comment by Elena Stepanova [ 2015-04-27 ] | ||
|
It was a local one, under VM Virtual Box. | ||
| Comment by Sergei Golubchik [ 2015-04-27 ] | ||
|
in your setup mysqld needs to access "netlink_audit_socket" and your default policy doesn't allow it. you need to enable that in your policy. The most helpful instruction that I've found was this one: CentOS * SELinux, PAM and MySQL. In short:
| ||
| Comment by Sergei Golubchik [ 2015-04-27 ] | ||
|
Documented in KB. | ||
| Comment by Daniel Black [ 2015-04-28 ] | ||
|
looks like RHEL might be coming out with a selinux update to fix this sometime: https://bugzilla.redhat.com/show_bug.cgi?id=1201413 | ||
| Comment by Sergei Golubchik [ 2015-04-28 ] | ||
|
Thanks! I've subscribed to it to know when it's fixed. |