Hello,
On Apr 25, 2011, at 11:09 , Stef Walter wrote:
I've heard that openct may not be that relevant any more, but in any
case here's an OpenCT patch to add support for the smart card reader in
my laptop.
Should I put this in the opensc trac, or does it go somewhere else?
The device you
Le 24/04/2011 23:45, NdK a écrit :
On 24/04/2011 14:18, Viktor TARASOV wrote:
It seems the root of the problem lies in the profile: changing
CRYPTO=$PIN to CRYPTO=NONE works around it, but it's surely sub-optimal.
What I wanted to say: shouldn't --insecure replace $PIN with NONE ?
For what
Although I am in favor of improving openct, I agree with Martin in this case.
The most CCID compliant library we have is libccid, first work out the
problem with libccid.
It may be that openct's CCID implementation works for you as it much
simpler and use smaller set of features.
On Mon, Apr 25,
Seems that make maintainer-clean forgets to delete trunk/MacOSX/Makefile.in
file
This patch does the work:
--- ../trunk/MacOSX/Makefile.am2011-04-21 11:33:09.0 +0200
+++ mine/MacOSX/Makefile.am2011-04-25 11:26:32.0 +0200
@@ -1,3 +1,4 @@
+MAINTAINERCLEANFILES =
Applied.
Thanks.
On Mon, Apr 25, 2011 at 12:39 PM, jons...@terra.es jons...@terra.es wrote:
Seems that make maintainer-clean forgets to delete
trunk/MacOSX/Makefile.in file
This patch does the work:
--- ../trunk/MacOSX/Makefile.am 2011-04-21 11:33:09.0 +0200
+++
(oops: forgot to CC to list :-)
Mensaje original
De: jons...@terra.es
Fecha: 25/04/2011 14:30
Para: mar...@martinpaljak.net
Asunto: Re: [opensc-devel] OpenDNIe project is now ready for public test
About User Consent AKA popping up notice windows about what the
user is about to
Dear friends,
pkcs15-tool --list-public-keys seems to return the list of available
public keys being registered on card as public keys. It does not include
the list of private keys. But some public keys can be derived from
private keys and thus are not listed.
Are there plans to modify
On 4/25/2011 12:40 PM, Jean-Michel Pouré - GOOZE wrote:
Dear friends,
pkcs15-tool --list-public-keys seems to return the list of available
public keys being registered on card as public keys. It does not include
the list of private keys. But some public keys can be derived from
private
On 25/04/2011 14:33, jons...@terra.es wrote:
I can figure out at least these different popups:
[...]
7 - You'are about to emit a digital signature. Please confirm operation
And, anyway, you expose yourself to malicious apps that ask for a crypto
pin and use it to sign a document... As long
Jean-Michel Pouré - GOOZE wrote:
It took me some time to understand that pkcs15-tool --list-public-keys
did not return all public keys. So I expect users to be lost.
We need one simple command returning precise information.
Yes and no. It's not bad to have low-level tools which are useless
Yes and no. It's not bad to have low-level tools which are useless
for end users. Those tools are very useful for developers.
[...]
Agree that end-user GUIs need more sophisticated functionality than
may be offered by most or even all existing OpenSC tools. But that
does not mean that
Hello,
2011/4/25 Jean-Michel Pouré - GOOZE jmpo...@gooze.eu:
pkcs15-tool --list-public-keys seems to return the list of available
public keys being registered on card as public keys. It does not include
the list of private keys. But some public keys can be derived from
private keys and thus
2011/4/25 Jean-Michel Pouré - GOOZE jmpo...@gooze.eu:
Le lundi 25 avril 2011 à 13:51 -0500, Douglas E. Engert a écrit :
But part of the derivation process may include additional parameters.
Thus the derivation may may not have been done when pkcs15-tool is run
or the key is only good why the
13 matches
Mail list logo
