Bug 45485 - NT_STATUS_LOGON_FAILURE if smbclient called without providing directly password
NT_STATUS_LOGON_FAILURE if smbclient called without providing directly password
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.2
Other Mac OS X 10.1
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
https://github.com/samba-team/samba/c...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-05 09:57 CEST by Michel Smidt
Modified: 2020-07-03 20:54 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017092921000403, 2017112721000135
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Smidt 2017-10-05 09:57:21 CEST
The customer reported this regression during an actual upgrade from 4.1-X to 4.2-2-latest.

It seems that since errata 165 the smbclient doesn't ask for the passwort anymore. I can reproduce this issue.

Actual behaviour:
# smbclient //localhost/benutzer2 -Ubenutzer2%univention
Domain=[SAML] OS=[] Server=[]        
smb: \>

# smbclient //localhost/benutzer2 -Ubenutzer2              
session setup failed: NT_STATUS_LOGON_FAILURE

Former behaviour:
# smbclient //localhost/benutzer2 -Ubenutzer2
Enter benutzer2's password:
Comment 1 Arvid Requate univentionstaff 2017-10-17 18:30:27 CEST
Indeed, it behaves as if --no-pass was default now. I can confirm, with erratalevel 159 it still asked for a password.
Comment 2 Felix Botner univentionstaff 2017-11-27 11:00:00 CET
also applies to rpcclient
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:54:27 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.