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

i will tell you about my setup

my setup is done with the command samba-tool domain provision --use-rfc2307
--interactive on the version 4.3.9 that i am thinking for me that version
is enough stable the last version doesn't have any more the
"Authenticated
Users"

it is active directory my server setup 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?

this path is connected to a smb.conf with the following way:

[test]
        path = /path (where is mounted the loop device)
        read only = no


thank you

nikos sarantopoulos



On Sun, May 8, 2016 at 6:31 PM, Gordon Messmer <gordon.messmer at
gmail.com>
wrote:
> On 05/08/2016 06:26 AM, nikos sarantopoulos wrote:
>
>> the only way to write there other users except root is setting with
>> chmod o+w /test
>>
>
> Yes, that is expected.
>
> from windows 7 using samba 4 i can write to folder but i cannot set
>> security setting getting always access denied when i am setting
>> security settings on the share
>>
>> what is wrong
>>
>
> You haven't told us anything about your Samba configuration, so
it's
> impossible to say.
>
> I'll make a wild guess though.  You're using "security =
user" and
> possibly mapping users to a guest account.  IIRC, you can only change items
> in the Windows security tab if you're using "security =
domain" or
> "security = ads"
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

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.

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
>