From: Tom Talpey <tom@talpey.com>
To: Volker.Lendecke@sernet.de, Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org
Subject: Re: Fix posix 311 symlink creation mode
Date: Wed, 11 Jan 2023 12:04:26 -0500 [thread overview]
Message-ID: <07befe2d-477a-5ff3-0eb5-93504ef1b09f@talpey.com> (raw)
In-Reply-To: <Y77pJ5LqbeU5uj8N@sernet.de>
On 1/11/2023 11:51 AM, Volker Lendecke wrote:
> Am Wed, Jan 11, 2023 at 10:21:07AM -0600 schrieb Steve French:
>> Should this be 0777 instead of 0644?
>>
>> I noticed the man page for symlink says:
>>
>> "On Linux, the permissions of an ordinary symbolic link are not
>> used in any operations; the permissions are always 0777 (read,
>> write, and execute for all user categories), and can't be
>> changed."
>
> I thought about that as well. If you "ls -l" such a symlink once
> created, it will show as 0777, probably the client does it
> somehow. The problem however is that if you create it with 0777
> server-side, everybody can mess with that file that the client view as
> a symlink. That's why I thought that 0644 is the best approximation.
Yeah, because this is an mfsymlink, which is really just a file with
specific contents, you might even argue 0444 is safest.
Definitely not 0777.
Tom.
next prev parent reply other threads:[~2023-01-11 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 11:42 Fix posix 311 symlink creation mode Volker Lendecke
2023-01-11 13:57 ` Paulo Alcantara
2023-01-11 16:21 ` Steve French
2023-01-11 16:51 ` Volker Lendecke
2023-01-11 17:04 ` Tom Talpey [this message]
2023-01-11 20:18 ` Steve French
2023-01-12 13:25 ` David Disseldorp
2023-01-12 15:59 ` Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07befe2d-477a-5ff3-0eb5-93504ef1b09f@talpey.com \
--to=tom@talpey.com \
--cc=Volker.Lendecke@sernet.de \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox