Bug#783252: Document samba changes in regard to serving executable files to Windows clients

[Niels Thykier <niels@thykier.net>]

On 2015-04-24 20:19, Justin B Rye wrote:
> (Oops, slightly delayed by a powercut.  Hurrah for FS journals.)
> 
> Niels Thykier wrote:
>> +<section>
>> +  <title>Samba4 requires exec-bit to permit files to be open for execution</title>
>> +  <para>
> 
> s/open/opened/, and I don't think people say "exec-bit" (just
> "executable bit").
> 
>      <title>Samba4 requires executable bit to permit files to be opened for execution</title>
> 
> Or maybe it could be shortened to
> 
>      <title>New requirements for file execution in Samba</title>
> 
>> +    If a client requests for a file to be "opened for execution", then
>> +    Samba4 will require that the file have the "exec-bit" set on the
>> +    file in addition to the regular read permissions.  This also
>> +    causes "netlogon" scripts to be silently ignored if they lack this
>> +    exec-bit.
> 
>        If a client requests that a file should be "opened for execution",
>        Samba4 will require the executable bit to be set on the
>        file in addition to the regular read permissions.  This also
>        causes "netlogon" scripts to be silently ignored if they lack this
>        executable bit.
> 

Thanks, applied as-is.

~Niels