Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Connecting with SMB signing now enabled
Previously, the badlock security flaw fixes caused a regression. This prevented users from connecting from Windows server 2012 servers to the Samba suite without disabling the server message block (SMB) signing. With this update, it is possible to connect with SMB signing enabled and the users of Windows server 2012 can connect to samba without problems.
Description of problem:
Unable to connect windows server 2012 servers to samba with out disabling SMB signing.
Registry :
HKLM\System\CurrentControlSet\Services\LanManServer\Parameters\RequireSecuritySignature
Samba is not authenticating against AD.
The user coming from Windows to samba is NOT configured and user nobody as guest should be the used at the end to write or read on the filesystem
With "RequireSecuritySignature=0" the anon access is working like expected.
As soon, as I set "RequireSecuritySignature=1" it is not working any more.
Version-Release number of selected component (if applicable):
Rhel 6.8
windows server 2012
samba-3.6.23-36
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Customers current configuration :
grep -v ^# etc/samba/smb.conf
[global]
workgroup = MYGROUP
server string = Samba Server Version %v
map to guest = bad User
guest account = nobody
netbios name = rchsat01
log level = 9
max log size = 0
log file = /var/log/samba/log.%m
security = user
passdb backend = tdbsam
#server signing = auto
load printers = yes
cups options = raw
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = no
writable = no
printable = yes
[Builds_sat01]
path = /Builds
browseable = yes
guest ok = yes
writable = yes
public = yes
create mask = 0777
force create mode = 0777
directory mask = 0777
However this is still failing with the error attached.
I tried to reproduce the issue in-house but I could not. It continued to work with and without security signing on windows server 2012.
I will upload the debug logs and the screensshots we received from the customer.
Comment 11Andreas Schneider
2017-11-15 12:55:14 UTC
*** Bug 1495448 has been marked as a duplicate of this bug. ***
Comment 12Andreas Schneider
2017-11-15 13:16:14 UTC
= Reproducer =
== smb.conf ==
[global]
map to guest = Bad user
[testshare]
path = /foo
guest ok = yes
== smbclient ==
smbclient //SERVER/testshare -U% --signing=required
Comment 17Andreas Schneider
2017-12-14 12:58:30 UTC
Looking at the log from comment #16, smbd failed to start or update correctly. Or smbd was alredy running and the customer tried to start another instance.
Hello ASN,
Got update from customer after running test-packs:
Freshly installed rhel6.4
[rhel-6.4-Have-test-pack-installed] Windows-7-Client
RequireSecuritySignature = 0
<--------Access share------------ Can access[ok]
RequireSecuritySignature = 1
<--------Access share------------ Cannot access[FAIL]
The account is not authorized to log in from this station
Thanks
Amit
Please Ignore Comment#19:
This is correct one:
[rhel-6.4-Have-test-pack-installed] Windows-2012-Client
RequireSecuritySignature = 0
<--------Access share------------ Can access[ok]
RequireSecuritySignature = 1
....Cannot Not test....
[rhel-6.4-Have-test-pack-installed] smbclient
# smbclient //<ip>/share -U% --signing=required
smb>
Can access[ok]
# smbclient //<ip>/share -U% --signing=auto
smb>
Can access[ok]
[rhel-6.4-Have-test-pack-installed] Windows-7-Client
RequireSecuritySignature = 0
<--------Access share------------ Can access[ok]
RequireSecuritySignature = 1
<--------Access share------------ Cannot access[FAIL]
The account is not authorized to log in from this station
Thanks
Amit
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, 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-2018:1860
Description of problem: Unable to connect windows server 2012 servers to samba with out disabling SMB signing. Registry : HKLM\System\CurrentControlSet\Services\LanManServer\Parameters\RequireSecuritySignature Samba is not authenticating against AD. The user coming from Windows to samba is NOT configured and user nobody as guest should be the used at the end to write or read on the filesystem With "RequireSecuritySignature=0" the anon access is working like expected. As soon, as I set "RequireSecuritySignature=1" it is not working any more. Version-Release number of selected component (if applicable): Rhel 6.8 windows server 2012 samba-3.6.23-36 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Customers current configuration : grep -v ^# etc/samba/smb.conf [global] workgroup = MYGROUP server string = Samba Server Version %v map to guest = bad User guest account = nobody netbios name = rchsat01 log level = 9 max log size = 0 log file = /var/log/samba/log.%m security = user passdb backend = tdbsam #server signing = auto load printers = yes cups options = raw [homes] comment = Home Directories browseable = no writable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes [Builds_sat01] path = /Builds browseable = yes guest ok = yes writable = yes public = yes create mask = 0777 force create mode = 0777 directory mask = 0777 However this is still failing with the error attached. I tried to reproduce the issue in-house but I could not. It continued to work with and without security signing on windows server 2012. I will upload the debug logs and the screensshots we received from the customer.