On Wed, 23 Jun 1999, Bodo Moeller wrote: > This depends on how you define "properly written", obviously. If you yes. but in order to make the OpenSSLifying of existing applications simpler, it would be nice to follow the semantics of normal socket calls. then you can start using OpenSSL just be inserting some initialization code at the beginning of the program and by replacing all calls to read/write to SSL_read/SSL_write. but if you must rewrite the internal logic of the application (buffer management, etc) in order to do so, then the conversion to secure sockets is quite time consuming. arne ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
- Re: cvs commit: openssl/util libeay.num Anonymous
- Re: cvs commit: openssl/util libeay.num Anonymous
- Re: cvs commit: openssl/util libeay... Anonymous
- Re: cvs commit: openssl/util li... Anonymous
- Re: cvs commit: openssl/uti... Anonymous
- Re: cvs commit: openss... Bodo Moeller
- Re: cvs commit: op... Arne Ansper
- Re: cvs commit... Anonymous
- Re: cvs commit: openssl/util libeay.num Dr Stephen Henson
- Re: cvs commit: openssl/util libeay... Arne Ansper
- Re: cvs commit: openssl/util libeay.num Ulf Moeller
- Re: cvs commit: openssl/util libeay... Ben Laurie
- Re: cvs commit: openssl/util libeay.num Richard Levitte - VMS Whacker
- Re: cvs commit: openssl/util libeay.num Richard Levitte - VMS Whacker
- Re: cvs commit: openssl/util libeay.num Richard Levitte - VMS Whacker
- Re: cvs commit: openssl/util libeay.num Geoff Thorpe
