You are quite right, Anders, on the motivations of banks
and telco to never get along. For example, GSM already has a fully
complete, end-end security service fully deployed, with
full security roaming, rekey per network etc. The banks
rejected it, because of the transaction-fee model imposed
by
ProductID 0xE001
VendorID 0x04E6
best jim
On Oct 30, 2003, at 5:55 PM, Jean-Luc Giraud wrote:
Cool!
Could you send me the ProductId and VendorId? I'll generate a new .pkg
for it.
Cheers,
JLuc.
On Wednesday, October 29, 2003, at 08:58 PM, James E. Hopper wrote:
Hi,
out of desperation i tried
Sorry, I tried it from home and its fine with road runner. it must be
something in my companies firewall thats keeping it from working for
me.
jim
On Oct 30, 2003, at 1:49 PM, Ludovic Rousseau wrote:
Le mercredi 29 octobre 2003 à 15:55:48, James E. Hopper a écrit:
Hi,
the link in your email
Peter Williams [EMAIL PROTECTED] wrote:
>With Phillips now shipping the low-power
>802.11b chips for use in GSM handsets, you will
>soon see the SIM chip of your phone authenticating
>to merchant terminals much as we now authenticate by presenting
>a ICC on a plastic carrier to a swipe/smartcard
"Martin Buechler" <[EMAIL PROTECTED]> wrote:
>Just for clarification: What do you define as 'signing on-line data on
>the web using Internet browsers' and where could one find an example?
The scenario is that you are connected to an on-line service like a bank
and at a certain phase have to aknow
Please no HTML posts in message groups!
--
Henning Follmann | [EMAIL PROTECTED]
it consultant | www.itcfollmann.com
___
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle
Might want to ensure that pcsc_stringify_error() is PCSC_API
defined and declared, so its exported from the musclecard DLL,
when built in DEBUG configuration. At least one musclecard client
tries to import the declaration from the win32 DLL implementation
(debuglog.obj).
pcsc_stringify_error()
