Permission in Amahi Webinterface - without Console!

[sleife]

So

Hi everybody

I have a question with Amahi. I make a new Folder "TestFolder" for example.

Then i gave the following permissions:




So. Why does the User: "family" write and read access whatever i mark.
I tried to connect with a Windows Vista 64-Bit Machine.

When i don't give any permissions then the user has no Access to this folder.. but when i only give "Access" no Writeable" then the User has full access!??

[sleife]

Can somebody help me??

[sleife]

Please its really important.. Because i don't want that all Users has full persmisson to the directories.. !

[Wrekker]

I actually have a very similar issue/problem. I have two users, admin (brek) and a regular user (guest). When i set guest to Access but not Writeable, the guest has full access. If I remove both Access and Writeable, the share cannot be accessed by the guest. I can't figure out why guest is getting full access when i only want readable for the guest.

Another thing i was wondering about....if i change the permissions on a share, they do not take effect until i restart the client machine. For example, if I change guest to no access and no writeable from Access with writeable, I am able to access and write to the share until I restart the client computer.

I'm really enjoying Amahi so far! Another Vail Fail Transfer.

[lou1z]

check your /etc/samba/smb.conf file

In amahi:

when only certain users are allowed > valid users = UserA, UserB
when write access allowed > write list = UserA

however, maybe the dev's should consider the use of "read list" as well as valid users

"read list" overrides any other Samba permissions granted, as well as file permissions (write) on the server to deny users write access to a writeable share.
"write list" overrides other Samba permissions to grant write access, but cannot grant write access if the user lacks write permissions for the file.

after applying samba changes, you have to restart the samba daemon. some systems do this automatically but i would always do a manual restart by:
service smb restart

[Wrekker]

Forgive me for being a total noob, but how do i...

check your /etc/samba/smb.conf file

Thank you for your time!

[radioz]

Open up a file browser and view the '/etc/samba/smb.conf' file.

Or, open up a terminal window and type: sudo gedit /etc/samba/smb.conf (you'll need to supply your password)

[lou1z]

i always encourage people to go with vi
it's a little trickier but sometimes you don't get a chance to gedit etc

so using putty (from windows) or terminal (from linux) clients

vi /etc/samba/smb.conf

this will allow you to view the smb.conf file. just scroll down to view. you will see you shares eg [myshare] and the config below eg valid users = UserA
if you want to edit, enter "i" to take you into edit mode
do your editing (after you've gemmed up on samba!!) and vi!
once done, enter "esc" to take you back to command mode
enter ":wq" to write and quit

sounds a little complex but it's easy once you do it once or twice.

[sleife]

Thank you everybody!! Now it works!! :D

Look here:


For the future if the link is down: http://img249.imageshack.us/img249/5438/smbconf.jpg

[lou1z]

glad it worked out.....
it's a common problem or misconception with samba etc.
when it comes to shares, the easiest way to think of it is layers.
imagine samba as a layer on top of file permissions.
eg the file permissions have write access to all. samba has write permission for UserA only.
only UserA will have write permission even though the file has write permission for all.

switch it around and allow samba to allow write to all but the file actually has only read access permissions to groups & others.
only the owner will be allowed to write to the file even though samba allows all.