Navigation

Search

Categories

On this page

DNA : Real identity ?
Sixth Law : The Law of Human Integration
ClickOnce Vs Windows Installer
Updater Application Block - An Excellent piece of work
Using NAnt custom tasks of .NET Smartcard SDK
Gates declares death of passwords using Cryptoflex.NET
Axalto Declares World’s First Commercial Deployment of Microsoft .NET-based Smart Card
Are there any .NET geeks for Liberty/SAML ?
WSE 3.0 wish list
Liberty Demo at Burton Catalyst, Europe
Plumbwork Orange moved to Sourceforge from GDN

Archive

Blogroll

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Sign In
Pick a theme:

 Wednesday, February 02, 2005
Wednesday, February 02, 2005 5:22:26 PM (Central Standard Time, UTC-06:00) ( )
I must say this is the most  beautifully phrased identity mapping I have seen
 
Your DNA is you. You are your DNA. It is not assigned to you nor can you change it. It is your identity. Everything else is simply a "handle", a shortcut or nickname for the identity that is you.
 
Scott  presents valid arguments against this perspective saying DNA is not 100% unique (fraternal twins and cloning) but his second argument that DNA does not mean anything in jungles of New zealand does not sound appealing to me. I mean whatever means of identity (token, certificate ...) you come up with, there will be a part of world which would not recognize it.
 
DNA coupled with hand prints (which are different for even fraternal twins) makes an interesting case.
 
Another important thing to see in his phrase is notion of "handle". I think every thing comes down to the fact that how secure, portable and efficient your handle is. Hey, am I saying Smartcards are the best handles :)
 
The phrase above is invention of Dave Kearns . I am a big fan of  newsletter on identity management by Dave.
 Tuesday, January 25, 2005
Tuesday, January 25, 2005 8:13:50 PM (Central Standard Time, UTC-06:00) ( )
Basically this Law says that identity system must define human user as one of the component in distributed systems and communication between human-machine should be protected against attacks.
 
Kim writes more,
    Returning to the discussion we've just had about the problems with today's browsers, I would summarize my thinking by saying we have done a pretty good job of cryptographically securing the channel between web servers and browsers - a channel that might extend for thousands of miles.  But we haven't done a very good job at all of setting up the two or three foot channel between the browser and the human who uses it.  And this is the channel that is attacked by phishers. 
 
I tried to solve the problem of Phishing and unsecured browser-human channel by providing an alternative to address bar (I know Kim is not a big fan of 'yet another address bar'). The alternative is that if user has identified his Service provider he/she can store the link to it as a metadata in Smartcard and once he has successfully pinned his Smartcard, this meta data will be extracted (securely) by some custom control in browser. I used this approach in Liberty LECP profile demo using .NET Smartcard storing the list of service providers as Xml metadata.
 
I feel that if we can achieve such kind of interaction [friendly enough for non-technical users] with the human element in distributed systems we should be good ? ....... Please comment.
 Saturday, January 22, 2005
Saturday, January 22, 2005 12:08:53 PM (Central Standard Time, UTC-06:00) ( )
Michael Sanford has a written a great article on comparison of ClickOnce and Windows installer technologies showing the differences in the features and when its ideal to use a particular
technology.
 
Message I got from this article that ClickOnce is not eliminating the Windows Installer but complement Windows installer by providing a robust, secure and easy way to update the applications installed using installer.
 
 
Saturday, January 22, 2005 11:56:55 AM (Central Standard Time, UTC-06:00) ( )
Although all the application blocks from Microsoft patterns and practices are great the one that I have liked the most and actually using in my product is UAB [Updater Application Block]. For a while I was playing around with version 1 posted here until last month I realized gotdotnet.com has a workspace for UAB and enhanced the application block in substantial way. UAB is in its version 2 now.
 
This is really great piece of work and would recommend people to use it.
 Friday, December 17, 2004
Friday, December 17, 2004 5:54:08 PM (Central Standard Time, UTC-06:00) ( )

Ant & NAnt have been the pioneers in recent times for automating the build and as Ant/NAnt guys describe their fascinating software - its kind of Make but without Make wrinkles. I have been a great fan of this stuff for a long time now. NET Smartcard SDK offers the custom NAnt tasks to automate the interactions with .NET Smartcard. I am going to describe here the custom tasks we have for .NET Smartcard.

If you are not familiar with NAnt please visit http://nant.sourceforge.net/

Below are described the custom NAnt tasks available for .NET Smartcard framework SDK.

  • LoaderTask             
         <target name="build" description="load and execute assembly">
         
              <load file="bin\debug\Test1.exe" todir="C:\Pub" execute="true"
                                                          reload="true" serviceName="test"/>        
 
 
               <load todir="D:\Pub">
                       <fileset basedir=".">
                            <includes name="Rijndael.bin"/>
                            <includes name="server\AppConfig.xml"/>
                       </fileset>
              </load>

         </target>
 
 
         This is most used task and also part of Server template in VS.NET 2003. Let's look at the attributes
 
 Name Description Required
file

File to be loaded in the card. You can specify the full or relative path.

    YES
todir On card directory in which to download the Test1.exe     YES
execute Run the executable [ This creates a .NET Smartcard service]     NO
reload If 'file' is already loaded in the assembly this will first remove the service installed & delete the file before downloading it again     NO
serviceName This is needed if you specify reload attribute since name of the service is needed to uninstall it.     NO
 
  • Delete2Task
        <delete2 file="D:\Pub\Rijndael.bin"/>
        <delete2 file="C:\Pub\server.exe" unregister="MyServiceUri.apdu"/>
       
        Delete task has 2 as a suffix to distinguish it from regular delete task.

       

Name Description Required
file

Full path to the on-card file to be deleted.

  YES
unregister If file to be deleted is an executable then name of the attribute is to be specified as value of this attribute   YES

  • ExecuteAssemblyTask       

        <execute file="C:\MyDir\MyProfile.exe"/>

        <execute>
            <fileset basedir="C:\MyDir2">
                <includes name="server1.exe"/>
                <includes name="server2.exe"/>
            </fileset>
        </execute>
 
There are still more tasks to write for administrating the card.
 
Running the build file from CardExplorer
 
 

Changing the path to NAnt binaries

.NET Smartcard SDK installs the NAnt binaries (shown below). The folder also contains netCard.NAntTasks.dll assembly which contain the above mentioned task. If you already have NAnt installed on your PC or want to download an updated version, you should add a path variable NANT_HOME in System settings & copy the netCard.NAntTasks.dll into the bin folder of NANT_HOME. If NANT_HOME is not defined, SDK takes [INSTALL_DIR]\3rdParty\NAnt as the default path for NAnt.

 Tuesday, November 16, 2004
Tuesday, November 16, 2004 2:44:55 PM (Central Standard Time, UTC-06:00) ( )

http://www.techworld.com/opsys/news/index.cfm?NewsID=2627

"The move towards smart cards is the way forward," said Gates in his keynote at IT Forum, in Copenhagen this morning. "The idea is to have a smart card that connects up in the best way - a .Net based smart card."

Microsoft partner Axalto "has done a super job on this", said Gates. "We will be using their smartcards internally - each employee will use those to get in and out of the buildings as we used to connect to our machines. We're requring them. We will completely replace passwords."

By having .Net capability, said Gates, "we think this brings different logic down to the card itself, giving a richness and continuity to the platform that only exists in that .Net environment." Axalto said this was the first commercial deployment of Axalto’s .Net-based smart cards.

Tuesday, November 16, 2004 2:41:03 PM (Central Standard Time, UTC-06:00) ( )

For the press release goto: http://www.axalto.com/Company/press/news.asp?id=220

Finally its out of the lab as the product which is not only going to make systems secure but revolutionize the Smartcard technology with the help of excellent on-card & off-card application developement framework i.e .NET.

 

 Sunday, November 14, 2004
Sunday, November 14, 2004 11:18:12 PM (Central Standard Time, UTC-06:00) ( )

Except for Ping identity package for .NET (where they used the xsd generated classes) for Liberty & SAML specifications I do not see single .NET implementation of either specifications. I am surprised why ASP.NET community and companies who use ASP/ASP.NET are not concerened about these standards or may be they are waiting for Microsoft to provide WS-Federation support.

I am in the process of writting SAML 2.0 implementation in C# and will open source it once I have a working version. I am using WSE 2.0 frameworks for the implementation.

Sunday, November 14, 2004 11:12:15 PM (Central Standard Time, UTC-06:00) ( )

Everyone is giving its wish list for WSE 3.0 with WS-Reliable messaging being the foremost requirement so I _wish_ WSE 3.0 would have support for SAML 2.0 & WS-Federation support. Given the extensible nature of WSE its not difficult (technically). Sometime back I had written an implementation of WS-Federation for Plumbwork at GDN (now moved to SourceForge) for my identity management demo at Burton-catalyst, WSE team may take that as a starting point.

 Thursday, October 28, 2004
Thursday, October 28, 2004 2:55:56 PM (Central Standard Time, UTC-06:00) ( )

Its been more than month I have blogged something.... was on holidays and before that busy preparing demo using Liberty LECP profile for SmartCards. This is what is described below:

LECP or Liberty-Enable Client & Proxy profile is specified in “Liberty Bindings & Profiles Specificatios“ [Section 3.2.5]. LECP can be briefly explained as a client that has, or knows how to obtain, knowledge about the identity provider that the principal wishes to use with the Service Provider. This client receives and sends Liberty messages in the body of HTTP requests and responses.

Flow Diagram for LECP profile is :

The Demo comprised of 4 elements.

  1. Service Provider [SP], http://www.dotnetcard.com/Demos/Liberty-Catalyst/Liberty-sp/TinkuTinki.aspx
  2. Identity Provider [IDP], http://www.networksmartcard.com/Demos/Liberty-Catalyst/Liberty-idp/LECP.ashx
  3. Liberty UA : Internet Explorer + LECP ToolBar.
  4. Trusted Module : SmartCard.

Demo shows the proof-of-concept for role of SmartCards in Liberty Federation/ID Management world. I designed a toolbar for internet explorer which does the interactions with IDP, SP and Trusted Module (SmartCard). In the figure above toolbar can be considered as UserAgent (UA). Below is the picture of the toolbar:

Illustrated Below are the detailed steps of the demo:

  • Clicking on the LogOn button in the toolbar prompts for user to enter PIN to authenticate to SmartCard.
  • On successful validation, a list of Service Providers (stored as Xml file in .NET SmartCard) is retrieved by toolbar and shown in Service Providers combo Box in toolbar. Options and AutoFill buttons also get enabled.
  • User selects the Service Provider from the combo Box.
  • UserAgent (here toolbar) sends the request to SP selected for getting the AuthnRequestEnvelope as specified in LECP [Section 3.2.5.2].
  • SP sends AuthnRequestEnvelope to UserAgent, UA validates and process this message to retrieve IDP (if provided by SP).
  • If AuthnRequest message is good and valid, UA helps doing the mutual authentication of Trusted Module (SmartCard here) & IDP based on some shared secret. This scheme (authentication) has been used for demo purposes, we can make it as sophisticated as required.
  • On Successful authentication, UA (toolbar) sends the AuthnRequest received from SP to the IDP.
  • IDP does the necessary validation and processing of message and generates the AuthnResponseEnvelope containing the assertion about the user.

AutoFill button on the toolbar is a nice application to fill the forms on web pages from user data retrieved from SmartCard.

I used .NET for all the pieces necessary for the demo. .NET SmartCard is used as a TrustedModule. Below is shown the contents of the .NET SmartCard.

Lets have a look at Card Contents:

  • Liberty.TM.exe is the application doing mutual authentication with IDP. 
  • Liberty.ITrustedModule.dll is the interface to Trusted Module Service.
  • AutoFillOptions.xml : Contains the user data (eg Name,address etc)
  • ServiceProviders.xml : Contains the list of Service Providers supported by this SmartCard.
  • Assertions.xml : This is another very interesting part. This is a cached assertion inside the SmartCard and to be used for offline mode. There may arise a need that Service Provider is not online so user can always download the assertions from IDP and present it to SP offline.

 

 Saturday, September 18, 2004
Saturday, September 18, 2004 9:49:09 AM (Central Standard Time, UTC-06:00) ( )

Plumbwork Orange workspace has been moved from GDN to Sourceforge. You can find implementations of various WS-* specifications there including one from me called WS-Federation.