RE: NO_BIO

[Tim Michals]

Title: NO_BIO

Liming,

 

No hard drive, we are using a primitive flash file system.  Just didn't what to start reading and writing to flash a lot.  I also found the same issue, it is hard to pull out some of the modules to make the library smaller.

 

Tim

-----Original Message-----
From: Liming Sun [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 28, 2001 10:58 AM
To: '[EMAIL PROTECTED]'
Subject: RE: NO_BIO

HI, Tim.  This morning, I tried to compile using NO_BIO and then found that there is really no easy way that I can get rid of BIO altogether. Examples, I would need to redefine BIO_flush, BIO_read(), BIO_write(), etc.

 

I do not know what you mean by an issue with have no File System.

 

Cheers

 

/liming 

-----Original Message-----
From: Tim Michals [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 28, 2001 8:24 AM
To: '[EMAIL PROTECTED]'
Subject: RE: NO_BIO

I've also ported to VxWorks, but I was having an issue with have no File System, did you over come this issue?  I was compiling with NO_BIO, NO_STDIO

 

T

-----Original Message-----
From: Liming Sun [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 28, 2001 3:38 AM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: NO_BIO

Good day, all.

(1) I compiled OpenSSL-0.9.6b in vxWorks.  When using it, a server receives clientHello from client and it looks ok.  But when the server flushes serverHello, Certificate, and KeyExchange, and serverHelloDone back to the client, the server crashes at sock_write(). I used SnifferPro to monitor traffic on the client side and found that client received most part of the data from server. When processing the received data, the client also crashes inside BIO_read().  Any suggestions?

(2) Because of (1), I am trying NOT to use BIO interface in OpenSSL.

It appears that SSL_set_fd(SSL *s,int fd) allows me to connect socket directly to SSL object (without using BIO interface).  But a closer look at SSL_set_fd()implemenation tells me that BIO is still used between SSL layer and socket. 

So, how do I use the flag NO_BIO (does it really mean no BIO interface between socket and SSL)?

Thank you very much for your suggestions and have a nice day.

/liming

--------------------------------------------------------------------------------

From: Tim Michals
Subject: Questions about NO_BIO and NO_STDIO
Date: Mon, 17 Sep 2001 06:03:27 -0700

--------------------------------------------------------------------------------

All,

I'm trying to build the cryptolib without file access(fopen, fclose, etc)
and general tty. The main reason for this, trying to use a small embedded
OS, that is very primitive and does not have a Unix file system interface. 

The certificate file will be stored in non-volatile ram.  The applications
I'm trying to use are LDAP (OpenLDAP) and web server (Goahead). So this
helps limit issues with the test and example apps.

 Noticed some defines NO_BIO and NO_STDIO but if these are defined it causes
some errors during compile. 

Some of the issues:
        - in the bio directory bss_file (it loads and manage the certificate
files)  I can hack a fix but concerned about a reason if a file needs to be
created?  What be the case for creating a file for ssl?
        - in the crypto directory read_pwd.c uses tty to read the password.

Any insight?

Thanks