LFCS · Question #588
When migrating files from a Windows server A to a Samba server B with the command 'net rpc share migrate files -S A -destination=B -acls -attrs -U administrator', some files that originally belong…
The correct answer is C. force unknown acl user = yes. The force unknown acl user = yes option in smb.conf ensures that ACLs containing Windows SIDs that don't map to a known Unix user or group are mapped to a default user/group, preventing migration errors.
Question
Options
- Ause acl = yes
- Bmap group acls = yes
- Cforce unknown acl user = yes
- Dinherit acls = no
How the community answered
(32 responses)- A19% (6)
- B3% (1)
- C72% (23)
- D6% (2)
Why each option
The `force unknown acl user = yes` option in `smb.conf` ensures that ACLs containing Windows SIDs that don't map to a known Unix user or group are mapped to a default user/group, preventing migration errors.
`use acl = yes` enables ACL support, but does not specifically handle unknown SIDs or their mapping.
`map group acls = yes` deals with how group ACLs are mapped, but not how *unknown* SIDs for users or groups are handled during migration.
The `force unknown acl user = yes` parameter tells Samba to map any unresolvable Windows SID (Security Identifier) found in an ACL to the `nobody` user and `nogroup` group on the Unix side. This prevents errors when migrating files with ACLs that refer to Windows users or groups not present in the Samba server's user/group mapping database.
`inherit acls = no` controls whether new files inherit ACLs from their parent directory, which is unrelated to mapping unknown SIDs during migration.
Concept tested: Samba ACL migration and unknown SIDs
Source: https://www.samba.org/samba/docs/current/manpages/smb.conf.5.html
Topics
Community Discussion
No community discussion yet for this question.