Hi Friends,
Can any body help me out to get the MS Visual Studio Workspace of
OpenSSL ?
Regards,
Abhishek
Good Evening folks:
If someone could push (or kick) me in the right direction, that would be
much appreciated.
I have a single threaded test application (Red Hat Linux release 9 -
Shrike), OpenSSL 0.9.8. I found that it's possible to permanently hang
a thread receiving SSL calls if a networ
I have a single threaded test application (Red Hat Linux release 9 - Shrike),
OpenSSL 0.9.8. I found that it's possible to permanently hang a thread
receiving SSL calls if a network interruption occurs during an established
connection.
This is the way TCP works. There's a couple of min
Hi Jim - thanks for the reply. See comments in-line
Jim Fox wrote:
I have a single threaded test application (Red Hat Linux release 9 -
Shrike), OpenSSL 0.9.8. I found that it's possible to permanently
hang a thread receiving SSL calls if a network interruption occurs
during an established
On Thu, Jul 19, 2007 at 03:54:55PM -0400, Jim Marshall wrote:
> Hi Jim - thanks for the reply. See comments in-line
> Jim Fox wrote:
> >
> >>
> >>I have a single threaded test application (Red Hat Linux release 9 -
> >>Shrike), OpenSSL 0.9.8. I found that it's possible to permanently
> >>hang a
Hello,
> i find an information about add new chipers BF-CBC but find nothing.
> may be somone ever find thid?
Look at:
http://www.openssl.org/docs/crypto/blowfish.html#
for low-level API, or use:
EVP_CIPHER_CTX_init(&ctx);
EVP_EncryptInit_ex(&ctx, EVP_bf_cbc(), NULL, key, iv
Once a TCP session is in the Established state, it stays that way
until a FIN or RST is received from the opposite host, or if a
packet times out. This is the purpose of keepalive. However,
the default time for keepalive is a system wide setting and is
usually very long, and may not be appropriat
Victor Duchovni wrote:
On Thu, Jul 19, 2007 at 03:54:55PM -0400, Jim Marshall wrote:
I'm also not sure I understand your answer "This is the way TCP works".
When we disconnect the network cable the connection never times out (we
left it for at least 30 minutes).
TCP only disconnects quickly
Date: Thu, 19 Jul 2007 16:09:59 -0400
From: Jim Marshall <[EMAIL PROTECTED]>
To: openssl-users@openssl.org
Reply-To: openssl-users@openssl.org
Subject: Re: How to prevent SSL from blocking from Network interruption
Victor Duchovni wrote:
On Thu, Jul 19, 2007 at 03:54:55PM -0400, Jim Marshall
> We are working on a threaded solution but right now we are using some
> third-party code (Webs 2.18) which is single threaded.
That's fine, but if you using blocking calls in a single-threaded
application, you can really only handle one client at a time.
> I'm also not sure I understand your a
David Schwartz wrote:
We are working on a threaded solution but right now we are using some
third-party code (Webs 2.18) which is single threaded.
That's fine, but if you using blocking calls in a single-threaded
application, you can really only handle one client at a time.
I know :( Which is w
Jim Marshall wrote:
David Schwartz wrote:
OpenSSL tries to make SSL connections act like regular TCP
connections. This
is exactly what TCP does. So your application would have this exact same
problem with or without OpenSSL. As such, how can you blame it on
OpenSSL?
Not to beat a dead horse,
On Jul 19, 2007, at 9:45 PM, Jim Marshall wrote:
Jim Marshall wrote:
David Schwartz wrote:
OpenSSL tries to make SSL connections act like regular TCP
connections. This
is exactly what TCP does. So your application would have this
exact same
problem with or without OpenSSL. As such, how can
Hi there,
Just curious if anybody has done any profiling of openssl's memory
usage? Is there much heap contention? Has anybody tried plugging in a
3rd party memory manager such as Hoard, or SmartHeap to see if there is
any performance improvement?
Thanks,
Ed
14 matches
Mail list logo
