On 5 Mar 2010, at 17:34, Greg Mefford wrote:
> It seems like the card software includes some
> Windows tools (which is fine with me if that's what it takes to get
> started) and a bunch of technical documentation, but not much
> practical help in how to actually use the thing.
Right. As far as
I came across a case where a file name contained a newline (decimal 10,
0x0A) character, so that opensc-explorer broke the line when displaying it:
OpenSC [3F00]> ls
FileID Type Size
0001iEF 0
0003iEF 0
2F00wEF 250
[4100]DF 0 Name: \xE8(\xBD\x08\x0F
ACOPKCS-
Ludovic Rousseau wrote:
> On Jan 3, 2008 9:52 PM, Ian Young <[EMAIL PROTECTED]> wrote:
>> Is there a file missing from that checkin? For me, revision 3309 builds
>> (on Fedora 8) but 3310 and 3311 fail to build:
>>
>> make[3]: *** No rule to make target `pk
Martin Paljak wrote:
> On 03.01.2008, at 22:52, Ian Young wrote:
>>> Commited in revision 3310.
>>> Thanks
>>
>> Is there a file missing from that checkin? For me, revision 3309 builds
>> (on Fedora 8) but 3310 and 3311 fail to build:
>>
>>
Ludovic Rousseau wrote:
> On Dec 29, 2007 10:17 AM, Andrew V. Stepanov <[EMAIL PROTECTED]> wrote:
>> Hello!
>> Thank you for pointing to my inaccuracies.
>> In attachment patch for opensc.
>
> Commited in revision 3310.
> Thanks
Is there a file missing from that checkin? For me, revision 3309 b
There's some indication in these pages that the ACS ACR38 USB reader
might be supported now or in the future, depending on what the page
means by "the next release" (the page isn't dated).
http://www.opensc-project.org/openct/wiki/pertosmart1038
Does anyone know what the actual situation is?
Try
Andreas Jellinghaus wrote:
> so the question is: which goal do we have?
> - an emulation for their format?
> - implementing pkcs#15 format on acos5
>
> both would be nice, but for me the later would be more important right now.
I'm not sure how I'd judge which would be the best approach. Mayb
[EMAIL PROTECTED] wrote:
> Does anyone know, if the ACOS5 cards are implemented fully yet, since
> there are signs of it in the subversion-repository and an ACOS5
> driver seems to exist already. The pkcs11-tool however seems not to
> work. Is there a workaround for this?
The ACOS5 support that i
Martin Paljak wrote:
> On 13.03.2007, at 15:38, [EMAIL PROTECTED] wrote:
>
>> +static struct sc_atr_table acos5_atrs[] = {
>> +{"3b:be:18:00:00:41:05:10:00:00:00:00:00:00:00:00:00:90:00",
>> NULL, NULL,
>> + SC_CARD_TYPE_TEST_BASE, 0, NULL},
>
> This should definitely be something else t
Andreas Jellinghaus wrote:
> we prefer this style:
> indent -npro -kr -i8 -ts8 -sob -l80 -ss -ncs
Thanks. I'll try and keep to that in future.
> I could either ident the file and commit it.
> or do you want to send an updated copy?
I'd be happy for you to indent the file I already sent, unless
Andreas Jellinghaus wrote:
> sounds great, please post your code for review.
Here's what I have, as one attachment in "svn diff" format with the
minor changes and one file card-acos5.c with the rest.
I made sure the indentation on the minor changes matched the files that
were being changed. The
I made some progress a few weeks back on adding support for the ACS
ACOS5 cards. My current status is that I have things working in
opensc-tool and opensc-explorer, which is enough to be able to poke
around inside the card, read and list files.
I do have a couple of other things working, but it i
Ian Young wrote:
> From what you're saying, maybe the -I../../src/include option (either of
> them!) ought to be making the right thing happen, as that directory does
> include an opensc directory containing (soft links to) the appropriate
> files. Apparently not, though, and I
Ville Skyttä wrote:
> Wouldn't that be the rough equivalent of adding "." to $PATH and/or
> $LD_LIBRARY_PATH, ie. what stuff gets actually used would depend on in which
> dir a command pulling it in would be run? Doesn't sound too good to me when
> thinking about these same headers being insta
I ran into a problem recently when rebuilding opensc in an environment
where a version of the package was already installed (Fedora Core 6, gcc
4.1.1, with both opensc and opensc-devel installed).
The problem is that many of the opensc source files, but particularly
opensc.h, include files like th
Gabriele Turchi wrote:
> I was able to do also some secure operation directly on the card (I must
> check my code), but I wasn't able to fully understand the structure of a
> card driver: there are so many cross references between different parts
> of the libraries...
I've started working on this
Andreas Jellinghaus wrote:
> I'd be willing to help as time permits, and I'm sure many other people
> here can answer questions about writing new card drivers too. So why
> don't you give it a try? take a look at a few drivers with full support
> (like cardos and cryptoflex and starcos), the basic
There was a brief discussion a couple of months back about the ACS ACOS5
cards. Did anyone make any progress on this?
The certificate management and PKCS#11 support that comes with these as
part of the SDK is Windows-only. That's fine for my current project,
but in the longer term it would be ni
18 matches
Mail list logo
