.
The (only?) PKI card from ACS is ACOS5. The rest are smart cards but cards that
are of no real interest to cryptographic PKI systems.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc
?
or is there some setting or theme or ... to do that?
With templates. I'll do it.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
OpenSC has never really had a IRC channel or people on it.
#opensc on freenode.net is occupied by some other (opensc.ws?) folks, so what
about #opensc-project channel?
I'm there at least..
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
?
or is there some setting or theme or ... to do that?
Maybe something like this:
http://www.opensc-project.org/test/newticket
?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
assert comes from entersafe (feitian)
driver code.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
and the
key files you have) I can try it with an epass3000 token (which should work
with the same driver and have the same chip inside) and see if/how/why it fails
for me.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel
On 11.01.2010, at 16:30, Peter Stuge wrote:
Martin Paljak wrote:
for generic educational purposes I would suggest making
YetAnotherSelfSignedSnakeOilOpenSSLCAGenerationGuide which the
user could just copy-paste.
I made one of those some time ago for BincIMAP and while the wiki it
lived
to decrypt old data to re-encrypt with the new key, right?
Correct.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
On 11.01.2010, at 17:28, Jean-Michel Pouré wrote:
Le lundi 11 janvier 2010 à 16:17 +0200, Martin Paljak a écrit :
Definitely not. You might find glitches and shortcomings with
pkcs11-tool but that would just benefit OpenSC as we could see the
problems and fix them.
Sorry to insist, but from
.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
but I've not used it because I managed to lock it up. A
friend of mine lately complained that OpenSC did not work for him either..
There have been no real developments on the driver for years and not many posts
on the mailing list either...
Cheers,
--
Martin Paljak
http://martin.paljak.pri.ee
and user
database hassle altogether.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
to be changed.
In this case the 'pOldPin' argument is the unblocking code.
For me it's quite logical, because, as you've told,
we do not have or cannot use the actual PIN value.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
On 04.01.2010, at 12:33, Viktor TARASOV wrote:
Martin Paljak wrote:
Hi.
There seem to be two targets:
a) How to accomplish all functionality via PKCS#11 interface
b) How to remain compatible with as many as possible / select existing
application implementations.
...
I propose
(Apple Inc. build 5646)]
Enabled features: zlib readline iconv openssl
pcsc(/System/Library/Frameworks/PCSC.framework/PCSC)
It could be aliased (or renamed) to --version
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel
, see http://www.opensc-project.org/opensc/ticket/71
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
it's up to you to find the change which causes the problem.
Regards,
Dominik
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http
/opensc/browser/trunk/src/pkcs11/pkcs11-session.c?rev=3862#L344
Why does it need (#if 0)?
See svn blame: r164. No further comments needed I guess.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel
eID in card-ias.c
http://www.opensc-project.org/opensc/browser/branches/martin/0.12/src/libopensc/card-ias.c?rev=3755#L207
Martin.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc
that still implement the
old style API of change_reference_data and verify instead of sc_pin_cmd. In
fact, new drivers have been added without the pin_cmd interface but the old
interface.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
and
libopensc-ctapi is that it is not realistic to have the hotpluggin feature work
with different subsystems.
Any thoughts on this?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc
, cache it in a single location, usable by
all layers above libopensc by same mechanism
2. Allow to personalize a card with all PIN-s going through a pinpad.
1. is possible, but 2 via PKCS#11 might be a problem, if a card requires
several times a PIN for a single operation...
--
Martin Paljak
you have a patch with these changes or it is just a suggestion?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
and
this has been asked by people as well.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
http://javacardsign.sourceforge.net/
PKCS#15 compatible open source applet. Has anyone on this list tried
it out?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http
and/or distro packaging. But making it clear
what gets used is definitely a good thing.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org
On 01.11.2009, at 13:16, Ludovic Rousseau wrote:
Any objection to use PC/SC by default (again)?
None.
And +1 for making openct conflict with libccid as well.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing
(as
seen on list)
Thanks,
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
On 29.10.2009, at 12:26, Johannes Becker wrote:
NSPlugin support:no
Do you miss it or expected that it would be available? It will be
removed from opensc, as it is not part of core functionality of opensc.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
On 26.10.2009, at 12:22, Martin Paljak wrote:
As I've also written a web signing plugin for Firefox/Opera/Safari I
can say it has changed from Netscape plugins to a more useful,
cross-browser API. I don't know if the current signer can do it. But
it's not trivial, for example on OS X
On 26.10.2009, at 12:35, Diego Elio “Flameeyes” Pettenò wrote:
Il giorno Mon, 26/10/2009 alle 12.22 +0200, Martin Paljak ha scritto:
So it seems we have a nsplugin user and new developer?
Do you use it? Would you be willing to maintain/develop it?
Actually, no to all counts.
I just
. p15emu-westcos.c. Problem: consistent naming. Rest of the emulation
drivers use pkcs15-name.c As there are pkcs15-foo.c files in src/
libopensc that deal with other tasks than emulation, maybe push the
emulation drivers into a subdirectory for clarity?
--
Martin Paljak
http://martin.paljak.pri.ee
that happens, we can provide a separate .pkg
with OpenSSH+PKCS#11, maybe even include it as an optional install
inside a package named OpenSC (which, clearly, it is not really part of)
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
better go into 0.12
development,
or else we will have two branches for a long time.
what does everyone else think about it?
Start with a 0.12 tree and stop pushing the limits of 0.11 other than
for security/stability issues.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
On 22.10.2009, at 0:01, Andreas Jellinghaus wrote:
Am Mittwoch 21 Oktober 2009 15:19:07 schrieb Martin Paljak:
1. For starters, we should rename the main slogan of OpenSC to
something that's more up to date. The supported cards list could
either be generalized or at least updated:
http
-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo
-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
at pkcs15-tool -D and
then pkcs#11 debug log?
Thanks,
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
(there are anyway things that should be changed in the
SM code as well)
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
to display more info about
the ATR/card.
Cool!
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
is not identified.
Maybe keep the input bar on the parse page as well, so that a new ATR
could be entered at once. Also, it would be better if the input field
was just a looong single line, from left side to right side of the
browser window.
--
Martin Paljak
http://martin.paljak.pri.ee
= (struct
pkcs15_pubkey_object*) object;
- struct pkcs15_cert_object *cert = pubkey-pub_cert;
+ struct pkcs15_cert_object *cert = pubkey-pub_genfrom;
struct pkcs15_fw_data *fw_data = (struct pkcs15_fw_data *) session-
slot-card-fw_data;
size_t len;
--
Martin Paljak
to be guaranteed.
I believe it is OK to assume that one of these pre-requisites (pubkey
or certificate) is fulfilled. It should work for most users, until the
problem arises and somebody proposes a fix/patch.
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
that bytes B2..0 are 0 bytes of data.
What do you think?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
/branches/martin/0.12/src/libopensc/apdu.c
if SC_APDU_CASE_3_SHORT and apdu-datalen == 0 and
apdu-lc == 0 then no error? Why?
Thanks
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc
Bonjour,
On 02.10.2009, at 13:45, Ludovic Rousseau wrote:
Hello,
2009/10/2 Martin Paljak mar...@paljak.pri.ee:
Maybe we should try
working with apple to get libopensc and the tokend to be included
in OSX?
http://smartcardservices.macosforge.org/ leaves me the impression
that
maybe
, send either openct or ccid+pcsc-lite logs.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
requires
hackery to build a Tokend), what is OK IMHO.
Thoughts?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
.
pkcs15-init knows this argument:
--format, -f argSpecify key/cert file format: PEM
(=default), DER or PKCS12
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
that does not yet have
any use outside of a single card driver.
Worked for me/EstEID as well otherwise.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc
then the emulation layer
information can be translated to lower flags. Check
SC_PIN_CMD_NEED_PADDING and SC_PKCS15_PIN_FLAG_NEEDS_PADDING for
inspiration.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
you use? Do you get a successful
PIN entry if you modify the code?
You can try the branches/martin/0.12 source, it adds a new field to
opensc-tool -l to display pinpad capabilities of the reader.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
On 18.09.2009, at 12:02, Andreas Jellinghaus wrote:
Am Donnerstag 17 September 2009 10:41:56 schrieb Martin Paljak:
I'm not an expert on pkcs15init nor know the historical and
philosophical reasons for the separation between libopensc and
pkcs15init.
I guess noone is. lets considere
through the pages and make a new page for your card. Try to make
it better than existing ones :) At least include some technical
details, where to buy a card, some things a user might need to know
when using the card or personalizing it.
Cheers,
--
Martin Paljak
http://martin.paljak.pri.ee
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
Hi,
2009/9/15 Aktiv Co. Aleksey Samsonov samso...@guardant.ru:
BUG: serial-len is used uninitialized in
rtecp_card_ctl:SC_CARDCTL_GET_SERIALNR (src/libopensc/card-rtecp.c)
Could you please add attached patch?
r3739, thanks.
Martin
___
opensc-devel
to be
able to pass more information.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
- sc_error() - sc_debug()
- instead of 0 return SC_SUCCESS where applicable
Also please prepare a wiki page with information about the card, where
to buy it, where it is used, can the applet be used with any Java card
etc.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
a single project / API / library
a bunch of cards instead every card making its own mycard-pkcs11.so,
the same should be followed in command line utilities.
What do you think?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc
information to be
useful. In normal situations everything should just work and no debug
log generated at all, but when things break it is always the best to
have as much logs as possible.
Thoughts?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
by Martin) to the Snow Leopard versions:
Security.framework
SecurityTokend.framework
security_cdsa_client.framework
security_cdsa_utilities.framework
security_utilities.framework
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc
-devel
--
Sent from my mobile device
Martin Paljak
http://martin.paljak.pri.ee
GSM:+3725156495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
functions
can't be implemented via pkcs15init interface (like -G)?
Some places still need more English.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http
On 11.09.2009, at 12:52, Andreas Jellinghaus wrote:
Hi Martin,
I saw you created a 0.12 branch for you.
instead we could create a 0.11 maintenance branch
(new driver and small fixes only), and commit your
work (e.g. debug cleanup etc.) on trunk.
OK.
Andreas, Aleksey
and Alan (thank you for your remarks).
This patch concern only the support of westcos card. As far as
concern the
integration in basecsp it will come later.
I hope to forget nothing...
François.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
that there is anything (except minor issues) that can
prevent including your patch in OpenSC trunk.
What do you think about this? Do you think that opensc can become a
standard in cryptographics use?
To some extent it is a standard/default solution, depending on the
requirements.
--
Martin Paljak
http
for linking into the basecsp dll.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
that can create such signatures, should be
sophisticated enough to be aware of the fact that every signature
requires a PIN verification (whatever API it uses). I don't think it
is a problem that needs to be fixed on OpenSC level.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
.
Initialization probably means C_Initialize - pkcs15_bind() which
takes a lot of time indeed (it reads out certificates for example).
There are some small optimizations I've tried to speed things up, but
no real good stuff yet.
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
--
Sent from my mobile device
Martin Paljak
http://martin.paljak.pri.ee
GSM:+3725156495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
somebody finds some use to the driver.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel
-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
create a dedicated EF into my card and
create all pkcs15 structure on it? Must I create all the
architecture of pkcs15 into my card? My card is read only.
If your card is read only = you can not create (==write) stuff.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
as a spring cleaning effort.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http
.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
.max_length)
return SC_ERROR_INVALID_ARGUMENTS;
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
I was wrong about the contactless thing:
On 08.04.2009, at 15:42, JP Szikora wrote:
Martin Paljak a écrit :
In fact, I guess it is safe to say that OpenSC does not currently
support in a documented way cards with contact-less interfaces.
I might be wrong of course, in that case please
the
PIN is re-validated and everything works as expected for example)
I'm not a strong believer that the suppress_errors mechanism actually
helps in those cases - it makes it just more complicated. In languages
with exceptions, you get a trace only if you don't handle the exception.
--
Martin
://wiki.github.com/martinpaljak/opensc.tokend
should get you up and running on leopard.
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman
syslog calls in a custom build?
You can run the PIV tokend in debug mode but that won't help you, as
there is no way you can modify the PIV tokend.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc
on the card.
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
0x45 + count(existing_keys) ?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
On 06.03.2009, at 17:18, Alon Bar-Lev wrote:
2009/3/6 Martin Paljak mar...@paljak.pri.ee:
SCardControl talks to reader drivers, not pcsc-lite or pc/sc
subsystem in
that matter.
3400 was the original reference number in teletrust (which later
became
PC/SC v2 part 10 which deals
the
required header? Is there a reason why it is not included or could
someone more familiar with mingw open a ticket?
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http
with binary builds as well.
You also need to run ./bootstrap to generate the configure script and
you'll need auto* tools (from fink) and pkg-config for this to work.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel
know for sure that OpenSC
based code is used by (tens of) thousands of people in Estonia alone
and other EU countries as well.
Talking about revolutions - last time it happened OpenSC was split
into different packages...
cheers,
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
corner case to deal with OS X makes the
code any simpler or common.
m.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
On 28.01.2009, at 14:46, Alon Bar-Lev wrote:
On 1/28/09, Martin Paljak mar...@paljak.pri.ee wrote:
You could blame Apple for this, but in real life there are many
such tweaks
in OS X.
Sure I can blame apple. PC/SC is Microsoft API, the API is fixed and
apple cannot modify entry points
machie and place it in OPENSC_TARGET_ROOT.
Compared to SCA installer, this means /Library/OpenSC
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc
not be provided
separately.
I routinely build on OS X and as of now there are no problems with
OepnSC + PCSC + OpenSSL + zlib + iconv.
--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495
___
opensc-devel mailing list
opensc-devel@lists.opensc
On 30.12.2008, at 21:28, Alon Bar-Lev wrote:
On 12/30/08, Martin Paljak mar...@paljak.pri.ee wrote:
The PKCS#11 specification does not limit concurrent application
access
to single token in any point in time.
The lock term was introduced by OpenSC due to implementation choice
#29 but you might be
interested in
http://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/a776fe268d149b57
as well.
Basically, v2.20 mode should be the default but there are some kinks
to be ironed out first.
--
Martin Paljak
http://martin.paljak.pri.ee
GSM:+3725156495
the code defaults.
cheers,
--
Martin Paljak
mar...@paljak.pri.ee
http://martin.paljak.pri.ee
GSM:+3725156495
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
Does anyone know of any real life readers that have multiple slots and
where the OpenSC driver (ctapi most probably) would show them as
slots, not as different readers?
http://www.opensc-project.org/opensc/changeset/2111
--
Martin Paljak
http://martin.paljak.pri.ee
GSM:+3725156495
. For
emulated cards, this option should not matter.
I thus propose the attached patch.
BTW, am I the only one having problems with opensc-commit list? I have
received only 2 mails from it in the past week.
--
Martin Paljak
mar...@paljak.pri.ee
http://martin.paljak.pri.ee
GSM:+3725156495
Index: src
701 - 800 of 891 matches
Mail list logo
