> On Mar 20, 2010, at 21:11 , Alejandro Vargas wrote:
> > Hello. I an trying to get working a binary card driver for a different
> > version.
> >
> > The driver is for the spanish DNI and it is distributed as a binary
> > file, then I cannot re-compile it. Then I think I could build a dummy
> >
Finally, here it is:
http://www.dnie.es/descargas/codigo_fuente.html
According to:
http://www.kriptopolis.org/disponibles-fuentes-pkcs11
Seems that code doesn't include component private key to establish secure
channel,
but I thing that it can be found in other software (java/windows) provided
In Spanish, sorry :-(
http://www.kriptopolis.org/disponibles-fuentes-pkcs11#comment-56793
In this article I've done a preliminar analisys of provided source code for
Spanish
DNIe OpenSC driver
http://www.dnie.es/descargas/codigo_fuente.html
In a nutshell: won't run without additional work
- N
As you can see at Kriptopolis web site
http://www.kriptopolis.org/disponibles-fuentes-pkcs11
A lot of job has been done !in just 2 days!
At this moment we have two independent working developments
from DGP provided code. So we can confirm that code is valid and
works fine
Next comes:
- Getting rp
Spanish Direccion General de la Policía has released a new
version of their DNIe opensc module... under GPLv3+ license
http://www.dnie.es/descargas/codigo_fuente.html
That makes several interesting (and problematic) issues:
As LGPL states, LGPL code can be promoted to GPL, but the
reverse is not
Mensaje original
De: mar...@paljak.pri.ee
Fecha: 24/06/2010 10:27
Para: "Juan Antonio Martinez"
CC: "Alejandro Vargas",
"opensc-devel@lists.opensc-project.org
devel", "Malcolm
Bain"
Asunto: Re: [opensc-devel] Changes on Spanish DNIe licensing
[]
> > As Direccion General de la P
hi folks!
We have tried to compile, install and get running OpenSC 0.12 with Spanish DNIe
code.
Status: compile,installs, but fails to run trying to stablish secure channel.
Too many changes
in debug code, sc_xxx structs, API changes... and not sure about correctness of
some patches I've done
> CIE does not use "Secure Channel" implementation by means of secure
> messaging, at least not for normal use of the card (which carries only
> Authentication Certificates and not Non-Repudiation, so it is not used
> to create legally binding Electronic Signatures).
> The version in trunk is cov
Martin:
here comes another (more verbose) 0.12.0-svn log
from other system and reader ( towitoko-openct serial reader
+plus openct-pcsc bridge )
In this case SM channel is created fine, but seems that
reader gets into an unstable state and card_transmit_apdu()
returns continuous fails
I'll check
Sorry for this horrible translation but no time for goodness...
http://www.kriptopolis.org/opensc-dnie-linux#comment-58005
---
The good news:
Using github Martin's repository, whit recent changes, and providing
correct SM keys:
> The bad news:
> When enabling opensc-pkcs11 in firefox. the program needs too many time
> to start. when going to DGP web page for DNI verification, ask for pin
> but hangs till message: "sec_error_pkcs11_general_error" appears.
> Hung is so big that i need to unplug-plug card reader and restart
Mensaje original
> De: alejandro@gmail.com
> Fecha: 12/09/2010 12:09
> Para:
> Asunto: Re: [opensc-devel] Rv: OpenSC-0.12.0 and Spanish DNIe
> 2010/9/10 jons...@terra.es :
> > I've checked this behaviour in the same computer and three different card
>
Perhaps anyone can help me:
Now that my DNIe has died [1] I'm trying to get dni code to be aware of this
situation.
¿What's the standard way to tell libopensc that a card has been invalidated?,
that is: the card is recognized,
but cannot operate with it because manipulation detected, too many
[...]
> > Not sure on other cards, but DNIe mark this situation by mean of
> > change on ATR status code from 03 90 00 to
> > 0F 65 81 (Memory error). Not sure what to do if detected this
> > situation:
> 1. When data structures of your card are still readable, then match on
> both ATRs. And fail
[...].
> Supposed that the attached log file is complete, then the card fails on
> receiving the first APDU. In this case the card provides only it's ATR
> and nothing more. This makes it less useful and thus I would prefer to
> ignore such a card.
You're right. after some test I conclude that ca
A very good news:
At Spanish DNIe Site [1] guys from TechOffice [2] have published the Developers
reference guide for the DNIe. Contains Documentation !And SM keys! enought to
create an independent development of DNIe pkcs#11 module
Documentation is distributed by mean a sort of Apple/Android I
Working with Spanish DNIe code, I've received some feedback [1] from Dirección
General
de la Policía about removal of "user consent" code on signature process
Afaik this theme has been discussed at OpenSC [2]. As a result, user consent
code
was removed from OpenSC. Same was for opensc-signer mo
Oops!! there are some obvious errors in attached code ( "module" instead of
"card_driver",
card context null checkings and so )
But It's just an idea :-)
Juan Antonio
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opens
> > Hello Nikos,
> > AFAIK only RSA is supported by OpenSC.
> Is this a design decision or a limitation of the supported cards?
Just natural evolution of OpenSC: first cards only supported RSA
See thread at opensc-devel list:
http://www.opensc-project.org/pipermail/opensc-devel/2010-October/0150
Working in OpenDNIe [1] code I've found a problem. How to send a verify() cmd
throught Secure Channel when pin is to be keyed by mean of a reader with
pinpad.
My feeling is that this is not possible: OpenSC handles pinpad at reader level.
The only way to insert pin from pinpad into SM is that
In Fedora 14 (that ships OpenSSL-1.0.0b) seems that EC support is not built in
OpenSSL package
-
Making all in tools
make[3]: se ingresa al directorio
`/home/jantonio/work/dnie/cenatic/opendnie/opensc-dnie/trunk/src/tools'
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -pth
More info:
Seems that Fedora removes all ECC related issues due to patents problems:
https://bugzilla.redhat.com/show_bug.cgi?id=615372
¿How these problems could affect OpenSC?
Perhaps we could do some kind of conditional compilation to take care on this
Juan Antonio
_
Mensaje original
De: mar...@paljak.pri.ee
Fecha: 03/12/2010 9:48
Para:
CC:
Asunto: Re: [opensc-devel] r4904 and OpenSSL-1.0.0b in Fedora 14
> OPENSSL_VERSION_NUMBER >= 0x1000L && !defined(OPENSSL_NO_EC) is
> the key,
> Douglas hopefully plans that into the next patch unless
Mensaje original
De: deeng...@anl.gov
Fecha: 03/12/2010 16:18
Para:
Asunto: Re: [opensc-devel] r4904 and OpenSSL-1.0.0b in Fedora 14
Commited r4906 to test for OPENSSL_NO_EC, and opensslconf.h is included.
Please verify id Fedora now compiles.
Just a simple patch to get it right:
---
Mensaje original
De: mar...@martinpaljak.net
Fecha: 24/01/2011 12:46
Para: "OpenSC-devel (opensc-devel)"
Asunto: Re: [opensc-devel] [opensc-commits] Fwd: IAS sucks
[...]
> One of the longstanding problems of OpenSC is lack of documentation, both
> developer
> (source comments, interna
Hi All:
I've concluded that DNIe card is not so pkcs15 compliant as promissed...
I think I need rewriting of several file permissions and paths, as information
provided in card pkcs15 structure seems to be wrong or incomplete
I've studying the source code of provided drivers, but still unsure o
> Mensaje original
> De: andre.zepeza...@student.uni-halle.de
> Fecha: 03/02/2011 13:06
> Para:
>CC:
> Asunto: Re: [opensc-devel] DNIe driver: Needs Information on writing
> pkcs15- files
>On Thu, 2011-02-03 at 12:03 +0100, jons...@t
In the testing process of OpenDNIe I've found a problem related with concurrent
access to opensc-pkcs11 library.
In short: as DNIe can only handle one SM at a time (no virtual channel
support),
there is no (known) way to get concurrent pkcs11 access
This "feature" makes unusable most of signin
Hi all.
Trying to optimize DNIe card driver, I'd like to cache current df to avoid
extra select_file()'s
DNIe card cannot handle select_file(SC_PATH_TYPE_PATH) directly: it has to be
splitted into
recursive calls to select_file(SC_PATH_TYPE_FILE_ID).
Studying other card drivers i figure that
>On Sunday, March 27 at 01:42PM, Viktor TARASOV wrote:
>> > http://www.opensc-project.org/opensc/wiki/SecureMessaging
>>
>> I've added my vision onto the SM implementation .
>> Still to be finalized the proposal for the SM data types.
>> I'll try to look over the prior works to see how their need
1- An stupid bug in piv-tool.xml:
[jantonio@jonsy trunk]$ diff ../../../opensc/doc/tools/piv-tool.xml
doc/tools/piv-tool.xml
22c22
<
---
>
-
( a missing start tag )
2- Not sure about the usage of card reader "black list" on broken readers:
What
2011/3/30 jons...@terra.es :
> > In my case Spanish C3PO's LTC31 (reported name 'C3PO LTC31 00 00' ) claims
> > for
> > having pinpad support but I'cannot see any pinpad :-)
>
> Can you send me the output.txt file for this reader as documented at [
Some notices on compile for windows under Fedora 14
Using r5283 and install instructions from wiki:
http://www.opensc-project.org/opensc/wiki/WindowsInstaller
1- In file win32/installer_from_build.sh
Fedora mingw compiler uses a different name:
-
# Ubuntu 10.10 (a
> Mensaje original
>De: jons...@terra.es
> Fecha: 31/03/2011 13:15
>Para:
>Asunto: [opensc-devel] Compiling for windows in Fedora 14
>
>Some notices on compile for windows under Fedora 14
Sorry: I forgot last notice:
My Fedora installation has default lan
>
>Hello,
>On Mar 31, 2011, at 14:22 , jons...@terra.es wrote:
>> Sorry: I forgot last notice:
>> My Fedora installation has default language set to "ES", so wine looks
>> for iscc.exe at
>>
>> ${HOME}/.wine/drive_c/Archivos de programa/Inn
(Apologizes if this is not the proper list to ask for )
What's the current status of CSP - support for OpenSC?
OpenSC-pkcs11 works fine for me in windows, but I'd like
to use not only pkcs11based tools but csp based apps too
I've tried some binaries from OpenSC links [1] without success
Any (w
BTW: what's the current state of cardmod?
Is it usable? Any instructions?
Juan Antonio
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
A little patch to "installer_from_build.sh" script to use correct mingw prefix
on win32 builds
Requires "lsb-core" package Ubuntu- or "redhat_lsb" -redhat/fedora-
-
# use mingw to generate binaries
+DistID=`lsb_release -is`
+case $DistID in
+Fedora ) p
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 = $(srcdir
(oops: forgot to CC to list :-)
Mensaje original
De: jons...@terra.es
Fecha: 25/04/2011 14:30
Para:
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 ab
> Mensaje original
> De: mar...@martinpaljak.net
> Fecha: 27/04/2011 7:21
> Para: "Juan Antonio Martinez"
> CC:
> Asunto: Re: [opensc-devel] pkcs15-tool --read-public-keys
[]
> > Ok, I finally did it. pkcs15-tool -D no longer shows "public keys"
> > on my DNIe card
> >
> > pkcs15-
Hi, Viktor:
> [...]
> > > Provide functions for start/stop/testAndSet SM
> > New card member 'SM context' will be added to sc_card structure.
> > There will be the placeholder for the SM related card/exrternal-module
> > handlers, session data, etc.
> > Every one will find the possibility to imp
> Mensaje original
> De: viktor.tara...@gmail.com
> Fecha: 31/05/2011 14:45
> Para:
> CC:
> Asunto: Re: [opensc-devel] RV: SM and remote data svn commits
>
> Hello Juan Antonio,
[...]
> Le 31/05/2011 13:02, jons...@terra.es a écrit :
> > Hi, Viktor:
&g
(Happy Holidays, Martin :-)
I'm working around ticket #232[1], (GUI related functions), but need a
consensus about
what is exactly needed [2]
- At least two functions are required
* Enter pin
* Confirm Operation
* ¿Any other?
- Should I take care on i18n?. Notice that other parts on OpenSC (eg
> Mensaje original
> De: ludovic.rouss...@gmail.com
> Fecha: 24/06/2011 14:13
> Para:
>Asunto: Re: [opensc-devel] About ticket #232 (portable gui)
>
>Hello,
>
>2011/6/24 jons...@terra.es :
>> I'm working around ticket #232[1], (GUI related fun
45 matches
Mail list logo
