Hi Tiange,
Could you please do me a favour of telling me your
project settings to make it work in VC 7?
thanks!
hao
--- Si Tiange <[EMAIL PROTECTED]> wrote:
> Hi, I just tested demo\sign\sign.c. It works fine on
> my laptop.
>
> On 4/16/05, hao chen <[EMAIL PROTECTED]> wrote:
> > Hi Tiange,
> >
Hi, I just tested demo\sign\sign.c. It works fine on my laptop.
On 4/16/05, hao chen <[EMAIL PROTECTED]> wrote:
> Hi Tiange,
>
> I also would like to know how to add an option such
> that the built DLL has debug information.
> So far I did not write any code by using openssl. Just
> tried to run
Yes, I think I understand what you are saying. If I get a WANT_READ from a
call to SSL_write, that means I need to read some data before I can send.
But like you said, there may not be any data to read since the other end may
not have sent anything. But I think my problem was that I was thinking
As of 0.9.7g, is OpenSSL still not cancellation safe? If not, am I okay
to bracket calls into the ssl library by changing the cancellation
state (sort of like a mutex) reverting back on return from the library?
According to the pthreads documentation changing the cancellation state
should preve
You're on the money. This confused me, too. I had a program that needed
to see if there was incoming data, and so I performed an SSL_read(). I
received back a WANT_READ, because there was no data yet to read. (I'm
using non-blocking I/O).
But then some time later I needed to send data. The logi
Ok, this is getting much clearer. Last question (hopefully)...so if an
SSL_write gets a WANT_READ, is it ok for the read thread to do an SSL_read
before I retry the SSL_write? Does it matter who does the requested
operation as long as it is done? Or does the read thread have to wait until
the wr
Hi All,
I have used
SSLeay_add_all_algorithms();
on windows and it is working fine there, now when I try to use it on Red hat Linux
9 it hangs for infinite time, we want to use it on SUSE linux 8.2 as well.
I need to know how to avoid
this problem.
Regards,
Muhammad Af
I copied the do_crypt routine (General encryption, decryption function example
using FILE I/O and RC2 with an 80 bit key) from the EVP_EncryptInit(3) man
page and used it to encrypt a 433282 byte file. Function EVP_CipherFinal_ex
fails and ERR_get_error returns `error:0606506D:lib(6):func(101
> Thanks for this explanation. As I read more, I think I am
> getting a better
> understanding of this. So unlike normal tcp connections, where a
> read juts
> reads, and a write just writes, SSL_read may write, and SSL_write
> may read.
> This is all done under the hood, so I don't need to be c
