RE: folder virtualisation
- From: jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]")
- Date: Tue, 26 Jun 2007 03:39:11 GMT
Hi Ashnah,
Thank you for feedback the further information.
Yes, I see your concern. However, your problem looks like a security
configuration issue. I do not think this security problem can be resolved
by providing sample code. It is most possibly caused by improperly Windows
account security configuration. Furthermore, coding a sample Windows
Service+Named pipe project requires a lot of time and is not a trivial
task.
With your further information, it seems that your client GUI application is
not running under an Administrator account, yes? This looks like an
important clue. I suspect when your Windows Service running under
LocalSystem account created the named pipe with CreateNamedPipe API, the
default DACL assigned to the pipe does not grant the normal user account
read/write permissions. It may only grant Administrators group and
LocalSystem account WRITE pemission. This is a normal situation.
To check the exact DACL list of the created pipe, I recommend you download
Process Explorer from the link below:
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExp
lorer.mspx
Then, you may use the steps below to examine your pipe handle security DACL:
1. In Process Explorer, you can press "Ctrl+H" to switch the lower panel to
show all handles in a process.
2. You may choose your Windows Service process in the process list
3. You can click the "Type" column in lower panel to order the handles by
type
4. Look "File" type handle in the lower panel and find your Named Pipe
handle
Note: the Named Pipe handle will have name like "\Device\NamedPipe\...", so
it is easy to identify your pipe handle
5. Double click the handle to bring up the property dialog and switch to
"Security" tabpage.
6. Examine the DACL in the dialog to check whether it will not grant Users
account write permission
Once, you can determine the DACL of your pipe object does not grant write
permission to user account, you may pass a dedicated security descriptor
the last parameter of CreateNamedPipe to grant WRITE permission to your
client application user account. If you need some sample code regarding how
to pass SECURITY_ATTRIBUTES to add a customized allow ACE, the link below
contains some code snippet:
http://www.codeguru.com/forum/archive/index.php/t-301326.html
Hope this helps.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: folder virtualisation
- From: ashnah
- RE: folder virtualisation
- References:
- RE: folder virtualisation
- From: "Jeffrey Tan[MSFT]"
- RE: folder virtualisation
- From: ashnah
- RE: folder virtualisation
- From: "Jeffrey Tan[MSFT]"
- RE: folder virtualisation
- From: ashnah
- RE: folder virtualisation
- From: "Jeffrey Tan[MSFT]"
- RE: folder virtualisation
- From: "Jeffrey Tan[MSFT]"
- RE: folder virtualisation
- From: ashnah
- RE: folder virtualisation
- From: "Jeffrey Tan[MSFT]"
- RE: folder virtualisation
- From: ashnah
- RE: folder virtualisation
- From: "Jeffrey Tan[MSFT]"
- RE: folder virtualisation
- From: ashnah
- RE: folder virtualisation
- Prev by Date: RE: folder virtualisation
- Next by Date: Vista Credential Provider. Changing password.
- Previous by thread: RE: folder virtualisation
- Next by thread: RE: folder virtualisation
- Index(es):
Relevant Pages
|