From: Ludovic Rousseau <[EMAIL PROTECTED]>
Reply-To: MUSCLE  <[EMAIL PROTECTED]>
To: MUSCLE <[EMAIL PROTECTED]>
Subject: Re: [Muscle] Newbie help on Gemplus 433USB setup?
Date: Wed, 21 Apr 2004 22:00:52 +0200

Le Tuesday 20 April 2004 � 16:56:37, Peter Williams a �crit:
> I built a version of muscle framework that links to microsoft's PC/SC.
> Happy to send the dll built for win32.

Never accept a binary only (dll) software. It may have a Trojan horse or
a side channel in it :-}

an interesting sideline. GeoTrust (the only real competitor to VeriSign in high-end certs) just licensed internal ms code, under the US part of the anti-trust settlement. This may finally break open the monopoly in authenticode certs, which controls when signed dll are loaded by the WinNT loader, and at what privilege level, for each NT subsystem.


Now that micorosoft have built/purchased a native subsytem for their Unix, there is no reason why a GNU/MING-linked PE for each IFD and PCSC-lite deamon could not be signed similarly, to create trusted paths on unix, too. The Internix kernel would then control loading of PE images. Once loaded, the socket on internix could be exported to the win32 subsystem, and be used by win32 apps to replace the win32 native resource manager.

This may be a better approach than the approach of building PCSC-lite on win32. In the subsystem build case, all the muscle IFD drivers would then work (awell as they currently do).


> It required a fair amount of source hacking - that we have no real > need to integrate into the muscle source.

Why do you think that? Supporting Windows would be fine and it should
not be impossible to support win32 AND Unix.

I gave David the source a while back. He was going to compare my hacks with the way he'd ideally like the integration to occur with the build process used by the trusted programmers in this community.


what was cute about the hack result was that I could build against any win32 PC/SC implementation, based on a .h and .dll. I build against two: microsoft's and an emulator for SUN's javacard TLP-224-wrapped TPDU server.

What I did not do, was try to link a PCSC-lite win32 DLL, as there would be no advantage today: the internal mappings onto IFD would get nowhere - the code does not use the windows PnP layer's enumerated set of readers: they dont export the muscle IFD interface, to my knowledge.

I suppose some soul could hack the opensc work and write an IFD->PnP-enumerator, so all windows readers bindings become available to PCSC-lite deamon via a meta-IFD. But, this seems only useful if there was some advantage to PCSC-lite deamon over microsoft's deamon. On this score, its only that the client can remotely drive the PCSC-lite resource manager over a client-deamon socket that really differentiates the two. And what is that advantage?

Whilst not answering the question posed, this last observation does incidentally link to the previous comment: that very remoting feature could be used to export the internix PCSC-lite deamon interface to the win32 world, on the same host. Assuming the designers got it right so all synchronization primitives are handled in the client/server protocol exported by PCSC-lite, then the fact that the winNT kernel is scheduling win32 and internix subsystems should not impact inter-subsystem communications.

This would all be cute. Its about a 2-4 weeks of dedicated work. Probably less than making and maintaining joint builds, as the design/build processes would be essentially independent.


 Dr. Ludovic Rousseau                        [EMAIL PROTECTED]
 -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle

_________________________________________________________________
Lose those love handles! MSN Fitness shows you two moves to slim your waist. http://fitness.msn.com/articles/feeds/article.aspx?dept=exercise&article=et_pv_030104_lovehandles


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

Reply via email to