Re: [opensc-devel] Do not hardcode 3F005015

2006-09-18 Thread Andreas Jellinghaus
Does anyone have a card with two confliciting applications? How common are cards with two applications? Why would anyone put two applications on one card? I'm scared we might fall for an overengineering trap here, so lets first see if there is a real world problem, and what the easiest solution

Re: [opensc-devel] Do not hardcode 3F005015

2006-09-18 Thread Andreas Schwier
Dear Andreas, it is not uncommon to place two application DF on the card, one for electronic signatures based on a qualified certificate and one for signatures, authentication and encryption using a non-qualified certificate. The main reason for doing this in separate applications is, that the

[opensc-devel] Do not hardcode 3F005015

2006-09-14 Thread Ludovic Rousseau
Hello, I am trying to use a PKCS#15 using OpenSC and I discovered that OpenSC hardcodes 3F005015 in src/libopensc/pkcs15.c. Unfortunately my card uses 3F005000 instead. This path is available in EF(DIR) and is already parsed by OpenSC so why not use it? The patch is really simple (maybe too