67 lines
2.1 KiB
Plaintext
67 lines
2.1 KiB
Plaintext
From: brunomadv at ciudad.com.ar (Bruno Mattarollo)
|
|
Date: Thu, 22 Apr 1999 05:07:36 GMT
|
|
Subject: permissions on win32 [Q]
|
|
In-Reply-To: <7flpkv$6je$1@m2.c2.telstra-mm.net.au>
|
|
References: <7flpkv$6je$1@m2.c2.telstra-mm.net.au>
|
|
Message-ID: <001b01be8c7e$093c5770$6eba0ac8@kuarajy.infosys.com.ar>
|
|
Content-Length: 1764
|
|
X-UID: 1192
|
|
|
|
It looks like a solution, but I would have to create those template file by
|
|
hand ... Since all the permissions are new. I mean it's a migration from one
|
|
system to another, so there is no previous state, or at least, the previous
|
|
state is so diferent from the final one, that I cannot use a template file
|
|
without some serious hand-worked labor.... :-)
|
|
|
|
Thanks a lot Mark.
|
|
|
|
/B
|
|
|
|
Bruno Mattarollo <bruno at gaiasur.com.ar>
|
|
... proud to be a PSA member <http://www.python.org/psa>
|
|
|
|
> -----Original Message-----
|
|
> From: python-list-request at cwi.nl [mailto:python-list-request at cwi.nl]On
|
|
> Behalf Of Mark Hammond
|
|
> Sent: Wednesday, April 21, 1999 9:15 PM
|
|
> To: python-list at cwi.nl
|
|
> Subject: Re: permissions on win32 [Q]
|
|
>
|
|
>
|
|
> Bruno Mattarollo wrote in message
|
|
> <002401be8c03$4f21d380$6eba0ac8 at kuarajy.infosys.com.ar>...
|
|
> >Thanks Mark...
|
|
> >
|
|
> > All this is supposed to run on sunday and it's Mission Critical, so I
|
|
> >presume wiill be doing it by hand, but anyway thanks. I am
|
|
> looking forward
|
|
> >to be able to do this on NT... :-)
|
|
> >
|
|
> > FYI we will be running another mission critical process on Sunday and it
|
|
> >will be a small Python app that will run on NT ... I love Python ... :-)
|
|
>
|
|
> Actually, overnight I thought of a different solution you could
|
|
> use - use a
|
|
> "template file".
|
|
>
|
|
> Although the help file omits this information, you could use
|
|
> "win32security.GetFileSecurity()", and name a file that has the
|
|
> permissions
|
|
> you wish to "copy". This will give you a SECURITY_DESCRIPTOR
|
|
> object. Once
|
|
> you have the object, you can even manipulate the contents - the only thing
|
|
> missing from 124 was the ability to create a brand-new, empty
|
|
> SECURITY_DESCRIPTOR - all the functionality to manipulate them is
|
|
> there....
|
|
>
|
|
> Mark.
|
|
>
|
|
>
|
|
>
|
|
>
|
|
|
|
|
|
|
|
|
|
|