Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-16 Thread Dave Korn
Christopher Faylor wrote: > On Mon, Nov 16, 2009 at 09:14:11AM +, Dave Korn wrote: >> Corinna Vinschen wrote: >>> On Nov 16 09:01, Dave Korn wrote: aputerguy wrote: > So is 'subinacl' just another example of these badly behaved non-Cygwin > applications? Looks like it.

Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-16 Thread Christopher Faylor
On Mon, Nov 16, 2009 at 09:14:11AM +, Dave Korn wrote: >Corinna Vinschen wrote: >> On Nov 16 09:01, Dave Korn wrote: >>> aputerguy wrote: >>> So is 'subinacl' just another example of these badly behaved non-Cygwin applications? >>> Looks like it. >>> If so, is there anything on

Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-16 Thread Dave Korn
Corinna Vinschen wrote: > On Nov 16 09:01, Dave Korn wrote: >> aputerguy wrote: >> >>> So is 'subinacl' just another example of these badly behaved non-Cygwin >>> applications? >> Looks like it. >> >>> If so, is there anything one can do other than to use one of the other >>> methods to get a pro

Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-16 Thread Corinna Vinschen
On Nov 16 09:01, Dave Korn wrote: > aputerguy wrote: > > > So is 'subinacl' just another example of these badly behaved non-Cygwin > > applications? > > Looks like it. > > > If so, is there anything one can do other than to use one of the other > > methods to get a properly authenticated ssh l

Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-16 Thread Dave Korn
aputerguy wrote: > So is 'subinacl' just another example of these badly behaved non-Cygwin > applications? Looks like it. > If so, is there anything one can do other than to use one of the other > methods to get a properly authenticated ssh login? You mean, apart from the other methods to g

Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-16 Thread Corinna Vinschen
On Nov 15 20:02, aputerguy wrote: > > OK - I just re-read the ntsec portion of the cygwin manual and found this > paragraph: > > [...] > > So is 'subinacl' just another example of these badly behaved non-Cygwin > applications? > If so, is there anything one can do other than to use one of the oth

Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-15 Thread aputerguy
OK - I just re-read the ntsec portion of the cygwin manual and found this paragraph: > This has the following unfortunate consequence. Consider a service > started under the SYSTEM > account (up to Windows XP) switches the user context to DOMAIN\my_user > using a token created > directly by ca

subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM)

2009-11-14 Thread aputerguy
When I log in via ssh (and have the infamous USERNAME=SYSTEM), subinacl assigns *all* file and directory ownership to "nt authority\system" getfacl however still gets the ownership right. I assume this has something to do with the fact that ssh comes in as USERNAME=SYSTEM but it is a pita that su