RE: SFL 1.8 and the SNACC v1.3 R4 ASN.1 compiler

Bob:

Yes, I found the same error; I tracked it down to something in the
certificate itself.  Since this particular certificate was encoded in our
early SFL days, I simply removed it from any references in the config files
rather than waste time on the details.  The code works fine for all other
RSA certificates (I started using the better built DaisyRsaExts certificate,
using the same public key).  I had thought I had removed the DaisyRsa
certificate from the test directory; I will re-check.  Sorry about the
confusion.

Bob Colestock

-----Original Message-----
From: Bob Smith [mailto:[email protected]]
Sent: Thursday, October 26, 2000 1:29 PM
To: [email protected]
Subject: SFL 1.8 and the SNACC v1.3 R4 ASN.1 compiler



Has SFL 1.8 been tested with the SNACC v1.3 R4 ASN.1 Compiler? I'm having 
problems when I use sfl 1.8 and the snacc v1.3 R4 at the 
GLOBALAddLoginFinish function. It seems that DECODE_BUF in 
CSM_Free3::DecodeCertificate does not work properly when I'm using the 
DaisyRSA.out certificate found in the test folder. DecodeCertificate does a 
memory overrun and then when the GLOBALAddLoginFinish function tries to 
clean up its memory, deleting the m_pSNACCCert variable of in the 
CSM_CertificateChoice destructor causes a memory overrun error.

I also tried using SFL 1.7 and SNACC v1.3 R4 and I got an access violation 
at DECODE_BUF when I call CSM_Free3::AddLoginStatic in SM_FREE3.



_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.