January 2010 - SmartcardServices-Dev

Building using darwinbuild
by William Siegrist 23 Jan '10

23 Jan '10

I wanted to report on recent work done to make SmartCardServices buildable outside of Apple. You can now build the Tokend and SmartCardServices projects that shipped with 10.5.6 and 10.5.7 using darwinbuild. We had to add a patch that adds includes that were needed to build with CFLite, but otherwise the source is unmodified. Darwinbuild helps by automatically putting roots in a chroot that have the private headers you need. First, install darwinbuild ( http://darwinbuild.macosforge.org/ ), then: # create a build environment $ mkdir ~/9J61 && cd ~/9J61 $ sudo darwinbuild -init 9J61 # build stuff $ sudo darwinbuild SmartCardServices $ sudo darwinbuild Tokend That's it. In this example, everything is kept in a chroot under ~/ 9J61/BuildRoot/. You can use /usr/local/share/darwinbuild/ packageRoots to produce a tarball in ~/9J61/Packages/ of your build. You can use /usr/local/bin/darwinup to install it like so: $ sudo darwinup install ~/9J61/Packages/SmartCardServices.root.tar.gz ... and to uninstall $ sudo darwinup list $ sudo darwinup uninstall <uuid from the list output above> -Bill

3 5

Re: [SmartcardServices-Dev] How to use secdebug()
by Garth Cummings 05 Jan '10

05 Jan '10

Hi Ludovic, On Jan 5, 2010, at 7:00 AM, smartcardservices-dev-request(a)lists.macosforge.org wrote: > Hello, > > I am trying to debug Apple version of pcsc-lite. The code contains calls like: > secdebug("pcscd", "RFCheckSharing: sharing violation, dwLockId: > 0x%02X", rContext->dwLockId); > > I would like to know _where_ the debug messages are sent? > And how to activate them (if needed)? <snip> > > It looks like it is related to DTrace. And I am a very beginner at DTrace. > So any help is welcome. > > Thanks > > -- > Dr. Ludovic Rousseau I have some instructions and a couple of D scripts for setting this up. Send a request to <dts(a)apple.com> and I'll get them to you without billing for a DTS incident. Best regards, --gc ____________________________________________________________________ Garth Cummings gcummings(a)apple.com Sr. Software Engineer Apple Developer Technical Support <http://developer.apple.com/technicalsupport>

1 0

How to use secdebug()
by Ludovic Rousseau 05 Jan '10

05 Jan '10

Hello, I am trying to debug Apple version of pcsc-lite. The code contains calls like: secdebug("pcscd", "RFCheckSharing: sharing violation, dwLockId: 0x%02X", rContext->dwLockId); I would like to know _where_ the debug messages are sent? And how to activate them (if needed)? What I found for now: >From /usr/local/SecurityPieces/Frameworks/security_utilities.framework/Headers/debugging.h // // The debug-log macro is now unconditionally emitted as a DTrace static probe p oint. // #define secdebug(scope, format...) \ if (__builtin_expect(SECURITY_DEBUG_LOG_ENABLED(), 0)) { \ char __msg[500]; snprintf(__msg, sizeof(__msg), ## format); \ volatile char c __attribute__((unused)) = scope[0]; \ SECURITY_DEBUG_LOG((char *)(scope), (__msg)); \ } else /* nothing */ #define secdebugf(scope, __msg) SECURITY_DEBUG_LOG((char *)(scope), (__msg)) >From /usr/local/SecurityPieces/Frameworks/security_utilities.framework/Headers/utilities_dtrace.h #define SECURITY_DEBUG_LOG(arg0, arg1) \do { \ __asm__ volatile(".reference " SECURITY_DEBUG_TYPEDEFS); \ __dtrace_probe$security_debug$log$v1$63686172202a$63686172202a(arg0, arg 1); \ __asm__ volatile(".reference " SECURITY_DEBUG_STABILITY); \ } while (0) #define SECURITY_DEBUG_LOG_ENABLED() \ __dtrace_isenabled$security_debug$log$v1() It looks like it is related to DTrace. And I am a very beginner at DTrace. So any help is welcome. Thanks -- Dr. Ludovic Rousseau

1 0