Bug 2034800
| Summary: | 4.10.16-17 regression for idmap_nss due to missing patch | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Rik Theys <rik.theys> |
| Component: | samba | Assignee: | Andreas Schneider <asn> |
| Status: | CLOSED ERRATA | QA Contact: | Denis Karpelevich <dkarpele> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.9 | CC: | aboscatt, asn, classe_it_group, dkarpele, gdeschner, jarrpa, jreznik, nsuryawa, sebastian.maennling, trondham |
| Target Milestone: | rc | Keywords: | Patch, Regression, Triaged, ZStream |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | samba-4.10.16-18.el7_9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-31 16:55:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rik Theys
2021-12-22 08:04:32 UTC
We're having the same issue. Even the addition of a username map script doesn't make Samba work properly. We have been forced to downgrade the Samba packages, which is unfortunate given the security issue. (In reply to Trond H. Amundsen from comment #3) > We're having the same issue. Even the addition of a username map script > doesn't make Samba work properly. We have been forced to downgrade the Samba > packages, which is unfortunate given the security issue. I've tried with the username map script and it seems to work here. You do have to make sure the script has the bin_t SELinux label otherwise smbd is not allowed to execute it. Maybe that's your issue with the script? Regards, Rik we're facing similar issues. at least authentication does not work anymore with version 4.10.16-17. by downgrading the packages authentication succeeds. our setup is an AD joined samba server used with kerberos authentication on client side. log shows the following: ``` [2021/12/22 11:46:39.731990, 3] ../../lib/util/access.c:365(allow_access) Allowed connection from xx.xx.xx.xx (xx.xx.xx.xx) [2021/12/22 11:46:39.732227, 3] ../../source3/smbd/oplock.c:1422(init_oplocks) init_oplocks: initializing messages. [2021/12/22 11:46:39.732467, 3] ../../source3/smbd/process.c:1948(process_smb) Transaction 0 of length 250 (0 toread) [2021/12/22 11:46:39.732742, 3] ../../source3/smbd/smb2_negprot.c:293(smbd_smb2_request_process_negprot) Selected protocol SMB3_11 [2021/12/22 11:46:40.061199, 0] ../../source3/auth/auth_generic.c:127(auth3_generate_session_info_pac) auth3_generate_session_info_pac: winbindd not running - but required as domain member: NT_STATUS_NO_LOGON_SERVERS [2021/12/22 11:46:40.061344, 3] ../../source3/smbd/smb2_server.c:3213(smbd_smb2_request_error_ex) smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NO_LOGON_SERVERS] || at ../../source3/smbd/smb2_sesssetup.c:146 [2021/12/22 11:46:40.064967, 3] ../../source3/smbd/server_exit.c:236(exit_server_common) Server exit (NT_STATUS_END_OF_FILE) ``` Regards, Sebastian (In reply to Rik Theys from comment #4) > (In reply to Trond H. Amundsen from comment #3) > > We're having the same issue. Even the addition of a username map script > > doesn't make Samba work properly. We have been forced to downgrade the Samba > > packages, which is unfortunate given the security issue. > > I've tried with the username map script and it seems to work here. You do > have to make sure the script has the bin_t SELinux label otherwise smbd is > not allowed to execute it. Maybe that's your issue with the script? That's not the issue unfortunately. We put the script under /usr/libexec/samba where it automatically gets the correct label (bin_t according to policy). With the script in place, it somehow works but not for all users. In particular, Windows users could not mount their home directory. We traced this to an issue with file permissions. We could reproduce this with smbclient, when the permission of the home dir was 700. In summary: * 4.10.16-17.el7_9 without username map script: Doesn't work at all, Samba doesn't authenticate the user (NT_STATUS_LOGON_FAILURE) * 4.10.16-17.el7_9 with username map script: No access to files with permissions 700, or ls on the dir (NT_STATUS_ACCESS_DENIED listing \*) * 4.10.16-15.el7_9 with username map script: same as above * 4.10.16-15.el7_9 without username map script: Everything works -trond Hi Trond, (In reply to Trond H. Amundsen from comment #6) > (In reply to Rik Theys from comment #4) > > (In reply to Trond H. Amundsen from comment #3) > > > We're having the same issue. Even the addition of a username map script > > > doesn't make Samba work properly. We have been forced to downgrade the Samba > > > packages, which is unfortunate given the security issue. > > > > I've tried with the username map script and it seems to work here. You do > > have to make sure the script has the bin_t SELinux label otherwise smbd is > > not allowed to execute it. Maybe that's your issue with the script? > > That's not the issue unfortunately. We put the script under > /usr/libexec/samba where it automatically gets the correct label (bin_t > according to policy). With the script in place, it somehow works but not for > all users. In particular, Windows users could not mount their home > directory. We traced this to an issue with file permissions. We could > reproduce this with smbclient, when the permission of the home dir was 700. You are correct: you can authenticate using the map script, but directories with 0700 are not accessible. Regards, Rik *** Bug 2041047 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Critical: samba security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0328 |