Bug 14531 - LDAP object visibility not implemented completely with "List Object" mode
Summary: LDAP object visibility not implemented completely with "List Object" mode
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.13.0
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Karolin Seeger
QA Contact: Samba QA Contact
URL: https://lists.samba.org/archive/samba...
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-13 09:31 UTC by Stefan Metzmacher
Modified: 2020-11-05 10:02 UTC (History)
2 users (show)

See Also:


Attachments
Patches for v4-13-test (66.61 KB, patch)
2020-10-21 09:19 UTC, Stefan Metzmacher
dbagnall: review+
Details
Patches for v4-12-test (66.61 KB, patch)
2020-10-21 09:20 UTC, Stefan Metzmacher
dbagnall: review+
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Metzmacher 2020-10-13 09:31:55 UTC
We don't implement [MS-ADTS] 5.1.3.3.6 Checking Object Visibility
completely.

We're hiding objects, which should be visible.
Comment 1 Samba QA Contact 2020-10-21 08:49:06 UTC
This bug was referenced in samba master:

80347deb544b38be6c6814e5d1b82e48ebe83fd1
06d134406739e76b97273db3023855150dbaebbc
d2dd7c2a5c1f8ee30f0f3b41f933d082b0c75f7c
c4a3028de726d6708f57d02f9162a4d62d1b6ae7
faff8e6c89777c38443e561235073c336cfb2e9c
e1529bedb2b6c8553e69a42537ac0cffd03af6d6
ffc0bdc6d49e88da1ee408956365da163ff3e1b2
7223f6453b1b38c933c9480c637ffd06d9f39b97
Comment 2 Stefan Metzmacher 2020-10-21 09:19:39 UTC
Created attachment 16290 [details]
Patches for v4-13-test
Comment 3 Stefan Metzmacher 2020-10-21 09:20:10 UTC
Created attachment 16291 [details]
Patches for v4-12-test
Comment 4 Karolin Seeger 2020-10-26 09:55:54 UTC
Pushed to autobuild-v4-{13,12}-test.
Comment 5 Samba QA Contact 2020-10-26 14:43:14 UTC
This bug was referenced in samba v4-12-test:

62f7642b073839f38fbbb4e97f6d15f672090444
1da871f7f24a0b285ef16ebfad9eae35b60649a4
c1df795199c9e924a7214f7613e2b710e5a3ea16
f6af56ad68a416e4d8e0ee374036a6fcbe36fe91
376fd7e1c0f0191e48732297d6062e98cbf78407
6073edb8c08b14ed545abd39cf0d853686b9215e
66e64bf9a61525bd3b0eee111a9860349841fa6a
a127fb862b6f9388f788c12ab390dbf8af0270c2
Comment 6 Samba QA Contact 2020-10-27 10:51:29 UTC
This bug was referenced in samba v4-13-test:

a89a78aa609115a770113d2d23e99ad7e3172b54
f92b61ec8265f9008950eeea6200c3d38f07fbfd
540cd43baf2b761dbed17cd7e817b312cf31b96e
24e0a440a9331f676cdeabf38f307fec281c86f3
ee5b2e3be9063f787c7302100ce04fba4f5fe3f5
160a2d6a5f9e3c1b57cef26937a2de5ecb9877a4
0918966f9d5673112a913d3be2b4cb8320be6b27
b15f35b573817b0e39425ae05962a9b1028bdc32
Comment 7 Karolin Seeger 2020-10-30 12:12:00 UTC
Closing out bug report.

Thanks!
Comment 8 Samba QA Contact 2020-11-03 12:36:17 UTC
This bug was referenced in samba v4-13-stable (Release samba-4.13.2):

a89a78aa609115a770113d2d23e99ad7e3172b54
f92b61ec8265f9008950eeea6200c3d38f07fbfd
540cd43baf2b761dbed17cd7e817b312cf31b96e
24e0a440a9331f676cdeabf38f307fec281c86f3
ee5b2e3be9063f787c7302100ce04fba4f5fe3f5
160a2d6a5f9e3c1b57cef26937a2de5ecb9877a4
0918966f9d5673112a913d3be2b4cb8320be6b27
b15f35b573817b0e39425ae05962a9b1028bdc32
Comment 9 Samba QA Contact 2020-11-05 10:02:05 UTC
This bug was referenced in samba v4-12-stable (Release samba-4.12.10):

62f7642b073839f38fbbb4e97f6d15f672090444
1da871f7f24a0b285ef16ebfad9eae35b60649a4
c1df795199c9e924a7214f7613e2b710e5a3ea16
f6af56ad68a416e4d8e0ee374036a6fcbe36fe91
376fd7e1c0f0191e48732297d6062e98cbf78407
6073edb8c08b14ed545abd39cf0d853686b9215e
66e64bf9a61525bd3b0eee111a9860349841fa6a
a127fb862b6f9388f788c12ab390dbf8af0270c2