1 Dec 2001 02:08
3 Dec 2001 10:55
Hi All!
Vlad Vetiul <Vlad.Vetiul <at> bnm.org>
2001-12-03 09:55:31 GMT
2001-12-03 09:55:31 GMT
Hi All! When I try to open "smime.dsw" or any other *.dsw file from SMIME distribution (even 2.0) MS Studio 6 doesn't show anything in these workspaces. No projects, no files, no classes, absolutly nothing. It even doesn't say that something is wrong (actually it says nothing at all). Then I tried to open *.dsp files and result was the same. What's going on? Obviously it isn't normal, but I can't say what is wrong. Anyway, *.dsp files refer to *.mak files. But I didn't found any of these *.mak files. I know, there are makefiles, but they are intended for UNIX not for Windows. Is it really no other way to build SMIME library for Windows, except creating a totally new project and including all necessary files manually (sounds scary for me) ? What sould I do? Can anyone help me with project files for Windows? Thanx for paying attention, Vlad Vetiul Senior Software Engineer National Bank of Moldova, IT Department
3 Dec 2001 17:48
RE: Hi All!
Colestock, Robert <Robert.Colestock <at> GetronicsGov.com>
2001-12-03 16:48:17 GMT
2001-12-03 16:48:17 GMT
Vlad: I just re-downloaded the getronics smimeR2.0.tar.gz file, extracted it using Winzip 8.0, then loaded it into MS Visual Studio 6.0 just fine. I have seen the symptoms you describe before, it had to do with the carriage control on the files. Check that your unzip/tar operation is not interfering with your workspace and project files. This will also interfere with our .cfg test files (if you happen to run them). Bob Colestock VDA -----Original Message----- From: Vlad Vetiul [mailto:Vlad.Vetiul <at> bnm.org] Sent: Monday, December 03, 2001 3:56 AM To: imc-sfl <at> imc.org Subject: Hi All! Hi All! When I try to open "smime.dsw" or any other *.dsw file from SMIME distribution (even 2.0) MS Studio 6 doesn't show anything in these workspaces. No projects, no files, no classes, absolutly nothing. It even doesn't say that something is wrong (actually it says nothing at all). Then I tried to open *.dsp files and result was the same. What's going on? Obviously it isn't normal, but I can't say what is wrong.(Continue reading)
5 Dec 2001 08:19
problem with compiling the testsrc under solaris
wooce <wooce <at> 21cn.com>
2001-12-05 07:19:32 GMT
2001-12-05 07:19:32 GMT
hi,
I downloaded the latest SFL2.0 source code and have compiled most of
the parts success.
but there's a problem with compiling testsrc, see below:
/home/wooce/SMP/SMIME/testsrc/hilevel>make
g++ -o autoHi
sm_Autohi.o -L../../lib -L../../../SMPDist/util/VDASnacc/cpplib/li
b -L../../../SMPDist/cml/lib -L../../libcert -L../../libCtilMgr -lsmutil -l
smfr
ee3 -lsmcommon -lcrypt -lsm -lasn1c++ -lsocket -lsocket
ld: fatal: library -lsmfree3: not found
ld: fatal: library -lsmcommon: not found
ld: fatal: File processing errors. No output written to autoHi
collect2: ld returned 1 exit status
make: *** [autoHi] Error 1
where i can find the source to make the libsmfree3.a and libsmcommon.a
library?
thank you and have a nice day,
Wooce.
5 Dec 2001 14:39
RE: problem with compiling the testsrc under solaris
Colestock, Robert <Robert.Colestock <at> GetronicsGov.com>
2001-12-05 13:39:49 GMT
2001-12-05 13:39:49 GMT
Wooce: I have checked the Makefile in the ./SMIME/testsrc/hilevel directory and could not find any uncommented references to -lsmcommon, it is obsolete. The makefile as-is does successfully build autoHi on both Linux and Solaris; I am assuming you had to modify the Makefile for some reason. The autoHi program does not reference the -lsm_frfee3 library (you will need it if you attempt to use this functionality, but it is dynamically loaded, not directly linked by autoHi). The -lsm_Free3 library is referenced by the autoAlg image, which does directly link to the crypto library. You may already be doing this, but... Have you performed the "make setup" in the ./SMIME root directory? This command should build the individual Makefile(s) from the Makefile.in delivered sources. If you need the sm_free3 library, you will need to download the smCTIR2.0.tar.gz file from the same site as the smimeR2.0.tar.gz archive. You will also need the crypto++ 4.1 library as described on the web page and the readme file(s). The sm_free3 Makefile will build a shared object on Unix/Linux (.so file) to be loaded by the autoHi test program. The ./SMIME/test/LoginsAlld.cfg file designates the .so file to load and the startup parameters (usually a PKCS12 file containing a certificate and private key). Bob Colestock VDA -----Original Message-----(Continue reading)
11 Dec 2001 18:18
Porting: sha.h/.cpp bug
Michael Wiedmann <michael.wiedmann <at> detewe.de>
2001-12-11 17:18:05 GMT
2001-12-11 17:18:05 GMT
Hi, I'm trying to port crypto++-4.2 for an embedded system and run into some trouble (to be honest, I face a lot of problems due to insufficient C++ features of the C++-compiler I have to use - anyway I'll give it a try). Here is one problem which should IMO be solved in the upstream sources: - sha.h/sha.cpp In "sha.h" the classes SHA512 and SHA384 are wrapped between "#ifdef WORD64_AVAILABLE / #endif", but in "sha.cpp" these preprocessor directives are missing, so I run into compiler errors because obviously my compiler doesn't support WORD64. If I wrap the definition of the two classes in "sha.cpp" with "#ifdef WORD64_AVAILABLE / #endif" I get rid of at least this compiler error. Or do I miss anything? Michael -- -- office: michael.wiedmann <at> detewe.de private: mw <at> miwie.in-berlin.de http://www.miwie.org/ mw <at> miwie.org
11 Dec 2001 18:39
Re: Porting: sha.h/.cpp bug
Michael Wiedmann <michael.wiedmann <at> detewe.de>
2001-12-11 17:39:24 GMT
2001-12-11 17:39:24 GMT
Michael Wiedmann wrote: > I'm trying to port crypto++-4.2 for an embedded system and run into some ... Sorry for the posting, this was the wrong mailinglistMichael -- -- office: michael.wiedmann <at> detewe.de private: mw <at> miwie.in-berlin.de http://www.miwie.org/ mw <at> miwie.org
28 Dec 2001 13:56
Certificate Builder
Christopher Brown <chris.j.brown <at> nist.gov>
2001-12-28 12:56:22 GMT
2001-12-28 12:56:22 GMT
Hi, I have compiled the SFL v2.0, but when I try to execute the Certificate Builder program under VS6 I receive the following error message: The CMLASN.DLL file is linked to missing export SNACCCPP.DLL:??1CSM_Exception <at> SCACC <at> <at> QAE <at> XZ What could be the problem? Thanx
28 Dec 2001 16:54
RE: Certificate Builder
Pawling, John <John.Pawling <at> GetronicsGov.com>
2001-12-28 15:54:18 GMT
2001-12-28 15:54:18 GMT
Christopher, SNACCCPP.DLL is included in the SMPDistSNACCWin1.3rn7.tar.gz file that is freely available from: <http://www.getronicsgov.com/hot/snacc_home.htm>. We have made significant enhancements to the CertificateBuilder utility since the v2.0 SFL release. We plan to deliver a new (v2.0.1) CML/SFL/ACL/Enhanced SNACC release in late January 2002 that will include CertificateBuilder enhancements and bug fixes. If you plan to use CertificateBuilder prior to late January, then please download the CertificateBuilder patch file available from: ftp://ftp.getronicsgov.com/ftpdrop/SFL/SFL_CertBldr_Patch5.zip. This patch file includes the majority of the CertificateBuilder enhancements made since the v2.0 SFL release. Please let us know if you require further assistance. =========================================== John Pawling, John.Pawling <at> GetronicsGov.com Getronics Government Solutions, LLC =========================================== -----Original Message----- From: Christopher Brown [mailto:chris.j.brown <at> nist.gov] Sent: Friday, December 28, 2001 7:56 AM To: imc-sfl <at> imc.org Subject: Certificate Builder Hi,(Continue reading)
Michael
RSS Feed