| |
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
1 Articles match "2003","Windows"
| Related DevelopMentor Courses | MORE | | NET Security Training Identify and prioritize risks and vulnerabilities in applications Protect data using encryption and signatures Impersonate and delegate Windows credentials Integrate with Windows domains and network authentication Write sandboxed applications Avoid common security threats like cross-site scripting or SQL injection Use CardSpace to authenticate users Secure communication with WCF Authenticate and authorize users in ASP.NET Security is a feature. How can I write applications that integrate with Windows security? But not every security feature is also a secure feature. DevelopMentor Courses - Tuesday, March 1, 2011 |
7 Articles match "2003","Windows"
| The Latest from DevelopMentor | MORE | | NET Framework platform availability Windows 95. The.NET Framework cannot be installed on Windows 95. Windows 98.NET 1.0,NET 1.1,NET 2.0,NET 3.0. Windows 98 SE.NET 1.0,NET 1.1,NET 2.0,NET 3.0. Windows ME.NET 1.0,NET 1.1,NET 2.0,NET 3.0. Windows NT 4.0 Windows XP.NET 1.0,NET 1.1. Windows XP SP2.NET 1.0,NET 1.1,NET 2.0,NET 3.0,NET 3.5. Windows 2000.NET 1.0,NET 1.1. Windows 2000 SP4.NET 1.0,NET 1.1,NET 2.0. Windows Vista.NET 2.0,NET 3.0,NET 3.5. Windows 2000 Server SP2.NET 1.0,NET 1.1. Windows Server 2003.NET 1.1,NET 2.0,NET 3.0. link]. link]. The Blomsma Code - Monday, February 2, 2009 Token Kidnapping (revisited) Quoting from the recommendations page of the original slide deck: Windows XP and 2003. On Windows Vista and 2008. It's been a while since I linked to Cesar Cerrudo's slide deck about token kidnapping. Now there is also a POC available (with samples how to use it from SQL Server and IIS). There is also some movement at MS now.( here , here ). On IIS 6 don't run ASP.NET in full trust and if classic ASP is enabled don't allow users to execute binaries. On IIS 7 don't run ASP.NET in full trust or don't run web sites under NetworkServer or LocalService accounts. www.leastprivilege.com - Wednesday, October 15, 2008 How to build a Development/Test/Demo CA So I ended up running Windows Cerificate Services which proved to be an easy to use, robust solution. Install Windows Server (2003 or 2008) - either phyiscally or virtually. You can also set the lifetime of that revocation list to some high value (like 5 years), so Windows will cache the list. I often need X509 certificates - but I never really became friendly with makecert. You can have one at home or carry it around in a VM. Perfect. There are some gotchas you can run into and I refined my configuration over the years. Basic Installation. Select Stand-alone CA. www.leastprivilege.com - Thursday, August 14, 2008 | -
| The Best from DevelopMentor | MORE | - How to build a Development/Test/Demo CA
So I ended up running Windows Cerificate Services which proved to be an easy to use, robust solution. Install Windows Server (2003 or 2008) - either phyiscally or virtually. You can also set the lifetime of that revocation list to some high value (like 5 years), so Windows will cache the list. I often need X509 certificates - but I never really became friendly with makecert. You can have one at home or carry it around in a VM. Perfect. There are some gotchas you can run into and I refined my configuration over the years. Basic Installation. Select Stand-alone CA. www.leastprivilege.com - Thursday, August 14, 2008 - Utilizing TAPI from an ASP.NET application
This deploys and executes properly on Windows 2003 Server and IIS6. I've gotten several email requests about using ATAPI from ASP.NET -- people have had trouble getting it to function properly so I figured I'd post an example of how it works. First, I'd recommend using ATAPI and not ITAPI3 - only because the latter pulls in COM objects which always makes things much more complex. The key thing to remember is where to hook up your events. Don't hook events inside your ASP.NET page-derived classes - that will keep the pages alive and cause memory leaks. Add a reference to ATAPI.DLL. - Christmas comes early: Microsoft releases Visual Studio.NET 2008
9: WPF and Windows Forms integration (“Crossbow”). Hand in hand with the designer view, VS2008 improves the designer experience for Windows Forms to WPF integration. 8: ClickOnce improvements Microsoft introduced a simplified way to deploy Windows Forms clients from the web with Visual Studio 2005 called ClickOnce. Building on the “split” window feature of VS 2005, Visual Studio 2008 now allows you to tile the window horizontally or vertically so you can split your design and code view across monitors! 7: Multi-framework targeting. SP1, 3.0 actually means 2.0 Mark's Blog of Random Thoughts - Wednesday, December 19, 2007 - Utilizing TAPI from an ASP.NET application
This deploys and executes properly on Windows 2003 Server and IIS6. I've gotten several email requests about using ATAPI from ASP.NET -- people have had trouble getting it to function properly so I figured I'd post an example of how it works. First, I'd recommend using ATAPI and not ITAPI3 - only because the latter pulls in COM objects which always makes things much more complex. The key thing to remember is where to hook up your events. Don't hook events inside your ASP.NET page-derived classes - that will keep the pages alive and cause memory leaks. Add a reference to ATAPI.DLL. - Christmas comes early: Microsoft releases Visual Studio.NET 2008
9: WPF and Windows Forms integration (“Crossbow”). Hand in hand with the designer view, VS2008 improves the designer experience for Windows Forms to WPF integration. 8: ClickOnce improvements Microsoft introduced a simplified way to deploy Windows Forms clients from the web with Visual Studio 2005 called ClickOnce. Building on the “split” window feature of VS 2005, Visual Studio 2008 now allows you to tile the window horizontally or vertically so you can split your design and code view across monitors! 7: Multi-framework targeting. SP1, 3.0 actually means 2.0 Mark's Blog of Random Thoughts - Wednesday, December 19, 2007 - NET Framework platform availability
Windows 95. The.NET Framework cannot be installed on Windows 95. Windows 98.NET 1.0,NET 1.1,NET 2.0,NET 3.0. Windows 98 SE.NET 1.0,NET 1.1,NET 2.0,NET 3.0. Windows ME.NET 1.0,NET 1.1,NET 2.0,NET 3.0. Windows NT 4.0 Windows XP.NET 1.0,NET 1.1. Windows XP SP2.NET 1.0,NET 1.1,NET 2.0,NET 3.0,NET 3.5. Windows 2000.NET 1.0,NET 1.1. Windows 2000 SP4.NET 1.0,NET 1.1,NET 2.0. Windows Vista.NET 2.0,NET 3.0,NET 3.5. Windows 2000 Server SP2.NET 1.0,NET 1.1. Windows Server 2003.NET 1.1,NET 2.0,NET 3.0. link]. link]. The Blomsma Code - Monday, February 2, 2009 - Token Kidnapping (revisited)
Quoting from the recommendations page of the original slide deck: Windows XP and 2003. On Windows Vista and 2008. It's been a while since I linked to Cesar Cerrudo's slide deck about token kidnapping. Now there is also a POC available (with samples how to use it from SQL Server and IIS). There is also some movement at MS now.( here , here ). On IIS 6 don't run ASP.NET in full trust and if classic ASP is enabled don't allow users to execute binaries. On IIS 7 don't run ASP.NET in full trust or don't run web sites under NetworkServer or LocalService accounts. www.leastprivilege.com - Wednesday, October 15, 2008 %>
| |   |
