pkcs15: for 'sc_pkcs15_cer's data use the 'der' object type

To hold the raw certificate blob in 'sc_pkcs15_cert' data use the 'sc_pkcs15_der' data type.
also:
; in 'pkcs15-cert.c' use short call of the debug messages;
; in 'destroy-object' pkcs15 framework handler take into account the multi-application cards:
-- when binding card use the application info;
-- when finalizing profile use the application ID.
pkcs11: unlink 'pubkey' FW object when deleting related certificate

Thanks to Andreas Schwier.
http://www.opensc-project.org/pipermail/opensc-devel/2012-September/018455.html

In PKCS#11 FW, the 'certificate' FW object is used to create corresponding 'public'key' FW object
or to get some of its attributes.
Seg.fault occured when, in the same session, the related certificate was destroyed and after that
there was the attempt to get such public key attributes.
pkcs11-tool: Fixed issue with ID increment failing on constant data
pkcs15: Fixed typo
pkcs15: Add support to encode EC private key description
framework-pkcs15: Fixed issued with uninitialized variable keysize
ecc: Adding more curves
framework-pkcs15: Fixed a SIGV when key generation returned ERROR_NOT_SUPPORTED
sc-hsm: Added write support for RSA and ECC keys, certificates and data objects
MSI: illegal caracters in component ID

OpenSC.wxs(168) : error CNDL0014 : The Component/@Id attribute's value, 'sc-hsm.profile', is not a legal identifier.  Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.).  Every identifier must begin with either a letter or an underscore.
entersafe: Disable RSA:512bits that modified in entersafe_generate_key and entersafe_store_key function

1.Added a prompt while initializing ePass2003 \n 2.Modify code to disable 512bit key
pkcs11: Fixed SIGV when deleting public key objects via PKCS#11

Thanks to Andreas Schwier.
build: release candidate 0.13.0 RC1
pksc11: Added ability to indicate hardware and firmware version information at PKCS#11 interface
sc-hsm: Added ability to initialize SmartCard-HSM using C_Initialize and C_InitPIN on PKCS#11 interface
move CK_VERSION data from 'pkcs15' to 'sc-card'

CK_VERSION is included into PKCS#11 data but is not specified by PKCS#15.

CK_VERSION can be provided by card's pkcs15 emulator or by the card's driver,
including the cards with the native support of pkcs#15 (and thus without pkcs15 emulator).

That's why the more general solution is to have these data included into 'sc-card' data type.
pkcs15: use whe available the pkcs15 object content

when reading certificate, try to get the pkcs15 object's content
before reading the certificate file.
libopensc: increase maximum number of card drivers

http://www.opensc-project.org/pipermail/opensc-devel/2012-October/018552.html
Default driver is disabled on 0.13 because there are more drivers listed in ctx.c. (leonardo.schenkel@gmail.com)

SC_MAX_CARD_DRIVERS is increases from 32 to 48. It's not the best solution, but the most rapid.
Will be waiting for the better proposals.
gemsafeV1: set 'auth-method' for the emulated PIN PKCS#15 object
pkcs15-tool: for public key show the presence of 'direct' value