I do not have MAC and cannot do the tests myself.
If it's a regression, and if you have an access to MAC platform, you could
try to determine the commit that introduced this problem.
I do not see other way to resolve it .
I propose to tag the 'rc1' and wait during certain time for more details or
Le mercredi 03 octobre 2012 à 09:17 +0200, Viktor Tarasov a écrit :
> Ok, I will create the tag for release candidate.
Please have a look at this Mac OS X package issue. I don't understand
why the package build fails at final stage.
Kind regards,
--
Jean-Michel Pouré - Gooze -
Hello Andreas,
On Tue, Oct 2, 2012 at 7:53 PM, Andreas Schwier (ML) <
andreas.schwier...@cardcontact.de> wrote:
> we've tested the nightly build (OpenSC-git20121002092635-win32.msi) that
> includes write support for the SmartCard-HSM and found no issues.
>
> We've tested with our own PKCS#11 tes
Hi Viktor,
we've tested the nightly build (OpenSC-git20121002092635-win32.msi) that
includes write support for the SmartCard-HSM and found no issues.
We've tested with our own PKCS#11 test suite, integration with Firefox
15.0.1 and Thunderbird 15.0.1 on Windows XP SP3.
Will there be a new releas
Hello,
Is there a way to test OpenSC latest developments for Windows? When I cd
to win32, there is an installer_from_build.sh script. Is it functional?
Does it require to use Wine under Windows?
Kind regards,
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
_
Hi everyone,
Ubuntu 10.04 LTS Beta 1 ("lucid") is now available on www.ubuntu.org.
I did some testing already, and it seems to work fine for the apps I
tested. More testing would be very welcome!
Also for those of you that want to test firefox with https client certificate
authentication, I found
Egon wrote:
> Hi everybody
>
> Several days ago I wrote a message about testing a new driver. I wrote my new
> driver over piv driver. Now, I am testing it... My driver uses a
> pkcs15-emulator.
>
The piv driver was never designed to work with pkcs15-init. as the card is
not file based, and
De: Andreas Jellinghaus
> Asunto: Re: [opensc-devel] Testing a new driver - File not found
> Para: "Egon"
> CC: opensc-devel@lists.opensc-project.org
> Fecha: martes, 12 mayo, 2009 11:39
> Hi Egon,
>
> so I get this right: you have a blank card, and you want to
>
Sorry, I've done.
I've integreated "westcos" cards.
You need to implement a "card-xxx.c " a "pkcs15-xxx.c" and to create a
tool "xxx-tool.c"
With westcos-tool I use opensc api to write file I need on the card, I
use pkcs15-westcos.c to
emulate pkcs15 structure for this card and of course car
Hi Egon,
so I get this right: you have a blank card, and you want to write
a driver for it, so you can initialize that card, create PINs,
create or store keys, store certificates and so on?
but you don't want to implement PKCS#15, but some other format
instead?
I think you need to write a huge a
aus
> Asunto: Re: [opensc-devel] Testing a new driver - File not found
> Para: opensc-devel@lists.opensc-project.org
> CC: "Egon"
> Fecha: martes, 12 mayo, 2009 9:43
> Am Dienstag 12 Mai 2009 09:32:57
> schrieb Egon:
> > Hi everybody
> >
> > Several days a
Hi Egon,
I think, if you use pkcs15 emulation you can't or didn't need to use
pkcs15-init tool, using pkcs15 emulation it's required when
cards are uncompatible with real pkcs15 structure so pkcs15-init tool
can't use them.
Use an another tool to init them or create yours...
François.
Egon
Am Dienstag 12 Mai 2009 09:32:57 schrieb Egon:
> Hi everybody
>
> Several days ago I wrote a message about testing a new driver. I wrote my
> new driver over piv driver. Now, I am testing it... My driver uses a
> pkcs15-emulator.
>
> When I use pkcs15-init -C , I get the following message:
I'm no
Hi everybody
Several days ago I wrote a message about testing a new driver. I wrote my new
driver over piv driver. Now, I am testing it... My driver uses a
pkcs15-emulator.
When I use pkcs15-init -C , I get the following message:
[pkcs15-init] apdu.c:184:sc_apdu_log:
Outgoing APDU data [ 1
Hi Egon,
I suggest you install your modified version of
opensc into some directory other than /usr
(e.g. /home/egon/my-opensc-build or /opt/my-opensc-build)
and then
a) change PATH and LD_LIBRARY_PATH to include those
bin and lib directories at the beginning, so your
modified opensc binaries and
Hi everybody
Several days ago, I wrote a message in order to know how can I write a new
driver for opensc. Now I have a alpha version of this driver and I want to test
it in my machine.
I have Ubuntu with opensc package installed. I have opensc-11.0.6 release too,
I made changes into this ver
2007/8/22, Douglas E. Engert <[EMAIL PROTECTED]>:
> Nils Larsch wrote:
> > Douglas E. Engert wrote:
> >> Looking at card.c:sc_detect_apdu_cse there is no check if the reader
> >> is capable of extended APDU should there be?
> >
> > is there a reliable way to detect this ?
>
> I think with the CCID
Nils Larsch wrote:
> Douglas E. Engert wrote:
>>
>> Lars Silvén wrote:
>>> Douglas,
>>>
>>> You got to have a reader capable of "extended APDU".
>>> Then no chaining is needed since the commands may exceed 256 bytes.
>>
>> Well what if I don't have a reader that is capable of extended APDU,
>
> b
Ludovic Rousseau wrote:
> 2007/8/21, Douglas E. Engert <[EMAIL PROTECTED]>:
>> While testing a pkinit with a PrimeCard, It tries to send a 266 byte
>> APDU and PCSC failed. I suspect that the block should be chained.
>> Is the logic at iso7816.c:812 iso7816_decipher correct for chaining?
>>
>>
>
Douglas E. Engert wrote:
>
> Lars Silvén wrote:
>> Douglas,
>>
>> You got to have a reader capable of "extended APDU".
>> Then no chaining is needed since the commands may exceed 256 bytes.
>
> Well what if I don't have a reader that is capable of extended APDU,
buy another one ?
> can the card
2007/8/21, Douglas E. Engert <[EMAIL PROTECTED]>:
> While testing a pkinit with a PrimeCard, It tries to send a 266 byte
> APDU and PCSC failed. I suspect that the block should be chained.
> Is the logic at iso7816.c:812 iso7816_decipher correct for chaining?
>
>
> stderr:
> [opensc-pkcs11]
> ../
Lars Silvén wrote:
> Douglas,
>
> You got to have a reader capable of "extended APDU".
> Then no chaining is needed since the commands may exceed 256 bytes.
Well what if I don't have a reader that is capable of extended APDU,
can the card do chaining in some other way?
Looking at card.c:sc_det
Douglas,
You got to have a reader capable of "extended APDU".
Then no chaining is needed since the commands may exceed 256 bytes.
Lars
Douglas E. Engert wrote:
> While testing a pkinit with a PrimeCard, It tries to send a 266 byte
> APDU and PCSC failed. I suspect that the block should be chaine
While testing a pkinit with a PrimeCard, It tries to send a 266 byte
APDU and PCSC failed. I suspect that the block should be chained.
Is the logic at iso7816.c:812 iso7816_decipher correct for chaining?
stderr:
[opensc-pkcs11]
../../../src/src/libopensc/reader-pcsc.c:215:pcsc_internal_transmit
24 matches
Mail list logo
