Re: [opensc-devel] Interfacing eToken Pro/OpenSC with Apple Keychain

2006-03-02 Thread Stef Hoeben
tommytian wrote: I have two targets : 1. Create a PKCS7 message using certificate and private key store in aladdin etoken on Mac OS X 10.3 and 10.4. 2. Create a PKCS7 message using certificate and private key store in Mac OS X KeyChain Store.User can use Mac Tool that named Keychain Access to v

Re: [opensc-devel] how to use size_t in a printf?

2006-03-02 Thread Stef Hoeben
Nils Larsch wrote: Andreas Jellinghaus wrote: Am Donnerstag, 2. März 2006 17:22 schrieb Nils Larsch: I vote for printf("... %lu ...", (unsigned long) whatever, ...); I googled, and the options are %lu or %zu, the first is C89-portable (could cause problems in theory, where size_t != us

Re: [opensc-devel] export parse_tokeninfo() and rename it sc_pkcs15_parse_tokeninfo()

2006-03-02 Thread Nils Larsch
Nils Larsch wrote: Ludovic Rousseau wrote: Hello, I would like to use the function parse_tokeninfo() wich is defined static in libopensc/pkcs15.c. In order to keep the same naming scheme I propose to rename it in sc_pkcs15_parse_tokeninfo(). I added its definition in libopensc/pkcs15.h This

Re: [opensc-devel] how to use size_t in a printf?

2006-03-02 Thread Nils Larsch
Andreas Jellinghaus wrote: Am Donnerstag, 2. März 2006 17:22 schrieb Nils Larsch: I vote for printf("... %lu ...", (unsigned long) whatever, ...); I googled, and the options are %lu or %zu, the first is C89-portable (could cause problems in theory, where size_t != usigned long), the later

Re: [opensc-devel] how to use size_t in a printf?

2006-03-02 Thread Andreas Jellinghaus
Am Donnerstag, 2. März 2006 17:22 schrieb Nils Larsch: > I vote for printf("... %lu ...", (unsigned long) whatever, ...); I googled, and the options are %lu or %zu, the first is C89-portable (could cause problems in theory, where size_t != usigned long), the later is POSIX and C99-portable, and t

Re: [opensc-devel] export parse_tokeninfo() and rename it sc_pkcs15_parse_tokeninfo()

2006-03-02 Thread Nils Larsch
Ludovic Rousseau wrote: Hello, I would like to use the function parse_tokeninfo() wich is defined static in libopensc/pkcs15.c. In order to keep the same naming scheme I propose to rename it in sc_pkcs15_parse_tokeninfo(). I added its definition in libopensc/pkcs15.h This function is only used

Re: [opensc-devel] pkcs15-piv.c:308: warning: 'dfpath' is used uninitialized in this function

2006-03-02 Thread Ludovic Rousseau
On 02/03/06, Ludovic Rousseau <[EMAIL PROTECTED]> wrote: > Commited. Thanks. Argh! Nils was faster than me on the commit :-) -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailm

Re: [opensc-devel] pkcs15-piv.c:308: warning: 'dfpath' is used uninitialized in this function

2006-03-02 Thread Ludovic Rousseau
On 02/03/06, Douglas E. Engert <[EMAIL PROTECTED]> wrote: > Ludovic Rousseau wrote: > > The compiler is right. The value dfpath is used but is never > > uninitialized (unless some black magic is involved). > > It was a holdover from the gemsafe module where the static path in the > pindata structur

Re: [opensc-devel] how to use size_t in a printf?

2006-03-02 Thread Nils Larsch
Ludovic Rousseau wrote: Hello, In changeset 2863 [1] I changed %u in %lu because I got a compilation warning. The problem is the size_t is 64 bits on a 64-bits architecture but 32 bits on a 32-bits architecture. We could use a cast to int in the printf and use %u. I don't think we will ever hav

Re: [opensc-devel] pkcs15-piv.c:308: warning: 'dfpath' is used uninitialized in this function

2006-03-02 Thread Nils Larsch
Douglas E. Engert wrote: Ludovic Rousseau wrote: The compiler is right. The value dfpath is used but is never uninitialized (unless some black magic is involved). variable declared at line 217: int dfpath; and used at lines 308-309: pin_info.path.value[2] = dfpath >> 8;

Re: [opensc-devel] pkcs15-piv.c:308: warning: 'dfpath' is used uninitialized in this function

2006-03-02 Thread Douglas E. Engert
Ludovic Rousseau wrote: The compiler is right. The value dfpath is used but is never uninitialized (unless some black magic is involved). variable declared at line 217: int dfpath; and used at lines 308-309: pin_info.path.value[2] = dfpath >> 8; pin_info.path.value[3] = d

[opensc-devel] pkcs15-piv.c:308: warning: 'dfpath' is used uninitialized in this function

2006-03-02 Thread Ludovic Rousseau
The compiler is right. The value dfpath is used but is never uninitialized (unless some black magic is involved). variable declared at line 217: int dfpath; and used at lines 308-309: pin_info.path.value[2] = dfpath >> 8; pin_info.path.value[3] = dfpath & 0xff; I don't know h

[opensc-devel] how to use size_t in a printf?

2006-03-02 Thread Ludovic Rousseau
Hello, In changeset 2863 [1] I changed %u in %lu because I got a compilation warning. The problem is the size_t is 64 bits on a 64-bits architecture but 32 bits on a 32-bits architecture. We could use a cast to int in the printf and use %u. I don't think we will ever have a PIN length of more tha

[opensc-devel] export parse_tokeninfo() and rename it sc_pkcs15_parse_tokeninfo()

2006-03-02 Thread Ludovic Rousseau
Hello, I would like to use the function parse_tokeninfo() wich is defined static in libopensc/pkcs15.c. In order to keep the same naming scheme I propose to rename it in sc_pkcs15_parse_tokeninfo(). I added its definition in libopensc/pkcs15.h This function is only used once so the impacts on th

Re: [opensc-devel] Interfacing eToken Pro/OpenSC with Apple Keychain

2006-03-02 Thread tommytian
I have two targets : 1. Create a PKCS7 message using certificate and private key store in aladdin etoken on Mac OS X 10.3 and 10.4. 2. Create a PKCS7 message using certificate and private key store in Mac OS X KeyChain Store.User can use Mac Tool that named Keychain Access to view the certifivate