This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: No effect of SE_BACKUP_NAME privilege on cygwin?

On Mar  1 23:06, Christian Franke wrote:
> Corinna Vinschen wrote:
> >  A Cygwin application's main thread is not running under the
> >process token, but under a derived impersonation token.  This is true
> >for every thread in Cygwin.  So, instead of using OpenProcessToken, you
> >should be able to accomplish what you want by calling OpenThreadToken.
> Yes, it works, thanks!
> Already tried this before but gave up too early, because it didn't work 
> in the non-cygwin version ;-)
> I didn't realize that the main thread has no token by default...

Yes, that's a bit irritating.

> >However, I'm wondering if a Cygwin application should always try by
> >itself to request the SE_BACKUP_NAME privilege.  It would simplify file
> >access for all privileged processes.  Hmm.
> >  
> Sounds reasonable.
> SE_RESTORE_NAME is requested somewhere in the code, but not SE_BACKUP_NAME.

I've applied a patch.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]