<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Understanding and managing shares - Raspberry Pi				            </title>
            <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/</link>
            <description>Tweaking4All.com Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sat, 09 May 2026 21:09:15 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>RE: Understanding and managing shares</title>
                        <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3125</link>
                        <pubDate>Sat, 20 Feb 2021 14:31:15 +0000</pubDate>
                        <description><![CDATA[Awesome! Good to hear you may have things working 😊 
As for the quick help; you&#039;re most welcome! I happened to sit behind my computer 😜]]></description>
                        <content:encoded><![CDATA[<p>Awesome! Good to hear you may have things working 😊 </p>
<p>As for the quick help; you're most welcome! I happened to sit behind my computer 😜 </p>]]></content:encoded>
						                            <category domain="https://www.tweaking4all.com/forum/raspberry-pi/">Raspberry Pi</category>                        <dc:creator>Hans</dc:creator>
                        <guid isPermaLink="true">https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3125</guid>
                    </item>
				                    <item>
                        <title>RE: Understanding and managing shares</title>
                        <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3124</link>
                        <pubDate>Sat, 20 Feb 2021 14:14:17 +0000</pubDate>
                        <description><![CDATA[@hans thank you so very much...
Adding the line:
valid users = user1 root admin
 
did the trick... On a MAC anyway.... It does exactly what I need.
If a user clicks on any of the folder...]]></description>
                        <content:encoded><![CDATA[<p>@hans thank you so very much...</p>
<p>Adding the line:</p>
<pre contenteditable="false">valid users = user1 root admin</pre>
<p> </p>
<p>did the trick... On a MAC anyway.... It does exactly what I need.</p>
<p>If a user clicks on any of the folders that they don't have a password for then they are denied access, except of course for their own folder and the public.</p>
<p>Thanks very much for your help, I really appreciate it.</p>
<p>My first time on this forum, my first call for help, and solved within an hour!!!</p>
<p>I'm not rolling this out yet, I'll test it some more and make sure and try it on a Windows &amp; Linux box, but I'm confident.</p>
<p>Have a great weekend</p>
<p>Dj</p>]]></content:encoded>
						                            <category domain="https://www.tweaking4all.com/forum/raspberry-pi/">Raspberry Pi</category>                        <dc:creator>deljones</dc:creator>
                        <guid isPermaLink="true">https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3124</guid>
                    </item>
				                    <item>
                        <title>RE: Understanding and managing shares</title>
                        <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3123</link>
                        <pubDate>Sat, 20 Feb 2021 13:58:30 +0000</pubDate>
                        <description><![CDATA[Almost forgot to mention ConnectMeNow for Mac users (free), which may make access easier once the access rights issue has been resolved.]]></description>
                        <content:encoded><![CDATA[<p>Almost forgot to mention <a href="https://www.tweaking4all.com/os-tips-and-tricks/macosx-tips-and-tricks/connectmenow-v3/" target="true">ConnectMeNow</a> for Mac users (free), which may make access easier once the access rights issue has been resolved.</p>]]></content:encoded>
						                            <category domain="https://www.tweaking4all.com/forum/raspberry-pi/">Raspberry Pi</category>                        <dc:creator>Hans</dc:creator>
                        <guid isPermaLink="true">https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3123</guid>
                    </item>
				                    <item>
                        <title>RE: Understanding and managing shares</title>
                        <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3122</link>
                        <pubDate>Sat, 20 Feb 2021 13:53:03 +0000</pubDate>
                        <description><![CDATA[Just another thing that may be helpful, which I found here:
valid users
To restrict users per share, you can use the valid users parameter. In the example below, only the users listed as v...]]></description>
                        <content:encoded><![CDATA[<p>Just another thing that may be helpful, which I found <a href="http://linux-training.be/networking/ch21.html" target="true">here</a>:</p>
<p><a href="http://linux-training.be/networking/ch21.html#idp70210080" target="true">valid users</a></p>
<p>To restrict users per share, you can use the valid users parameter. In the example below, only the users listed as valid will be able to access the tennis share.</p>
<p>(modified for your user1)</p>
<pre contenteditable="false">
path = /home/user1
comment = authenticated and valid users only
read only = No
guest ok = No
valid users = user1 root admin</pre>
<p> </p>
<p>Note: The link seems a little dated, but the <a href="https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#idm4379" target="true">Samba.org Documentation</a> mentions it as well.</p>
<p> </p>]]></content:encoded>
						                            <category domain="https://www.tweaking4all.com/forum/raspberry-pi/">Raspberry Pi</category>                        <dc:creator>Hans</dc:creator>
                        <guid isPermaLink="true">https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3122</guid>
                    </item>
				                    <item>
                        <title>RE: Understanding and managing shares</title>
                        <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3121</link>
                        <pubDate>Sat, 20 Feb 2021 13:47:34 +0000</pubDate>
                        <description><![CDATA[Hi Deljones!

 Posted by: @deljones 
Users 1 to 3, after they have entered the server address then get asked for their credentials after which they get logged in. Good
However on a MAC, ...]]></description>
                        <content:encoded><![CDATA[<p>Hi Deljones!</p>
<blockquote data-userid="5017" data-postid="3120" data-mention="deljones">
<div class="wpforo-post-quote-author"><strong> Posted by: @deljones </strong></div>
<p>Users 1 to 3, after they have entered the server address then get asked for their credentials after which they get logged in. Good</p>
<p>However on a MAC, for example, when user 1 logs in they are then presented with a list of "volumes" to select. The volumes are the other uses and the public folder.</p>
</blockquote>
<p>This is typical Mac behavior when just entering the server name/IP address, for example:</p>
<pre contenteditable="false">smb://192.168.1.100</pre>
<p><br />To avoid this, use the full path tot he share, for example:</p>
<pre contenteditable="false">smb://192.168.1.100/user2</pre>
<p> </p>
<p>As for the undesired access (eg. User1 can work with the files of User2):<br />I suspect this has to do with your directory mask setting</p>
<pre contenteditable="false">create mask=0777
directory mask=0777</pre>
<p> </p>
<p>I'm definitely not a Linux/Samba expert, but from the <a href="https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#idm2702" target="true">Samba documentation or directory masks</a>:</p>
<p><span style="color: #0000ff"><em>    This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories.<br /></em></span><span style="color: #0000ff"><em>...<br /></em></span><strong><span style="color: #0000ff"><em>    The default value of this parameter removes the 'group' and 'other' write bits from the UNIX mode, <br />    allowing only the user who owns the directory to modify it.</em></span></strong></p>
<p><span style="color: #0000ff"><em>    Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force directory <br />    mode parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).</em></span></p>
<p><strong><span style="color: #0000ff"><em>    Default: directory mask = <span style="color: #ff0000">0755  </span></em></span></strong></p>
<p>So the mask you're using (777) actually gives full access to everybody (see also my <a title="Tweaking4All - CHMod Calculator" href="https://www.tweaking4all.com/software/linux-software/chmod-calculator/" target="true">chmod calculator</a>).<br />The mask 755 on the other hand, allows only the owner (and root of course) to write files (others can still read).</p>
<p>Maybe you'd like to tighten this even more, but <a href="https://askubuntu.com/questions/97669/i-cant-get-samba-to-set-proper-permissions-on-created-directories" target="true">Samba may do an odd translation of the rights</a>. You may need to do a little experimenting.<br />I also presume that <strong>create mask</strong> needs to be corrected as well.</p>
<p>Also note: you may need to update the access rights of the affected directories and files on your Raspberry Pi.<br />However, before doing this, I'd recommend testing the <strong>directory mask</strong> and <strong>create mask</strong> first.<br />If you have root access to your Raspberry Pi (which I assume you have), and you still see the undesired access, then you can look into changing the directory/file access rights with chmod (with <strong>chmod -R xyz</strong> wher xyz is the mask you'd like to use).</p>
<p>Hope this helps 😊 </p>]]></content:encoded>
						                            <category domain="https://www.tweaking4all.com/forum/raspberry-pi/">Raspberry Pi</category>                        <dc:creator>Hans</dc:creator>
                        <guid isPermaLink="true">https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3121</guid>
                    </item>
				                    <item>
                        <title>Understanding and managing shares</title>
                        <link>https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3120</link>
                        <pubDate>Sat, 20 Feb 2021 12:53:35 +0000</pubDate>
                        <description><![CDATA[Hello all.
I am trying to understand sharing on a pi. Here is what I have.
Three users, 1, 2, 3. They each have a folder. I also have a public folder.
Samba is installed and working. Here...]]></description>
                        <content:encoded><![CDATA[<p>Hello all.</p>
<p>I am trying to understand sharing on a pi. Here is what I have.</p>
<p>Three users, 1, 2, 3. They each have a folder. I also have a public folder.</p>
<p>Samba is installed and working. Here is the problem.</p>
<p>The public share works, users 1,2, and 3 can see it, read and write to it over the network. Good...</p>
<p>Users 1 to 3, after they have entered the server address then get asked for their credentials after which they get logged in. Good</p>
<p>However on a MAC, for example, when user 1 logs in they are then presented with a list of "volumes" to select. The volumes are the other uses and the public folder.</p>
<p>If user 1 selects user 2's folder it opens meaning user 1 can now see all of user 2's stuff and user 3! Bad</p>
<p>In fact, any of the users can log in, with the right credentials, but once on they can see and modify all the other users folders and content! Bad</p>
<p>Whew!!!! What have I done wrong here?</p>
<p>It's a permissions thing I know but I'm trying to get it so users 1 to 3 can log in anywhere on the LAN and see ONLY their own folders (R/W) and of course the public folder...</p>
<p><br />comment= user1 folder<br />path=/home/user1<br />browseable=yes<br />writeable=Yes<br />only guest=no<br />create mask=0777<br />directory mask=0777<br />public=no</p>
<p><br />comment= user2 folder<br />path=/home/user2<br />browseable=yes<br />writeable=Yes<br />only guest=no<br />create mask=0777<br />directory mask=0777<br />public=no</p>
<p><br />comment= user3 folder<br />path=/home/user3<br />browseable=yes<br />writeable=Yes<br />only guest=no</p>
<p>create mask=0777<br />directory mask=0777<br />public=no</p>
<p><br />Comment = Public shared folder<br />Path = /share<br />Browseable = yes<br />Writeable = Yes<br />only guest = no<br />create mask = 0777<br />directory mask = 0777<br />Public = yes<br />Guest ok = yes</p>
<p>Help! I'm almost there. I think.</p>
<p>Here is the section of my samba.conf file showing the users etc.</p>
<p>Best wishes</p>
<p>Dj</p>
<p> </p>
<p> </p>
<p> </p>]]></content:encoded>
						                            <category domain="https://www.tweaking4all.com/forum/raspberry-pi/">Raspberry Pi</category>                        <dc:creator>deljones</dc:creator>
                        <guid isPermaLink="true">https://www.tweaking4all.com/forum/raspberry-pi/understanding-and-managing-shares/#post-3120</guid>
                    </item>
							        </channel>
        </rss>
		