<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:media="http://search.yahoo.com/mrss/"
    xmlns:evnet="http://www.mscommunities.com/rssmodule/"
    >
<channel>
    <title>ASP.NET Whitepapers</title>
    <link>http://www.asp.net/learn/whitepapers/</link>
    <description>ASP.NET Whitepapers</description>
    <dc:language>en-US</dc:language>
    <generator>RSS generated by www.asp.net</generator>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>The New Dynamic Language Extensibility Model for ASP.NET</title>
        <link>http://www.asp.net/ironpython/whitepaper/</link>
        <pubDate>Thursday, 2 Nov 2006</pubDate>
        <description>This paper describes the new dynamic language extensibility model that has enabled Microsoft to introduce IronPython for ASP.NET, a new implementation of the popular Python programming language.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Call a Web Service Using Client Certificates from ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302408.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>This How To describes how you can pass a client certificate to a Web service for authentication from an ASP.NET Web application or from a Windows Forms application. You can install the client certificate in either the local machine store or the user store. If you store the client certificate in the local machine store, you must configure the Access Control List (ACL) on the certificate to allow access to your application&amp;#8217;s account. If you are running a Windows Forms application, this account is your user account. If you are running an ASP.NET application, this account is the Network Service account by default on the Microsoft&amp;#174; Windows Server&amp;trade; 2003 operating system. If you have configured a custom account to run your ASP.NET application, you must configure the ACL to grant access to the custom account. If you store the certificate in an account&apos;s user store, applications that run using that account identity can access the certificate from there.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use IPSec for Filtering Ports and Authentication</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302366.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>Internet Protocol security (IPSec) is a protocol, not a service, that provides encryption, integrity, and authentication services for IP-based network traffic. Because IPSec provides server-to-server protection, you can use IPSec to counter internal threats to the network, including eavesdropping, tampering, man in the middle attacks, IP spoofing, and other password-based attacks. IPSec is completely transparent to applications because encryption, integrity, and authentication services are implemented at the transport level. Applications continue to communicate normally with one another using TCP and UDP ports.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use Forms Authentication with SQL Server in ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302398.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>This How To shows you how to implement Forms authentication against a SQL Server credential store. It also shows you how to store password digests in the database.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Call a Web Service Using SSL from ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302409.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>Secure Sockets Layer (SSL) encryption can be used to guarantee the integrity and confidentiality of the messages passed to and from a Web service. This How To shows you how to use SSL with Web services.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Implement Kerberos Delegation for Windows 2000</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302400.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>Kerberos delegation allows you to flow an authenticated identity across multiple physical tiers of an application to support downstream authentication and authorization. This How To shows you the configuration steps required to make this work.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use DPAPI (Machine Store) from ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302403.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>This How To shows you how to use DPAPI from an ASP.NET Web application or Web service to encrypt sensitive data.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use DPAPI (User Store) from ASP.NET 1.1 with Enterprise Services</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302404.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>This How To shows you how to use DPAPI from an ASP.NET Web application or service to encrypt sensitive data. This How To uses DPAPI with the user store, which requires the use of an out of process Enterprise Services component.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Create GenericPrincipal Objects with Forms Authentication in ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302399.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>This How To shows you how to create and handle GenericPrincipal and FormsIdentity objects when using Forms authentication.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Create a Custom Account To Run ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302396.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>ASP.NET Web applications usually run using the built-in ASPNET account. On occasion, you may want to use a custom account instead. This How To article shows you how to create a least privileged local account to run ASP.NET Web applications. This How To describes how to create a least privileged local account to run the ASP.NET worker process (aspnet_wp.exe) or for impersonated identities in virtual directories. Although the procedures in this How To create a local account, the same concepts apply to a domain account.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use IPSec to Provide Secure Communication Between Two Servers</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302413.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>IPSec is a technology provided by Windows 2000 that allows you to create encrypted channels between two servers. IPSec can be used to filter IP traffic and to authenticate servers. This How To shows you how to configure IPSec to provide a secure (encrypted) channel.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Set Up Client Certificates</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302412.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>IIS supports client certificate authentication. This How To shows you how to configure a Web application to require client certificates. It also shows you how to install a certificate on a client computer and use it when calling the Web application.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use Forms Authentication with Active Directory in ASP.NET 1.1</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302397.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>This How To article shows you how to implement Forms authentication against an Active Directory credential store.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Set Up SSL on a Web Server</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302411.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>A Web server must be configured for SSL in order to support https connections from client applications. This How To shows you how to configure SSL on a Web Server.</description>
        
    </item>
    <item>
        <dc:creator>ASP.NET Whitepapers</dc:creator>
        <title>Updated: Use SSL to Secure Communication with SQL Server</title>
        <link>http://msdn2.microsoft.com/en-us/library/aa302414.aspx</link>
        <pubDate>Sunday, 1 Jan 2006</pubDate>
        <description>It is often vital for applications to be able to secure the data passed to and from a SQL Server database server. With SQL Server, you can use SSL to create an encrypted channel. This How To shows you how to install a certificate on the database server, configure SQL Server for SSL and to verify that the channel is secure.</description>
        
    </item>
</channel>
</rss>