Sure enough, the default acl shows the following:
TOKEN default acl:
Number of ACE: 2
cannot get name
S-1-0xc70x00x280x00xc80x0: unknown
read_perm|execute|delete|read|chmod
cannot get name
S-1-0xc70x00x280x00xc80x0: unknown
read_perm|execute|delete|read|chmod
Please forgive my ignorance, but what controls this and do you know how
I can change it. Something must have changed recently (much of our
computers are now locked down administratively due merging with another
company :O)
Thanks again!
Dave
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, April 29, 2008 12:00 PM
To: [email protected]
Subject: uwin-users Digest, Vol 46, Issue 14
Send uwin-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.research.att.com/mailman/listinfo/uwin-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of uwin-users digest..."
Today's Topics:
1. Re: unpacking using uwin-base.exe creates files with mode 000
(David Korn)
----------------------------------------------------------------------
Message: 1
Date: Mon, 28 Apr 2008 16:29:13 -0400
From: David Korn <[EMAIL PROTECTED]>
Subject: Re: [uwin-users] unpacking using uwin-base.exe creates files
with mode 000
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Subject: Re: [uwin-users] unpacking using uwin-base.exe creates files
with mode 000
--------
> This is a multi-part message in MIME format.
>
> Dear UWIN Team, I've encountered a recent issue installing UWIN using
> the latest (and even previous) uwin-base.exe files. For some reason
the
> files extracted to the temp folder created by the installation process
> are being extracted with mode 000, including the .exe files such as
> pax.exe. Thus the installation fails as it tries to run pax. I realize
> this maybe an issue with how our company is now adminstrating our
> computers, but any hints you might have would be extremely helpful.
I'm
> attempting to install on a Windows XP host, and haven't run into this
> problem before. The simple solution was to start the installation
> process and, before tapping "finish" on the final installation prompt,
> change the mode of the .exe files to be executable. Then the
> installation process completed.
>
> Thanks in advance,
> Dave
>
I haven't seen this behavior. It could be that the default acl
disables permissions.
You can try running
dumpsd -T
to dump out the process token security descriptor along with the
process security descriptor and maybe that will show something.
David Korn
[EMAIL PROTECTED]
------------------------------
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
End of uwin-users Digest, Vol 46, Issue 14
******************************************
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
