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

2015-04-24 Thread Niels Thykier
On 2015-04-24 20:19, Justin B Rye wrote: > (Oops, slightly delayed by a powercut. Hurrah for FS journals.) > > Niels Thykier wrote: >> + >> + Samba4 requires exec-bit to permit files to be open for >> execution >> + > > s/open/opened/, and I don't think people say "exec-bit" (just > "executa

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

2015-04-24 Thread Justin B Rye
(Oops, slightly delayed by a powercut. Hurrah for FS journals.) Niels Thykier wrote: > + > + Samba4 requires exec-bit to permit files to be open for > execution > + s/open/opened/, and I don't think people say "exec-bit" (just "executable bit"). Samba4 requires executable bit to permit

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

2015-04-24 Thread Niels Thykier
Control: tags -1 pending On 2015-04-24 18:22, Mario Lipinski wrote: > Package: release-notes > > Hi, > > Jessie will release with Samba 4 containing lots of changes. While the > default configuration will be mostly backwards compatible I belief the > following change noteworthy in the release no

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

2015-04-24 Thread Mario Lipinski
Package: release-notes Hi, Jessie will release with Samba 4 containing lots of changes. While the default configuration will be mostly backwards compatible I belief the following change noteworthy in the release notes: Windows may ask to "open a file for execution". While with Samba 3 this wa