Bug 13671 - lookupsids S-1-22-2-0 returns NT_STATUS_INVALID_SID instead of NT_STATUS_NONE_MAPPED
Summary: lookupsids S-1-22-2-0 returns NT_STATUS_INVALID_SID instead of NT_STATUS_NONE...
Status: RESOLVED DUPLICATE of bug 14213
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.9.1
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-01 16:11 UTC by Björn Baumbach
Modified: 2020-02-10 10:15 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Baumbach 2018-11-01 16:11:03 UTC 
With Samba 4.8 and newer the lookup of a unknown SID returns NT_STATUS_INVALID_SID, here running again Samba AD 4.9.1:

# rpcclient -c "lookupsids S-1-22-2-0"
result was NT_STATUS_INVALID_SID

The expected behavior is NT_STATUS_NONE_MAPPED, here running against Samba AD 4.7:
# rpcclient -c "lookupsids S-1-22-2-0"
S-1-22-2-0 *unknown*\*unknown* (8)

Additional note:
The NT_STATUS_INVALID_SID leads to a crash of the ACL editor of my Windows 7 version. So it seems to be very unexpected.
Comment 1 Björn Baumbach 2019-08-06 07:01:18 UTC 
Additional additional note:
Recently I've seen that the issue leads to a crash of the Windows 10 ACL editor, too.
Comment 2 Roel van Meer 2020-02-07 08:04:39 UTC 
May be a duplicate of bug 14213
Comment 3 Björn Baumbach 2020-02-10 10:15:23 UTC 
(In reply to Roel van Meer from comment #2)
Yes, thanks!
Arvid reported the same bug there. I close this one, because the other report already contains more information.

*** This bug has been marked as a duplicate of bug 14213 ***