|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: "How Named Pipe Security Works" (update)
From: Matt Conover (shok
CAMEL.ETHEREAL.NET)Date: Thu Aug 03 2000 - 09:37:11 CDT
- Next message: Todd Garrison: "Re: PORT or PASV mode of IIS 4.0's FTP"
- Previous message: Matt Conover: "Re: ImpersonateNamedPipeClient -- "How Named Pipe Security Works""
- In reply to: Matt Conover: "Re: ImpersonateNamedPipeClient -- "How Named Pipe Security Works""
- Next in thread: Marc: "Re: ImpersonateNamedPipeClient -- "How Named Pipe Security Works""
- Reply: Matt Conover: "Re: "How Named Pipe Security Works" (update)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
After talking to some friends again, I need to correct my final
paragraph. On the server side, you can only imperson someone *with* a
local account. The named pipe connection isn't established until the
client passes its credentials to the LSA (Local System Authority). An
administrator on machine A couldn't talk to a named pipe on machine B
without having an account on machine B.
Matt
- Next message: Todd Garrison: "Re: PORT or PASV mode of IIS 4.0's FTP"
- Previous message: Matt Conover: "Re: ImpersonateNamedPipeClient -- "How Named Pipe Security Works""
- In reply to: Matt Conover: "Re: ImpersonateNamedPipeClient -- "How Named Pipe Security Works""
- Next in thread: Marc: "Re: ImpersonateNamedPipeClient -- "How Named Pipe Security Works""
- Reply: Matt Conover: "Re: "How Named Pipe Security Works" (update)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]