Re: MUSCLE SSP for Cyberflex

2000-02-09 Thread Simos Xenitellis



On Tue, 8 Feb 2000, kefren wrote:

 Hi all,
 
 I had a look at SSP-Lite, and found it a bit incomplete.
 As I'm really needing RSA-Authentication, and RSA-Signing services with
 SLB-Cyberflex, I'm completing it by myself.
 
 Is there any "work-in-progress"-version more recent than the one
 on the Linuxnet Web-Site ??

Hmm, does the SLB-Cyberflex support RSA-Authentication and Signing?
Which "Cyberflex" card do you have in particular?

Simos Xenitellis

***
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
***



R: MUSCLE SSP for Cyberflex

2000-02-09 Thread kefren

Xenitellis wrote:
 
 Hmm, does the SLB-Cyberflex support RSA-Authentication and Signing?
 Which "Cyberflex" card do you have in particular?
 

I have Cyberflex(TM) Access SmartCards - Class 00 Crypto
(ATR = 3B 16 94 81 10 06 01 81 3F), and it shoult support
RSA 512/768/1024 general encryption/decryption (useful
for signing/verifying too), as stated in
CyberflexProgrammersGuide (http://www.cyberflex.slb.com)


 
 ***
 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
 ***
***
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
***



Re: R: MUSCLE SSP for Cyberflex

2000-02-09 Thread David Corcoran

Hello,

I tried to answer the questions in between 
On Wed, 9 Feb 2000, kefren wrote:

 David wrote:
 
  Some of the crypto functions may require a
  significant increase in the WWT on the reader.  If you let me know what
  reader you are using I can see if this will be a problem and fix it before
  it exists.
 
 Could you please explain me what "WWT" stands for, because I don't
 understand what
 the problem is. However, I'm using a Towitoko's CHIPDRIVE.
 

WWT is working waiting time.  This is the time it takes for the card to
respond.  On some crypto functions this might take along time causing a
timeout.  By adjusting the WWT you can avoid this.

 Just 'cause you could help me, I'm having troubles to let RSA work on the
 Card,
 and I'd be very happy if anyone could take a look at this URL:
 http://smartie.austin.apc.slb.com/forums/cybaccmisc/62.html#1
 where I reported the problem.
 
 Furthermore, I need some elucidations about the transition from the old
 pcsc-src-0.8.9's C++ structure to the new pcsc's C structure.
   . Where has it ended the RESOURCEMANAGER class ?
   . Didn't you want to be compliant with PCSC/Winscard API ?
   . It provides separate classes for SCard, CryptKey, etc.., doesn't it ?
 (however, maybe I lost some important messages from you mailing-list, and
 misinterpreted the overall problem).

The pcsc-lite uses C function calls.  The reason for this is that most
programs under Unix use C instead of C++ and this makes the calling
conventions much easier.  The Microsoft class definitions for the service
providers are completely different than what is implemented under Windows.
The IS_FileAccess is just a list of C functions that I defined which are
very similar to those under Windows but use C instead.  I would suggest
using these and creating your own functions.  Also, if you are looking to
do crypto now you could use OCF which is in Java - I have written a layer
that interfaces between OCF and pcsc-lite for Linux.  You can use the
crypto under OCF if you want.  If you define the C functions let me know
and I will document them.


I don't suggest using pcsc-0.8.9 since I will no longer distribute it.  It
is way too bulky and non portable.


 

 A related me-uderstanding problem: what do they mean the prefixes
 IS_FileAccess, etc.. which I find on some (don't remember which one)
 card-driver ?
 
 BTW, the REAL problem, here, is: if I go on and write some code (I'm
 thinking
 to modify slb_cfaccess as a starting point), shoud I use
   . this-scard-hContext-Transmit(...)
   OR
   . SCardTransmit(hContext, ...) ?


I would use the SCardTransmit.  Download pcsc-lite from the web site and
take a look at the API document under docs directory.  It is pretty easy
to use.

 
 
 Thank you very much,
 
 Tommaso.
 
 
 
 Tommaso Cucinotta [EMAIL PROTECTED]
 Dipartimento di Ingegneria dell'Informazione
 Facolta' di Ingegneria
 Universita' di Pisa
 Italy
 
 ***
 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
 ***
 

***
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
***



Re: R: MUSCLE SSP for Cyberflex

2000-02-09 Thread Jim Rees

As David pointed out, WWT is work waiting time.  See 7816-3/8.2.  It's the
amount of time the terminal should wait before deciding the card isn't going
to respond.  It is normally 1 second for cards with default timing, such as
Cyberflex.

Every time you call apdu.waitExtension() it resets the timer, so you can
sprinkle these through the code, but Cyberflex is so slow you have to put
them in every few lines.

Or you can increase WWT by specifying non-default timing in your atr.
Problem with this is that most terminals seem to ignore WWT.

Here is an atr for Cyberflex that specifies a four second WWT:

3b 97 94 40 28 57 65 62 63 61 72 64
T=0 TA1=94 TD1=40 TC2=28
7 historical bytes: W e b c a r d
103 etu = 372 F / 1 D * 3.58 f
3990 cwt = (960 * 40 WI * 372 F) / 3.58 f / 1000

You can change the number of historical bytes, which is given in the bottom
nibble of the second byte.  Remember that all but the last two historical
bytes are specified in the "set java atr" apdu, whereas the last two are
specified in the exception thrown by your applet's main() method.
***
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
***



Re: MUSCLE JavaCard 2.0

2000-02-09 Thread mgaddin


 Mahlzeit
 
 
 Does someone have the JavaCard 2.0 specifications? I can't find
 them anywhere.
 
 
 Mahlzeit
 
 endergone Zwiebeltuete
 

Try here :

http://java.sun.com/products/javacard/javacard20.html

Bye!


 ***
 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
 ***
***
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
***



Re: MUSCLE JavaCard 2.0

2000-02-09 Thread Harald Vogt

On Mit, 09 Feb 2000, Matthias Bruestle wrote:

 Mahlzeit
 
 
 Does someone have the JavaCard 2.0 specifications? I can't find
 them anywhere.

Sun seems to have removed the links to older versions from their
JavaCard page. Anyway, they are still there and the 2.0 spec can be
accessed at

http://java.sun.com/products/javacard/javacard20.html

Regards

Harald
***
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
***