is later unlocked.
Exact.
I'll take care about, thank you .
Great. Thanks!
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http://www.cendio.com
A: Because it messes up the order
On Mon, 14 Mar 2011 16:07:53 +0100
Viktor TARASOV viktor.tara...@opentrust.com wrote:
On 14.03.2011 15:38, Pierre Ossman wrote:
PS. Should OpenSC really try unknown applications at all? Seems like
it'll just cause random glitches.
As for me yes,
it has to be able to read any PKCS#15
this is an OpenSC bug.
The commit message talks about protected attributes and doesn't say
anything about this specific change. One guess is that this was a check
to see what was already parsed when the card is later unlocked.
Rgds
--
Pierre OssmanOpenSource-based Thin Client
like are sorted first, this code change makes
OpenSC actively choose the applications least likely to work. Not
exactly desired behaviour. :)
PS. Should OpenSC really try unknown applications at all? Seems like
it'll just cause random glitches.
Rgds
--
Pierre OssmanOpenSource-based Thin
On Thu, 2 Sep 2010 17:34:05 +0200
Ludovic Rousseau ludovic.rouss...@gmail.com wrote:
2010/9/2 Pierre Ossman oss...@cendio.se:
I noticed this documentation added in r4583:
* Each thread of an application shall use its own SCARDCONTEXT. On
* Windows the same SCARDCONTEXT can
On Fri, 3 Sep 2010 14:08:28 +0200
Ludovic Rousseau ludovic.rouss...@gmail.com wrote:
2010/9/3 Pierre Ossman oss...@cendio.se:
I'm not sure I think that's sufficient. Given that more or less every
call can potentially block, you generally want to run these things in
custom threads
blocking nature of this API).
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http://www.cendio.com
signature.asc
Description: PGP signature
#11 spec, what you're suggesting sounds to me like
it would break things. And to make things worse, it would probably have
a high risk of expending the PUK attempts (as the user would be feeding
it the PIN instead) and really screw the user over.
Rgds
--
Pierre OssmanOpenSource-based
Ludovic, you're listed as the author of unblock.py in pykcs11. Could
you give some input on this discussion?
On Thu, 3 Dec 2009 15:09:26 +0100
Pierre Ossman oss...@cendio.se wrote:
On Thu, 03 Dec 2009 14:57:34 +0100
Viktor TARASOV viktor.tara...@opentrust.com wrote:
Another possible
the PIN now that
it is locked?
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http://www.cendio.com
signature.asc
Description: PGP signature
pkcs15-tool --unblock-pin supports as it should work in the
same way.
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http://www.cendio.com
signature.asc
Description: PGP signature
#11 only has
two types of PIN, so SO PIN must be the PUK.
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http://www.cendio.com
signature.asc
Description: PGP signature
(CKU_SO) followed by
C_InitPin() is set in stone as we want to be compatible with what's
already out there.
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http://www.cendio.com
On Tue, 10 Nov 2009 18:48:21 +0100
Pierre Ossman oss...@cendio.se wrote:
I'm looking at implementing support for unblocking a locked PIN in my
application, but looking at OpenSC that doesn't seem to be possible. In
fact, there are a number of issues along the way.
I've had another look
On Wed, 2 Dec 2009 09:51:20 +0100
Pierre Ossman oss...@cendio.se wrote:
On Tue, 10 Nov 2009 18:48:21 +0100
Pierre Ossman oss...@cendio.se wrote:
I'm looking at implementing support for unblocking a locked PIN in my
application, but looking at OpenSC that doesn't seem to be possible
On Wed, 2 Dec 2009 12:48:56 +0300
Aktiv Co. Aleksey Samsonov samso...@guardant.ru wrote:
Pierre Ossman:
I've had another look at this and implemented a somewhat ugly hack to
provide this functionality. Basically C_Login will return success for
CKU_SO if it can't find an auth object
On Wed, 2 Dec 2009 16:05:13 +0300
Aktiv Co. Aleksey Samsonov samso...@guardant.ru wrote:
Pierre Ossman:
On Wed, 2 Dec 2009 12:48:56 +0300
Aktiv Co. Aleksey Samsonov samso...@guardant.ru wrote:
Pierre Ossman:
Comment away!
Please see:
http://www.opensc-project.org/pipermail/opensc
debug output. I found it helpful to see how the library chooses to
associate objects, even though it currently only prints the index
number.
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb
On Mon, 5 Oct 2009 11:28:12 +0300
Martin Paljak mar...@paljak.pri.ee wrote:
On 05.10.2009, at 11:01, Pierre Ossman wrote:
New attempt, this time against r3756 (r18006 was our internal repo,
for
those curious :)), as an attachment and without a signature on the
mail. Hopefully
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;
Rgds
--
Pierre Ossman
on there being either a public
key object or a certificate on the card that corresponds to the private
key, but that does not seem to be guaranteed.
Rgds
--
Pierre OssmanOpenSource-based Thin Client Technology
System Developer Telephone: +46-13-21 46 00
Cendio ABWeb: http
21 matches
Mail list logo
