RE: Problems building sm_free3DLL project in SFL 1.6 by means of VC++6.0 SP3

-----Original Message-----
From: Colestock, Robert 
Sent: Monday, April 17, 2000 11:27 AM
To: Pawling, John
Subject: FW: Problems building sm_free3DLL project in SFL 1.6 by means
of VC++6.0 SP3

Gianluca:

The 1st one is easy; you have already done the hard part.  Unfortunately the
CertificateBuilder program must reference the CTILs directly; it cannot
create public/private keys through the general CTIL interface like the SFL
library.  This restriction requires that each CTIL be directly linked and
referenced uniquely for the various functions necessary to build the
private/public keys.  If you have already built the executable without
BSafe, then all you have to do now is remove the dynamic login references
from the "./data.d/LoginsAll,cfg" file.

By the way, the newest release project definitions contain a project
specific to Crypto++ only.  It sounds like you have already created such a
definition.

Our PKCS #11 CTIL development is on hold, the existing PKCS #11 CTIL
software is incomplete and only partially tested.  We have tested the
signature verification operations using a beta release of the Litronics
Maestro library and the Fortezza card.  ENCRYPTION HAS NOT BEEN COMPLETELY
IMPLEMENTED YET.  Even after we get the PKCS #11 CTIL operational, we will
have to develop the custom functionality to build public/private keys and
integrate this logic into the CertificateBuilder.  This will probably not be
developed for at least the next 3 months.

If you are interested in developing the necessary logic to create
public/private keys using the PCKS 11 CTIL, it would not be hard to develop.
Good examples exist in the sm_free3.cpp and sm_rsa.cpp source files
demonstrating how the Crypto++ library and BSafe library are used to build
the keys.  This custom library logic could easily be integrated into the
CertificateBuilder GUI with the appropriate #ifdef checks.  You could still
use the CertificateBuilder to construct and sign certificates using existing
public keys (or keys built elsewhere) using the PKCS-11 CTIL (loaded
dynamically, not public/private key generation capability).

Bob Colestock


-----Original Message-----
From: Gianluca Ramunno [mailto:[email protected]]
Sent: Saturday, April 15, 2000 12:25 PM
To: 'Colestock, Robert'; [email protected]
Cc: 'Pawling, John'
Subject: R: Problems building sm_free3DLL project in SFL 1.6 by means of
VC++6.0 SP3


The sm_free3DLL DLL was created.
Thank's Bob!
It works fine!
But I have another problem.

I apologie for my question if is off-topic for the mailing list. If yes,
please
tell me and I'll wrote directly to you.

When I try to build CertificateBuilder.exe, VC++ searches for sm_rsaDLL
library.
I have only Crypto++ 3.1 crypto library, so I have to build libraries and
tools
without linking other crypto libraries and relative CTILs.
Which way? How can I eliminate references to Bsafe and sm_rsaDLL libraries?

I tried to eliminate references to Bsafe and sm_rsaDLL libraries
(in C/C++ and Link Options for the CertiticateBuilder.exe project).
So building the application was OK, but when I run that app, it crashes
or gives me an error messagebox (attached)

It's possible that I'll try to use a smartcard reader with PKCS#11 interface
together with SFL libraries.
Again which way can I build SFL?

Thank's
Gianluca