Allow specifying application name for data objects at pkcs15-init.
[[The change from memcmp to strcmp is valid as in this case the
data is not oid]]
Alon Bar-Lev
svn diff -r 3280:3282
https://www.opensc-project.org/svn/opensc/branches/alonbl/opensc-data
---
Index: opensc-data/src/tools/pkcs1
Return CKR_PIN_INCORRECT and not CKR_ARGUMENTS_BAD
at C_Login when PIN length is out of range, as PIN
must be incorrect, and applications are not expected
to follow PIN limitations on user entry. They
Do epxected to do so when they set a new PIN, and
for this reason we have CKR_PIN_LEN_RANGE out
o
PKCS#11 "Application and processes" instructs the sequence
that should be taken after fork().
Applications should call C_Initialize() immediately after fork()
to reinitialize the provider.
The change monitor the pid that calls C_Initialize(), if it is
different than previous C_Finalize() is calle
Complete rewrite of OpenSC build system.
1. Build system now supports MinGW (Windows) compilation using msys and cross
compilation.
2. Ability to explicitly disable and enable dependencies of the package.
3. openct, pcsc and nsplugins features are disabled by default.
4. Modified pcsc driver to
Convert constant SC_PKCS11_MAX_VIRTUAL_SLOTS to configuration option.
Alon Bar-Lev
svn diff -r 3283:3284
https://www.opensc-project.org/svn/opensc/branches/alonbl/pkcs11-slots
---
Index: pkcs11-slots/src/pkcs11/pkcs11-global.c
==
Commited in [3400]
Thanks!
On Feb 29, 2008, at 10:35 AM, Alon Bar-Lev wrote:
>
> Return CKR_PIN_INCORRECT and not CKR_ARGUMENTS_BAD
> at C_Login when PIN length is out of range, as PIN
> must be incorrect, and applications are not expected
> to follow PIN limitations on user entry. They
> Do epx
Hi Ivars,
yes I am using SCB v0.9 , but only certain parts of it; this probably
explains why I have not seen this issue...
the OpenSSL issue is due to the fact that
- SCB is compiled against openssl 0.9.8e
- OpenVPN is compiled against openssl 0.9.7m
There is no easy way around it other than
- bu
I already done this...
I am waiting for the test results of [1].
Alon.
[1] http://alon.barlev.googlepages.com/opensc-mingw-openssl-0.9.7.tar.bz2
On 2/29/08, Jan Just Keijser <[EMAIL PROTECTED]> wrote:
> Hi Ivars,
>
> yes I am using SCB v0.9 , but only certain parts of it; this probably
> expl
On Tue, Feb 12, 2008 at 2:00 PM, Ludovic Rousseau
<[EMAIL PROTECTED]> wrote:
> A complete patch is attached.
>
> sc_asn1_decode_integer() should still decode INTEGERs encoded with the
> old/bogus encoding function.
>
> If nobody complains I will commit the patch.
Patch commited in revision 340
