MUSCLE Resource Manager

1998-09-17 Thread David Corcoran 

Ok, I have released a sample base for a resource manager.  The code calls the
config file function to return key/value pairs from the config file called
config.txt.  This function returns the location of the reader CT-API library
for the specified reader SLB_RF_60 (Schlumberger Reflex 60).  The library is
then dynamically loaded and some sample smartcard functions are applied using
the CT-API provided by the dynamic library that is loaded.  The library is then
closed and the program exits.

This is base code for a Resource manager.  It just needs to be cleaned up and
CT-BCS functions need to be implemented in an API that sits above all of this. 
Then we just need to make it static to all applications and lock handles and we
have finished a very simple resource manager.

Let me know what you think.

Thanks
Dave


--
**
David Corcoran   Internet Security/Smartcards

Work:School:
205 Industrial Blvd  2252 US Highway 52 West Apt C4
Sugar Land, TX 77478 West Lafayette, IN 47906

Suggestion: Use Linux, it is for IQ's higher than 95.

Quote:
  If you can't make it work, at least make it look good.
~ Bill Gates
**
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***

MUSCLE Resource Manager

1998-09-16 Thread David Corcoran 



Now that the link is fixed I'll explain what we would have to do for the low
levels on a resource manager.  On the top level or the level that is what the
Application uses we can write a PC/SC subset of commands for the Application to
talk to.  Unfortunately there are some kernel issues here if we want the
resource manager to show up as a device like /dev/smartcard or whatever.  I
suppose you could have a static shared library which all the applications call
also.  Anyway, in this high level API there is a command which  allows the
Application to tell the Resource Manager which reader to utilize.  So a command
might be like this HandleIoInitialize ("Towitoko ChipDrive extern", PORT_COM2);
This functions (which is bogus) would then grep a configuration file looking
for the "Towitoko ChipDrive extern" configuration.  It would then see what
ports are available to it and if everything was OK, that file would also list
the location of it's shared library. The shared library would then be loaded
into memory which has it's appropriate CT-API commands with CT-BCS implemented
underneith even if the reader was poorly designed to fit this spec we can
always emulate in software.  The above function would return a Handle known to
the Resource Manager which would put a lock on that handle and the application
could then speak freely to the smartcard.  The resource manager should be
flexible enough to handle readers with PIN pads, Displays, etc. such like the
CT-BCS did.  We can do this by adding entries into the configuration file.  I
suppose we will have just 1 file for all of the readers instead of splitting
them up.  That could be a mess.  The Resource Manager is surprisingly pretty
simple to do I'm just not quite so sure how I want all of the applications to
be able to communicate with it.  I will need some suggestions here.
Questions ? Concerns ?  Let me know.

Thanks
Dave



 --
**
David Corcoran   Internet Security/Smartcards

Work:School:
205 Industrial Blvd  2252 US Highway 52 West Apt C4
Sugar Land, TX 77478 West Lafayette, IN 47906

Suggestion: Use Linux, it is for IQ's higher than 95.

Quote:
  If you can't make it work, at least make it look good.
~ Bill Gates
**
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***