Andreas Jellinghaus wrote:
> document this hack and good? very few people have the problem you mention
> so I think it is good enough?
This is the same issue I have with openct and the automatic detection
of pcsc-lite. If it's possible to use openct without pcsc-lite and this
is a supported confi
On 7/20/07, Nils Larsch <[EMAIL PROTECTED]> wrote:
could you send me the opensc debug log (including the APDUs
send to the card) ?
I guess you mean the attached?
If not, please send me some instructions.
Best Regards,
Alon Bar-Lev.
[pkcs15-init] ctx.c:704:sc_context_create: ===
Alon Bar-Lev wrote:
> Hello,
>
> I am trying to use the new Athena support, it is my first attempt to
> use opensc as a native driver so I may got this wrong.
>
> I don't see that there are traces more than the --verbose flag.
> The "File not found" result is common to any PIN I write.
> The card
Andreas Jellinghaus wrote:
> On Wednesday 18 July 2007 22:27:06 Nils Larsch wrote:
>> IMHO the right way to fix this would be to tell the profile
>> layer to use the decryption operation for signing and not to
>> modify the card driver.
>
> I don't know about the profile layer, so I implemented a
On 7/20/07, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> On Friday 20 July 2007 20:41:52 Alon Bar-Lev wrote:
> > No...
> > Please explicitly add --enable-nsplugin or something.
> > So that if you add dependency no additional hacks will be nessesery.
>
> ok. thanks, commited.
There is another i
On Friday 20 July 2007 20:48:12 Douglas E. Engert wrote:
> Dmitry Zhigulin wrote:
> > Douglas E. Engert anl.gov> writes:
> >> Can you use C_Verify instead?
>
> I meant as a stating point to write the missing C_Encrypt code for OpenSC
> pkcs11.
issue solved, opensc does not automatically use decry
On Friday 20 July 2007 20:41:52 Alon Bar-Lev wrote:
> No...
> Please explicitly add --enable-nsplugin or something.
> So that if you add dependency no additional hacks will be nessesery.
ok. thanks, commited.
> > sorry, I have little clue about the plugin, I even think I never used it
> > myself
Dmitry Zhigulin wrote:
> Douglas E. Engert anl.gov> writes:
>
>> Can you use C_Verify instead?
I meant as a stating point to write the missing C_Encrypt code for OpenSC
pkcs11.
>>
>
> How to use it for encryption, may you show example?
>
> I found in pkcs11-tool example - function "encrypt
On 7/20/07, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
what happends if you run LIBASSUAN_CONFIG=/bin/false ./configure
?
Oh...
For now, I've used --with-libassuan-prefix=tmp
document this hack and good? very few people have the problem you mention
so I think it is good enough?
No...
Pl
Andreas Jellinghaus dungeon.inka.de> writes:
>
> Peter Koch might be interested, he wrote drivers for all other german
> signature cards, but those were TCOS/NetKey cards.
>
> Documentation etc. would be always welcome.
>
By the way, maybe anybody have additional documentation for German Off
On Friday 20 July 2007 16:15:29 Alon Bar-Lev wrote:
> Yes it does.
ok, good.
what happends if you run LIBASSUAN_CONFIG=/bin/false ./configure
?
I get an ugly warning from configure output, but it seems to work fine.
Thus I can disable libassuan without any need for special options.
does it work
Traced the problem to:
src/pkcs15init/pkcs15-asepcos.c::asepcos_check_verify_tpin::
sc_profile_get_file_by_path
Having the function return success on error, I tried to return
SC_SUCCESS anyway...
Got:
Unspecified PIN [reference 0] required.
Please enter Unspecified PIN [reference 0]:
[pkcs15-init]
On Friday 20 July 2007 16:29:44 Dmitry Zhigulin wrote:
> Andreas Jellinghaus dungeon.inka.de> writes:
> > Dmitry: can you try this? you would need to checkout svn trunk and
> > compile it yourself. it works for me (pkcs15-crypt and pkcs11-tool on a
> > siemens initialized card).
>
> All right, Sig
Andreas Jellinghaus dungeon.inka.de> writes:
>
> On Thursday 19 July 2007 09:57:31 Dmitry wrote:
> what is the name of the low level crypto implementation by microsoft?
pkcscsp use default PROV_RSA_FULL CSP.
> or do you think that many appliations will fail, if such a CSP is installed?
Mayb
Andreas Jellinghaus dungeon.inka.de> writes:
>
> Dmitry: can you try this? you would need to checkout svn trunk and compile
> it yourself. it works for me (pkcs15-crypt and pkcs11-tool on a siemens
> initialized card).
>
All right, Sign and Verify is working correctly.
Only little problem w
On 7/20/07, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> if you don't have libassuan installed, then opensc should compile
> fine (and not create the plugin). does that work for you?
Yes it does.
But if I have gnupg install, I already have libassuan, it does not
suggest I want to use it with O
Hello,
I am trying to use the new Athena support, it is my first attempt to
use opensc as a native driver so I may got this wrong.
I don't see that there are traces more than the --verbose flag.
The "File not found" result is common to any PIN I write.
The card was previously formatted by Athena
[opensc-pkcs11] asn1.c:1172:asn1_decode: mandatory ASN.1
object 'publicKeyCoefficients' not found
[opensc-pkcs11] asn1.c:1184:asn1_decode: returning with: Required ASN.1 object
not found
[opensc-pkcs11] pkcs15-pubkey.c:256:sc_pkcs15_decode_pubkey_rsa: ASN.1 parsing
of public key failed: Required
Andreas Jellinghaus dungeon.inka.de> writes:
>
> Documentation etc. would be always welcome. Could you create a wiki page and
> link or attach every information you have? That is not a guarantee that
> anyone will write a driver, but without documentation etc. noone can do that
> for sure.
>
On Thursday 19 July 2007 09:57:31 Dmitry wrote:
> Peter Stuge cdy.org> writes:
> > If it doesn't however, directly calling OpenSC would be useful.
> > But in that case, why not do away with CryptoApi completely?
>
> Some theory:
>
> As tells http://msdn2.microsoft.com/en-us/library/ms953432.aspx
>
On Fri, Jul 20, 2007 at 02:39:17PM +0200, Andreas Jellinghaus wrote:
> or do you need an option for those who have it installed (including
> development files), and try to compile opensc, but don't want opensc
> to automatically compile the plugin during that?
Good point, --enable- and --disable-
On Friday 20 July 2007 14:19:48 Alon Bar-Lev wrote:
> In next version, can you please add --enable-plugin so that the plugin
> will be built/installed only if requested?
> I don't see many people using it, and the libassuan, pinentry
> dependency can be dropped.
>
> There is also an issue of text r
On Wednesday 18 July 2007 22:27:06 Nils Larsch wrote:
> IMHO the right way to fix this would be to tell the profile
> layer to use the decryption operation for signing and not to
> modify the card driver.
I don't know about the profile layer, so I implemented a crude
hack, which is not too bad I h
On Friday 20 July 2007 12:01:19 Gürer Özen wrote:
> > > I guess, allocation size was supposed to be objlen + 1 ?
> >
> > Yep it seems so, attached patch fixes this problem.
>
> But introduces another problem, string length is reported one byte bigger,
> so here is the more correct fix :)
thanks, c
On Thursday 19 July 2007 12:45:23 Gürer Özen wrote:
> new version:
> * create_file implemented
> * EF(DIR) hack removed, it is easier to put a real EF(DIR)
> * SC_CARDCTL_GET_SERIALNR implemented
thanks, commited.
Regards, Andreas
___
opensc-devel maili
On Friday 20 July 2007 01:30:21 Siddhartha Kasivajhula wrote:
> But if I make an attempt at initializing the card ("pkcs15-init
> --create-pkcs15", as per the "QuickStart" tutorial on the OpenSC site), it
> fails to initialize the card after the "Enter key(default:):" step
> (which is expected, I g
Hello Andreas,
On 7/17/07, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> OpenSC - new version 0.11.3
In next version, can you please add --enable-plugin so that the plugin
will be built/installed only if requested?
I don't see many people using it, and the libassuan, pinentry
dependency can be
On Friday 20 July 2007 11:00:17 Dmitry Zhigulin wrote:
> When OpenSc will provide suuport of Seccos? At least rough terms.
when someone writes code for it. I'm not aware of anyone working on it.
> I have SECCOS Bankensignaturcart card (as told SecCardAdmin).
> It has German Office Identity Card,
On Friday 20 July 2007 12:52:40 Gürer Özen wrote:
> On Thursday 19 July 2007 01:10:33 Gürer Özen wrote:
> > asn1_decode_entry() allocates (objlen - 1) bytes for SC_ASN1_UTF8STRING
> > types with SC_ASN1_ALLOC flag, then calls the sc_asn1_decode_utf8string()
> > function which then fails with BUFFER
On Thursday 19 July 2007 01:10:33 Gürer Özen wrote:
> asn1_decode_entry() allocates (objlen - 1) bytes for SC_ASN1_UTF8STRING
> types with SC_ASN1_ALLOC flag, then calls the sc_asn1_decode_utf8string()
> function which then fails with BUFFER TOO SMALL cause it wants to end the
> string with an extr
When OpenSc will provide suuport of Seccos? At least rough terms.
I have SECCOS Bankensignaturcart card (as told SecCardAdmin).
It has German Office Identity Card, HBCI, GelteKarte applications.
So, maybe possible create emulation for it, for example throw OIC,
OS documentaion available in Web.
Nils Larsch gmx.net> writes:
> IMHO the right way to fix this would be to tell the profile
> layer to use the decryption operation for signing and not to
> modify the card driver.
>
Thanks,
So, I need just test if card is cardos, certificate support encryption and use
C_DecryptInit/C_Decrypt i
32 matches
Mail list logo