.NET news » Search results

It wasn't all that long ago that biometric authentication seemed like the kind of sci-fi technology that might never be practical outside of top-secret government laboratories. But believe it or not, you can build a fingerprint scanner into any .NET application you like just by following these simple instructions.

Is running .NET Framework code within SQL Server 2005 exciting or a threat? Which is it? This article explores the security issues of SQLCLR code so that both developers and DBAs can make informed decisions about its use.

How to build a secure file sharing network using a freeware Peer-to-Peer SDK

The Microsoft .NET Framework Class Library includes a ReaderWriterLock class in the System.Threading namespace. This month Jeffrey Richter explains when to use it and how you can get better threading performance.

This is a self paced workshop designed to lead you through the benefits and features of .NET security. There are over 50 code examples and many more walkthroughs showing you how to use the .NET security classes and how to administer .NET security policy. The workshop covers code access security, role based security, access control lists, symmetric and asymmetric cryptography, certificates, CMS/PKCS, data protection APIs, and encrypting and signing XML.

What InfoCard is, what it isn't, and what it means for the future of business and personal security on the Web.

Secure file download using basic authentication, the interesting part is that it maintains two separate entry points for uploading and downloading a file

Many classic ASP applications exist side-by-side with newer ASP.NET applications, sometimes leading to a need to transfer or share information between the two. This article shows one method of transferring such information securely.

Security Briefs: A First Look at InfoCard

One of the major benefits of writing .NET code to run in the Common Language Runtime (CLR) hosted in any environment is code access security (CAS).CAS provides a code-based-rather than user-based-authorization scheme to prevent various kinds of luring and other code attacks. But how does that security scheme coexist with SQL Server 2005's own, newly enhanced security features? By default your .NET code is reasonably secure, but it's all too easy for the two security schemes to butt heads and cause you grief. In this article I'll look briefly at the concept behind CAS and a few new security features in SQL Server 2005, then explore how to make the two systems work for you instead of against you as you take advantage of these advanced programming features in SQL Server.