Re: Respecting inherited Windows file permissions on file create

2013-09-30 Thread Jason Kresowaty
> Subject: Re: Respecting inherited Windows file permissions on file > create > From: Branko Čibej > Date: Mon, September 30, 2013 6:07 am > Whew. I'd really prefer not to second-guess Windows ACL inheritance like > this, Not to beat a dead horse, but if you call Set

Re: Respecting inherited Windows file permissions on file create

2013-09-30 Thread Branko Čibej
On 30.09.2013 11:33, Ivan Zhakov wrote: > On 30 September 2013 12:12, Bert Huijben wrote: >> Given the ‘create/close/move/open/write/close/move’ the average Windows >> installation would introduce a few more steps on both open and close for >> virusscanner intervention. >> >> There are thousands o

Re: Respecting inherited Windows file permissions on file create

2013-09-30 Thread Ivan Zhakov
On 30 September 2013 12:12, Bert Huijben wrote: > Given the ‘create/close/move/open/write/close/move’ the average Windows > installation would introduce a few more steps on both open and close for > virusscanner intervention. > > There are thousands of regressions since moving to a central working

Re: Respecting inherited Windows file permissions on file create

2013-09-30 Thread Branko Čibej
On 30.09.2013 10:12, Bert Huijben wrote: > > Given the ‘create/close/move/open/write/close/move’ the average > Windows installation would introduce a few more steps on both open and > close for virusscanner intervention. > > > > There are thousands of regressions since moving to a central working

RE: Respecting inherited Windows file permissions on file create

2013-09-30 Thread Bert Huijben
Windows file permissions on file create On 29.09.2013 23:15, Ivan Zhakov wrote: On 29 September 2013 18:49, Branko Čibej <mailto:br...@wandisco.com> wrote: On 29.09.2013 16:06, Jason Kresowaty wrote: The solution Ivan mentioned of creating a temp file in the same directory as the final f

Re: Respecting inherited Windows file permissions on file create

2013-09-29 Thread Branko Čibej
On 29.09.2013 23:15, Ivan Zhakov wrote: > On 29 September 2013 18:49, Branko Čibej wrote: >> On 29.09.2013 16:06, Jason Kresowaty wrote: >> >> The solution Ivan mentioned of creating a temp file in the same directory as >> the final file is common. >> >> >> I agree this is something we can look at

Re: Respecting inherited Windows file permissions on file create

2013-09-29 Thread Ben Reser
On 9/29/13 2:15 PM, Ivan Zhakov wrote: > Brane, do you remember reasons for creating temporary files in > .svn/tmp instead of target directory? Is it pre-wcng decision? I haven't looked at how WCNG processes things in this respect but the old WC code would create temp files and then a log of thing

Re: Respecting inherited Windows file permissions on file create

2013-09-29 Thread Ivan Zhakov
On 29 September 2013 18:49, Branko Čibej wrote: > On 29.09.2013 16:06, Jason Kresowaty wrote: > > The solution Ivan mentioned of creating a temp file in the same directory as > the final file is common. > > > I agree this is something we can look at. There were good reasons to not > create tempora

Re: Respecting inherited Windows file permissions on file create

2013-09-29 Thread Branko Čibej
On 29.09.2013 16:06, Jason Kresowaty wrote: > The solution Ivan mentioned of creating a temp file in the same > directory as the final file is common. I agree this is something we can look at. There were good reasons to not create temporary files in the target directories, but we can certainly rev

Re: Respecting inherited Windows file permissions on file create

2013-09-29 Thread Jason Kresowaty
> From: Branko ÄŒibej > Date: Sun, 29 Sep 2013 07:14:07 +0200 > This is not in fact a bug in Subversion > The solution that jiggles the security descriptor is not acceptable. I note that svn is not touching the place where the inherit is actually assigned (a directory), yet it is interfering w

Re: Respecting inherited Windows file permissions on file create

2013-09-28 Thread Branko Čibej
On 28.09.2013 23:17, Ivan Zhakov wrote: > On 29 September 2013 00:25, Jason Kresowaty wrote: >>> Subject: Re: Respecting inherited Windows file permissions on file create >>> From: Ivan Zhakov >>> Date: Sat, September 28, 2013 3:29 pm >>> Solution (2) is c

Re: Respecting inherited Windows file permissions on file create

2013-09-28 Thread Jason Kresowaty
> Subject: Re: Respecting inherited Windows file permissions on file create > From: Ivan Zhakov > Date: Sat, September 28, 2013 3:29 pm > Solution (2) is create temporary file in > wc\a folder. In this case it will get proper inherited permissions > from wc\a folder. You may tr

Re: Respecting inherited Windows file permissions on file create

2013-09-28 Thread Ivan Zhakov
On 29 September 2013 00:25, Jason Kresowaty wrote: >> Subject: Re: Respecting inherited Windows file permissions on file create >> From: Ivan Zhakov >> Date: Sat, September 28, 2013 3:29 pm >> Solution (2) is create temporary file in >> wc\a folder. In this cas

Re: Respecting inherited Windows file permissions on file create

2013-09-28 Thread Ivan Zhakov
On 28 September 2013 23:19, Jason Kresowaty wrote: >> From: Ivan Zhakov >> Date: Sat, September 28, 2013 2:46 pm >> I see two possible solutions for this problem: >> 1. Use hTemplate argument in CreateFile call when temporary file is created >> 2. Created temporary file along original file to be

RE: Respecting inherited Windows file permissions on file create

2013-09-28 Thread Jason Kresowaty
> From: Ivan Zhakov > Date: Sat, September 28, 2013 2:46 pm > I see two possible solutions for this problem: > 1. Use hTemplate argument in CreateFile call when temporary file is created > 2. Created temporary file along original file to be replaced instead > of .svn/tmp in working copy root > > O

Re: Respecting inherited Windows file permissions on file create

2013-09-28 Thread Ivan Zhakov
On 28 September 2013 22:00, wrote: > In a working copy, different directories may require different Windows > permissions (access control lists). For example, some might contain > code or data to be accessed by Windows services. Concretely, the > Windows service might be a web server and the dire