Since not so long time, also ext3 (2?) supports ACLs. They're (as you tell) however build on different IDs. But this is a problem which also occours between different linux installations. Until you strictly use equal UIDs and GIDs. WinNT/ROS does also just use GIDs/UIDs. They're however GUIDs. Thus a simple workaround would be a flag for the SAM to just use 16-bit IDs or an option to manually specify an ID.
BTW. GUIDs in NTLM are organized as [32Bit-Domaincontrolerspecific][32-Bit User/GroupID with speciall bits]
Andrew "Silver Blade" Greenwood wrote:
Just to chime in here... Something I've thought about recently regarding file systems...
I believe there was going to be an ext2 driver in ReactOS. Am I right in thinking that complications arise because of the different ways in which security is implemented for different operating systems? And thus if you use ext2 from Windows or NTFS from Linux, you essentially have unrestricted access to all files (non-encrypted, of course.)
One possible solution might be to provide some sort of GROUPS and PASSWD "emulation" in ReactOS for each user account, so when NTFS is being used, the NT style security descriptors are used, whereas when ext2 is used, the Linux style is used. I'm assuming here of course that Linux uses the group and user IDs for the security info - I could be wrong. Still fairly new to Linux.
The actual emulation implementation wouldn't be too difficult as it'd just be a case of storing the Linux GID and UID for a user - something which should be possible. Maybe the ext2 driver would be responsible for converting the NT security descriptor into a Linux one? Or maybe a common module (linuxids.dll or something?) could perform this conversion.
I'm probably dreaming away here as if it was THAT easy, surely it would have been done already huh?