Bug 1497162

Summary: smbcacls fails if no password is specified
Product: Red Hat Enterprise Linux 7 Reporter: Marc Muehlfeld <mmuehlfe>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED ERRATA QA Contact: Andrej Dzilský <adzilsky>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.4CC: adzilsky, aheverle, asn, gdeschner, jarrpa, rhack
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: samba-4.7.0-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 17:30:15 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 Marc Muehlfeld 2017-09-29 10:57:28 UTC 
Problem description:
If you run an smbcacls command without specifying the password in the -U parameter, the command fails and prints:
> cli_full_connection failed! (NT_STATUS_LOGON_FAILURE)
instead of asking for the password such as other tool do (e. g. "net" or "samba-tool").



Version-Release number of selected component (if applicable):
samba-client-4.6.2-11.el7_4.x86_64



Steps to reproduce:
1. Run:
   # smbcacls //server/share / -Uadministrator
   cli_full_connection failed! (NT_STATUS_LOGON_FAILURE)



Further details:
* The command works if you add the password to the -U parameter. For example:
  # smbcacls //server/share / -Uadministrator%password
  But this should not be the recommended way.
* Connections also work if you have a valid Kerberos ticket and pass the
  -k option to the command



Additional info:
This bug has been fixed upstream:
https://bugzilla.samba.org/show_bug.cgi?id=12765
Comment 3 Andrej Dzilský 2017-10-27 17:02:26 UTC 
Verified. Smbcacls now prompts user for password if no password was used.
Comment 9 errata-xmlrpc 2018-04-10 17:30:15 UTC 
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/RHBA-2018:0937