Re: [opensc-devel] Misleading information about capabilities of readers

Le mercredi 12 janvier 2011 à 23:41 +0100, Peter Stuge a écrit : > What do you mean by this? It sounds really obnoxious, but I think > there is a language barrier here and I do not want to jump to > conclusions. Sure, French is my mother tongue, not English. I am a nice guy, always pleasant with

Re: [opensc-devel] Misleading information about capabilities of readers

Jean-Michel Pouré - GOOZE wrote: > The libccid supported list is for companies which pay technical review. > When companies do not pay, readers are listed in "Should be supported". What do you mean by this? It sounds really obnoxious, but I think there is a language barrier here and I do not want

Re: [opensc-devel] Misleading information about capabilities of readers

On 12.01.2011 18:41, Aventra wrote: > My questions are: > - have other OpenSC users tried cards that use T=1 protocol? > - have somebody managed to use MyEID cards without adjusting the > configuration? In OpenSC-trunk r5087 MyEID card is normally working (erase,init,import PKCS#12) without c

Re: [opensc-devel] Misleading information about capabilities of readers

On Wed, 2011-01-12 at 19:41 +0200, Aventra wrote: > Hi, > > > -Original Message- > > > > -Original Message- > > > > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de] > > > > Sent: 12. tammikuuta 2011 12:46 > > > > > > > > > > There is nothing special about MyEID t

Re: [opensc-devel] Misleading information about capabilities of readers

Hi, > -Original Message- > > > -Original Message- > > > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de] > > > Sent: 12. tammikuuta 2011 12:46 > > > > > > > > There is nothing special about MyEID that would cause the issue. In > > windows > > > > everything works

Re: [opensc-devel] Misleading information about capabilities of readers

2011/1/12 Aventra : > Hi, > > I have attached the requested logs. Try again with _exactly_ what is documented on the web page: LIBCCID_ifdLogLevel=0x000F export LIBCCID_ifdLogLevel pcscd --foreground --debug --apdu Thanks --  Dr. Ludovic Rousseau ___

[opensc-devel] Supported algo references in 'sc_pkcs15_prkey_info'

Hello, I would like to introduce the array of algorithm references supported by key into the 'pkcs15 private/public key info' data. This issue was discussed in http://www.opensc-project.org/pipermail/opensc-devel/2010-September/014921.html and it seems that community was not hostile to this deman

Re: [opensc-devel] Consistence between the OpenSC and proprietary drivers

On 1/12/2011 1:54 AM, francois.lebl...@cev-sa.com wrote: > > I don't try this, but trainee that make some tests and manage to start > login, > > but server refuse the certificat (don't have exactly the cause). > > So I guess that opensc successfully start... > > > The best way is to have a one

Re: [opensc-devel] Misleading information about capabilities of readers

On Wed, 2011-01-12 at 17:22 +0200, Aventra development wrote: > Hi, > > > -Original Message- > > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de] > > Sent: 12. tammikuuta 2011 12:46 > > > > > > There is nothing special about MyEID that would cause the issue. In > windows

Re: [opensc-devel] Misleading information about capabilities of readers

Hi, > -Original Message- > From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de] > Sent: 12. tammikuuta 2011 12:46 > > > > There is nothing special about MyEID that would cause the issue. In windows > > everything works just fine if we follow the readers maxIFSD value. > > On

Re: [opensc-devel] Misleading information about capabilities of readers

Le mercredi 12 janvier 2011 à 13:26 +0200, Martin Paljak a écrit : > > > Per discussion, we have to pay to get the reader out of the > unsupported > > list, and this is quite a large sum of money. > Pay whom? How much? I would say 'technical review', nothing special. Reviewing a smartcard reade

Re: [opensc-devel] Misleading information about capabilities of readers

On Jan 12, 2011, at 1:22 PM, Jean-Michel Pouré - GOOZE wrote: > Le mercredi 12 janvier 2011 à 12:07 +0200, Martin Paljak a écrit : >> Jean-Michel, what were the symptoms of the bug? > > As for R-301-v1, it used to have an unsupported message, but it proved > to be an OpenCT incompatibility. So e

Re: [opensc-devel] Braking change in OpenSC 0.12.0 tokenInfo

Le mercredi 12 janvier 2011 à 13:07 +0200, Kalev Lember a écrit : > > Putting my Fedora packager hat on, please release new tarballs if you > have important bugfixes to distribute. This ensures everybody is using > the same code and makes problems much easier to debug. I also second this approac

Re: [opensc-devel] Misleading information about capabilities of readers

Le mercredi 12 janvier 2011 à 12:07 +0200, Martin Paljak a écrit : > Jean-Michel, what were the symptoms of the bug? Feitian R-301 was updated recently with a new CCID firmware, which works fine: http://www.gooze.eu/feitian-r-301-v2 In the CCID database, it is listed as the Feitian SCR310: http:

Re: [opensc-devel] Cryptoflex unsupprted?

On Wed, 2011-01-12 at 11:44 +0100, François Schauber wrote: > D:\Program Files\OpenSC Project\OpenSC>opensc-tool.exe -i > opensc 0.12.0 [gcc 4.4.4] > Enabled features: zlib openssl pcsc(winscard.dll) > > I added the lines in the opensc.conf but it's not enough, i assume > it's necessary to add th

Re: [opensc-devel] Braking change in OpenSC 0.12.0 tokenInfo

On 01/11/2011 06:21 PM, Mr Dash Four wrote: > >>> Something like that might actually warrant a new point release of >>> opensc to make sure Linux distros pick up the fix. >> >> Having a point release for every single bug fix would be overkill. So >> the question is, what's the best approach to quic

Re: [opensc-devel] Misleading information about capabilities of readers

2011/1/12 Andre Zepezauer : > On Wed, 2011-01-12 at 12:26 +0200, Aventra development wrote: >> There is nothing special about MyEID that would cause the issue. In windows >> everything works just fine if we follow the readers maxIFSD value. >> One difference with many other cards supported by OpenS

Re: [opensc-devel] Misleading information about capabilities of readers

On Wed, 2011-01-12 at 12:26 +0200, Aventra development wrote: > Hi, > > > -Original Message- > > From: opensc-devel-boun...@lists.opensc-project.org [mailto:opensc-devel- > > boun...@lists.opensc-project.org] On Behalf Of Ludovic Rousseau > > Sent: 12. tammikuuta 2011 11:22 > > To: opensc-

Re: [opensc-devel] Cryptoflex unsupprted?

D:\Program Files\OpenSC Project\OpenSC>opensc-tool.exe -i opensc 0.12.0 [gcc 4.4.4] Enabled features: zlib openssl pcsc(winscard.dll) I added the lines in the opensc.conf but it's not enough, i assume it's necessary to add the lines to treat the APDU treatment specific to this Cryptoflex card. 2

[opensc-devel] small change in build script to build with cardmod.

Hello Alon, I've noticed that you remove --enable-cardmod on build scripts due to licence issue, it's ok for me but to permit building cardmod simply I wish add the possiblity to set extra_opensc=--enable-cardmod in command line so : to enable cardmod: CHOST=i586-pc-mingw32 CBUILD=i686-pc-li

Re: [opensc-devel] Cryptoflex unsupprted?

Hello, On Wed, 2011-01-12 at 10:53 +0100, François Schauber wrote: > Hi, > > I just discovered OpenSC. I try to read my card, a Cryptoflex, but it > seems unsupported. > > D:\Program Files\OpenSC Project\OpenSC>opensc-tool.exe --reader 0 -a > 3b:95:18:40:14:64:02:01:01:02 > > D:\Program Files\O

Re: [opensc-devel] Misleading information about capabilities of readers

Hi, > -Original Message- > From: opensc-devel-boun...@lists.opensc-project.org [mailto:opensc-devel- > boun...@lists.opensc-project.org] On Behalf Of Ludovic Rousseau > Sent: 12. tammikuuta 2011 11:22 > To: opensc-devel > Subject: Re: [opensc-devel] Misleading information about capabilitie

Re: [opensc-devel] Cryptoflex unsupprted?

Hello, On Jan 12, 2011, at 11:53 AM, François Schauber wrote: > Hi, > > I just discovered OpenSC. I try to read my card, a Cryptoflex, but it seems > unsupported. > > D:\Program Files\OpenSC Project\OpenSC>opensc-tool.exe --reader 0 -a > 3b:95:18:40:14:64:02:01:01:02 This seems like an unknown

[opensc-devel] Cryptoflex unsupprted?

Hi, I just discovered OpenSC. I try to read my card, a Cryptoflex, but it seems unsupported. D:\Program Files\OpenSC Project\OpenSC>opensc-tool.exe --reader 0 -a 3b:95:18:40:14:64:02:01:01:02 D:\Program Files\OpenSC Project\OpenSC>opensc-tool.exe --reader 0 --name Unsupported card Are all the c

Re: [opensc-devel] Misleading information about capabilities of readers

Hello, On Jan 12, 2011, at 11:22 AM, Ludovic Rousseau wrote: > Every _non-bogus_ reader. > For example the Feitian SCR301 [2] is bogus and can't support CASE 2 > APDU with Le=0 (256 bytes). That is why this reader is listed in the > "unsupported" list of my CCID driver. Interesting. Too bad the o

Re: [opensc-devel] Misleading information about capabilities of readers

Hello, On Jan 12, 2011, at 11:34 AM, Aventra development wrote: > Readers we have tested are: > - ACS ACR38 CCID This is a very broad range, ACS re-uses the chip in different incarnations in several products that are marketed under different names and I would not bet on it being 100% the same chi

Re: [opensc-devel] Misleading information about capabilities of readers

Hi, Well this is just something we (and our customers) have encountered with the readers that we have tested. I don't know what causes the limitation (probably not the reader itself, because they work in windows just fine). So it might be in pcsc-lite, the ccid driver or something to do with usb

Re: [opensc-devel] Misleading information about capabilities of readers

2011/1/11 Andre Zepezauer : > Hello, > > the wiki page of MyEID [1] contains the following paragraph: > > "Many readers don't support receiving the default amount of data (254). > Problems will only appear when reading larger files from the card (e.g. > certificates). So if you have problems with r

Re: [opensc-devel] ruToken question

On 11.01.2011 09:03, Aktiv Co. Kirill Mescheryakov wrote: Rutoken device with with vid=0x0a89 and pid=0x0004 is earlier version of Aktiv Rutoken S Device. It contains several errors in PCSC layer and supported only by Aktiv Co. proprie

Re: [opensc-devel] Consistence between the OpenSC and proprietary drivers

On 1/11/2011 10:50 PM, Jan Just Keijser wrote: > Hi all, > > Viktor TARASOV wrote: >> On 11.01.2011 09:23, Xiaoshuo Wu wrote: >> >>> On Mon, 10 Jan 2011 16:50:37 +0800, Viktor TARASOV >>> wrote: >>> >>> Do we have any chance to influence the card producer and to change behavior