Hello :)
It's with great pleasure that I hereby announce that the
FileSystemCardService I was developing for the Cyberflex Open 16K is now
ready (at least until I discover the first bug :) ).
So, if someone needs one and wants to try it out, please don't hesitate
to ask me for it, ok ?
The sources occupy 75 KB and the documentation 111 KB.
Here follows a description of it's characteristics:
----------------------------------------------------------------------------
------------------------------------------------
This OCF 1.1.1 Compliant FileSystemCardService for the Cyberflex Open 16K
smartcard was developed for the course Cryptography Fundamentals.
However, since I felt that there were some features about the card that
weren't explored by the framework due to it's generality, I decided to offer
in this class not only the mandatory methods but also some utility methods
that may come in handy to anyone. So, if you really need to comply with the
standart, do so. Otherwise, you can use the non-standart methods that allow
to perform other operations or to determine the exact error using a large
number of specific exceptions.
It can also operate in 2 different ways of identity verification. By
default, and if the provideCredentials method is not invoked before trying
to perform an operation, there's no attempt to verify any identities before
trying to execute the operation. However, when this method is invoked, the
behaviour of the FileSystemCardService changes to trying to verify the
necessary known keys before each operation. But be advised that, if you
invoke any of the verifyCardHolder1 , verifyCardHolder2 or verifyKey
methods, the behaviour will revert to default.
This class offers two methods (printDirectoryInfo and printTree) that allow
to list a directory's contents and the directory tree, respectively. But,
because I haven't worked with Java Card or cardlets yet, these methods are
only capable of handling ISO defined file types like transparent, fixed
record,etc...
>From what I gathered, this card doesn't support variable record files. Even
though this has no impact on the card service itself, this card, and
therefore this card service, can't handle this file type.
I found this project to be very fulfilling. However, some errors or
omissions in the card's documentation made it a hard work because some
properties of the card had to be discovered by trial/error. I also had a
limited period for developing and testing this card service. Therefore, if
you spot any bug, incorrection or have an explanation to any of the facts
here stated, please don't hesitate to bring it to my attention. I'll be more
than happy to correct them in a future version.
It's in all justice to say that, through the OCF Mailing List, there were a
lot of people who helped me to unravel some of my doubts about the card, the
reader and the drivers used. So, and in no particular order, here go my
thanks to:
Neville Pattinson <[EMAIL PROTECTED]>
Akshay Sahai <[EMAIL PROTECTED]>
Marc Maman <[EMAIL PROTECTED]>
Simos Xenitellis <[EMAIL PROTECTED]>
Marc Talbot <[EMAIL PROTECTED]>
Peter Bendel <[EMAIL PROTECTED]>
Soren Hilmer <[EMAIL PROTECTED]>
----------------------------------------------------------------------------
------------------------------------------------
--------------------------
http://talk.to/borges
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--------------------------
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
