[Muscle] GPShell 1.0.1 release

GPShell 1.0.1 was released. We have added support for "put_sc_key" command to put secure channel keys on card. We have tested it with Oberthur CosmopoliC 64K card and Cyberflex Access e-gate 32K. GPShell and OpenPlatform Library (which GPShell depends on) can be found at: http://sourceforge.net

Re: [Muscle] Card insertion/removal detection?

On 10/08/05, Geoffrey Elgey <[EMAIL PROTECTED]> wrote: > G'day, Hello, > I want to perform certain actions when a token is removed or inserted > into a slot. The PKCS#11 library includes a "WaitForSlotEvent" function, > but apparently this is not well supported across different PKCS#11 > implemen

Re: [Muscle] GPShell 1.0.0 release

Thanks, Peter. A new feature idea is alwas nice. I assume SCP01 stands for Secure Channel Protocol? I fail to understand how this would be helpful, though. If GPShell knows the plaintext of the key to be loaded, not much point in encrypting it between GPShell and the card. Could you elabora

Re: [Muscle] Card insertion/removal detection?

Hi Geoff, You may use the SCardGetStatusChange PC/SC API to monitor the reader. Rgds. Martin Geoffrey Elgey wrote: G'day, I want to perform certain actions when a token is removed or inserted into a slot. The PKCS#11 library includes a "WaitForSlotEvent" function, but apparently this is not

Re: [Muscle] GPShell 1.0.0 release

Peter Williams wrote: a nice featue would be this: use the SCP01 support to establish a confidentiality channel, and use the GP kek in the keyset to load a DES key into the _muscle_ key store. Thanks. But this would mean that the applet must support secure channels and the user of the apple

[Muscle] Card insertion/removal detection?

G'day, I want to perform certain actions when a token is removed or inserted into a slot. The PKCS#11 library includes a "WaitForSlotEvent" function, but apparently this is not well supported across different PKCS#11 implementations. I've written a daemon that makes PCKS#11 calls to detect a

RE: [Muscle] GPShell 1.0.0 release

a nice featue would be this: use the SCP01 support to establish a confidentiality channel, and use the GP kek in the keyset to load a DES key into the _muscle_ key store. From: Snit Mo <[EMAIL PROTECTED]> Reply-To: Snit Mo <[EMAIL PROTECTED]>, MUSCLE To: muscle@lists.musclecard.com Subje

Re: [Muscle] Info about smartcard!

Here is my problem: I have read *- ISO/IEC 7816 Part 4: Interindustry command for interchange *- MUSCLE PC/SC Lite API Toolkit API Reference Documentation *- CamCard C++ class for accessing the University Card (cambridge university) *- and many others docs but i have doubts about the fol

Re: [Muscle] windows CE, and PIV201 tokens

Picture + PKI == >> The idea of mixing a badge for visual inspection with PKI for remote access >> was a great idea. Ten years ago. Today it only creates problems and should >> be >I would tend to agree, using traditional engineering principles. >But its an enticing social prospect: ta

Re: [Muscle] Info about smartcard!

Antonio A wrote: hi friends of muscle, i write because you are the people who know about using smartcards on Linux. I am working on an application that have to use smartcards to export private keys and digital certificates. i have a LTC31 smart card reader from C3PO (usb interface) and a ceres

[Muscle] Info about smartcard!

hi friends of muscle, i write because you are the people who know about using smartcards on Linux. I am working on an application that have to use smartcards to export private keys and digital certificates. i have a LTC31 smart card reader from C3PO (usb interface) and a ceres smart card (criponi

Re: [Muscle] pkcslite and libmusclecard on solaris box

Wei Hu wrote: Hi Doug, I am trying to make it work on my solaris 9 box too. So far I've added the reader and I want to know how you use opensc-tool to see a card. I am pretty new to this area so some details are appreciated. You had to build the pcsclite with --enable-scf Then build the o

RE: [Muscle] windows CE, and PIV201 tokens

> The idea of mixing a badge for visual inspection with PKI for remote > access > was a great idea. Ten years ago. Today it only creates problems and > should be I would tend to agree, using traditional engineering principles. But its an enticing social prospect: take the existing US drivers

[Muscle] testpcsc is not responding

hi, Just installed pcsc lite on kernel 2.6.9-1.667 with 16K stacks enabled for Cardman 6020 USB Reader. I installed the latest drivers for 2.6 kernel from www.omnikey.com and installed the pcsc lite , the pcscd daemon is working fine but i cant understand that when I do ./testpcsc it says :- Test