Re: Respecting inherited Windows file permissions on file create

> Subject: Re: Respecting inherited Windows file permissions on file
> create
> From: Branko Čibej <brane_at_wandisco.com>
> 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 SetNamedSecurityInfo after
the move, then most of the time things will end up "right" and once in
a while they will end up no worse than what you have today.

I don't know if SetNamedSecurityInfo is optimized for the case where it
performs a no op, but you can code that optimization yourself to avoid
any performance regression. (Have not researched how easy that
would be. Nor the corner case where you have (F) Full Control access
to .svn directory but not the final directory. Though as the file's
creator/owner I think you still will be able to effect the ACL
change.)

(Sorry, I haven't figured out why my mail program Reply to All doesn't
work quite right yet...)
Received on 2013-09-30 14:59:55 CEST