CentOS - May 2016 - access denied from windows changing security setting when i use a folder connected to a fake drive made with dd

it is a standalone server but what permissions i should set to this image
connected to a loop device
the selinux is disabled


On Sun, May 8, 2016 at 9:39 PM, Gordon Messmer <gordon.messmer at
gmail.com>
wrote:
> On 05/08/2016 10:10 AM, nikos sarantopoulos wrote:
>
>> it is active directory my server setup
>>
>
> Is it a standalone AD server or a member of a domain?
>
> If it is standalone, how did you join the Windows workstation to the
> domain?  How did you create new users?  Are you using those new users on
> the Windows workstation?
>
> If it is a domain member, how did you join the AD domain?
>
> i am suspicious that is something
>> wrong when i am connecting to a loop device that is made this way dd
>> if=/dev/zero of=imgfile bs=1M count=60 for example
>> then losetup /dev/loop0 imgfile and formating it as ext4 filesystem
>>
>> but only root have there write access am i doing something wrong?
>>
>
> No, that's normal.  An ext4 filesystem supports permissions, and you
must
> manually set them to allow users to write to the new filesystem.
>
> this path is connected to a smb.conf with the following way:
>>
>> [test]
>>          path = /path (where is mounted the loop device)
>>          read only = no
>>
>
> You may have to deal with SELinux labels at some point, but at this point,
> I suspect your problems are more fundamental.
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

i join windows workstations from the computer with the properties and
switching it to a domain giving after the credentials of the Administrator
and the password of the Administrator to join the active directory domain



On Sun, May 8, 2016 at 10:03 PM, nikos sarantopoulos <
nsarantopoulos68 at gmail.com> wrote:
> it is a standalone server but what permissions i should set to this image
> connected to a loop device
> the selinux is disabled
>
>
> On Sun, May 8, 2016 at 9:39 PM, Gordon Messmer <gordon.messmer at
gmail.com>
> wrote:
>
>> On 05/08/2016 10:10 AM, nikos sarantopoulos wrote:
>>
>>> it is active directory my server setup
>>>
>>
>> Is it a standalone AD server or a member of a domain?
>>
>> If it is standalone, how did you join the Windows workstation to the
>> domain?  How did you create new users?  Are you using those new users
on
>> the Windows workstation?
>>
>> If it is a domain member, how did you join the AD domain?
>>
>> i am suspicious that is something
>>> wrong when i am connecting to a loop device that is made this way
dd
>>> if=/dev/zero of=imgfile bs=1M count=60 for example
>>> then losetup /dev/loop0 imgfile and formating it as ext4 filesystem
>>>
>>> but only root have there write access am i doing something wrong?
>>>
>>
>> No, that's normal.  An ext4 filesystem supports permissions, and
you must
>> manually set them to allow users to write to the new filesystem.
>>
>> this path is connected to a smb.conf with the following way:
>>>
>>> [test]
>>>          path = /path (where is mounted the loop device)
>>>          read only = no
>>>
>>
>> You may have to deal with SELinux labels at some point, but at this
>> point, I suspect your problems are more fundamental.
>>
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>

On 05/08/2016 12:09 PM, nikos sarantopoulos wrote:
> i join windows workstations from the computer with the properties and
> switching it to a domain giving after the credentials of the Administrator
> and the password of the Administrator to join the active directory domain

Again, how did you create users in the Samba AD domain?  Are you logging 
in to Windows using those AD user accounts?

On 05/08/2016 12:03 PM, nikos sarantopoulos wrote:
> but what permissions i should set to this image
> connected to a loop device

Ignore the fact that the filesystem is on a loopback device.  You will 
set permissions exactly the same way you would for any other directory.  
Generally: create a group of users in Samba AD, add the appropriate 
Samba AD users to the group, allow the group read/write access to the 
directory, and set the SGID bit so that group ownership is inherited 
from the parent directory.