> also, thank to note that "over-the-air" can be present "in the equation" - for
> some kind os applications that require confidentiality (but can't rely on the
> systematic availability of a SAM or HSM) some exchanges can be managed in
> plain with contact reader but require encryption when managed over-the-air.
(unrelated but still interesting)
Sorry but do not want! This kind of feature is a highway to funny security
problems. If you can have a secure channel, why not have it in contact mode too?
Are you aware of the kind of device the osmocom simtrace is?

here it is: http://bb.osmocom.org/trac/wiki/SIMtrace

> regarding provided information, I wasn't thinking about a long list that will
> never approved; I only dealt with contact or contactless.
>
> from my point of view (and my needs too) the details of the communication (and
> all points relevant at the "-3 level", including speed, RF type, and so on)
> don't need any new services / reporting.
>
Be careful, we're talking about contactless communication, not over the air!
(OTA is basically remote APDUs for mobile operators (mostly related to
globalplatform), it has little to do with  PC/SC :) )

RF type is still relevant, e.g. in the NFC world, you can have comme
applications activated or not according to the radio mode (A or B). but I agree
that communication speed is not.

> regarding features like biometric sensors, some providers (iD3) did provide
> some proprietary API and they weren't that nice, some (Sagem) define
> proprietary APDU to trigger scans, other (Zvetco) exhibit the biometric device
> w/o any privileged communication with the card reader(s) - a biometric chapter
> could / would be a great addition to the PC/SC standard but it wasn't my 
> point :)
>
correct me if I'm wrong but what does biometry has to do with PCSC except
nothing? If a card reader also has a fingerprint/whatever sensor then it's a
composite device isn't it?


Regards
Sebastien

_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to