<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Why doesn't delegation work over the network?</title><link>http://blogs.msdn.com/larryosterman/archive/2004/06/29/169085.aspx</link><description>One question that keeps on coming up when you&amp;rsquo;re writing a server in NT is: &amp;ldquo;Why can&amp;rsquo;t I access remote resources from my server when impersonating my client?&amp;rdquo; It shows up on our internal aliases about once a month in one form or</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Why doesn't delegation work over the network?</title><link>http://blogs.msdn.com/larryosterman/archive/2004/06/29/169085.aspx#169459</link><pubDate>Wed, 30 Jun 2004 05:03:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:169459</guid><dc:creator>Pavel Lebedinsky</dc:creator><description>&amp;quot;Programming Windows Security&amp;quot; by Keith Brown has an interesting discussion of how delegation could have been implemented in a Win2K/Kerberos environment. The problem with the existing Win2K implementation is that you have no control over which services the clients can be delegated to - once the server is marked as trusted for delegation, it can do anything it wants with the client credentials. This has been addressed in Windows 2003 with its constrained delegation feature.&lt;br&gt;&lt;br&gt;By the way, LocalService doesn't have access to machine credentials. To be able to use delegation (or even authenticate to other machines in a domain), a service has to run as LocalSystem, NetworkService or a domain account.</description></item><item><title>re: Why doesn't delegation work over the network?</title><link>http://blogs.msdn.com/larryosterman/archive/2004/06/29/169085.aspx#169944</link><pubDate>Wed, 30 Jun 2004 16:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:169944</guid><dc:creator>Larry Osterman</dc:creator><description>Doh, of course you're right Pavel about LocalService - I added that to the list of accounts without thinking about it.  LocalService has no access to network resources, by design :)&lt;br&gt;</description></item><item><title>Roadmap To Delegation</title><link>http://blogs.msdn.com/larryosterman/archive/2004/06/29/169085.aspx#380116</link><pubDate>Fri, 25 Feb 2005 06:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:380116</guid><dc:creator>K. Scott Allen</dc:creator><description /></item><item><title>When people ask for security holes as features: Stealing passwords</title><link>http://blogs.msdn.com/larryosterman/archive/2004/06/29/169085.aspx#414603</link><pubDate>Wed, 04 May 2005 16:03:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:414603</guid><dc:creator>The Old New Thing</dc:creator><description>You can't get the user's password. You'd think that'd be obvious.</description></item><item><title>NT Networks, Delegation, Kerberos and Impersonation.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/06/29/169085.aspx#414696</link><pubDate>Wed, 04 May 2005 20:38:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:414696</guid><dc:creator>Miscellaneous Debris</dc:creator><description /></item></channel></rss>