On Tue, 20 Jul 1999, Richard Levitte - VMS Whacker wrote:
> Bodo_Moeller> So, is backwards compatibility an important issue here
> Bodo_Moeller> and is it worth this kind of evil hack, or should we
> Bodo_Moeller> just add the parameters?
>
> Backward compatibility is an important issue. Think
On Tue, 20 Jul 1999, Bodo Moeller wrote:
> On Tue, Jul 20, 1999 at 01:20:52AM +0200, Richard Levitte - VMS Whacker wrote:
>
> >> So, is backwards compatibility an important issue here
> >> and is it worth this kind of evil hack, or should we
> >> just add the parameters?
>
> > Backward compatib
On Mon, Jul 19, 1999 at 07:41:34PM -0400, Timothy Canfield wrote:
> Is there anyway to optimize the connection overhead (connections from
> multiple clients)? I have been trying to download lots of small files
> from an in-house server. I get very poor throughput since the files are
> only abou
On Tue, Jul 20, 1999 at 01:20:52AM +0200, Richard Levitte - VMS Whacker wrote:
>> So, is backwards compatibility an important issue here
>> and is it worth this kind of evil hack, or should we
>> just add the parameters?
> Backward compatibility is an important issue. Think "dynamic
> library".
Bodo, thanks for your response. You're right, I wasn't aware of how
session caching is supposed to work.
Is there anyway to optimize the connection overhead (connections from
multiple clients)? I have been trying to download lots of small files
from an in-house server. I get very poor through
Bodo_Moeller> > Please find attached a patch against openssl-SNAP-19990718
Bodo_Moeller> > which modifies the pem/* stuff to take an extra
Bodo_Moeller> > argument of type void* to all the functions which use
Bodo_Moeller> > a password callback. It also modifies the apps/* to
Bodo_Moeller> > use t
I have a few questions (could not locate a FAQ)
1. Is there any support for SET certificates?
2. I assume that OpenSSL does not provide for
any certificate management, and this is
currently the domain of openca.org
Thanks!
Clark Evans
__
Damien Miller <[EMAIL PROTECTED]>:
> Holger Reif:
>> There has been a discussion on this recently. The conclusion was
>> it should be changed. I think it was even aggred on how to do
>> this. But I think nobody took the task of actually implementing
>> it. (Please correct me if I'm wrong!)
>>
>>
Timothy Canfield <[EMAIL PROTECTED]>:
> I have noticed that much of the overhead of an openssl session is during
> the connection stage. Is it possible for me to use only one SSL_session
> for every connection that which I accept. This will make it easier to
> crack a session, right? Will it a
According to brad:
>
> the problem i am having is when trying to use these shared libs with other
> applications. in particular, Trf 1.7, which is a Tcl extention.
i just solved my particular problem with libcrypto.so and solaris 7 x86
compiled with gcc 2.7.2.3. took me a while to find the off
I have noticed that much of the overhead of an openssl session is during
the connection stage. Is it possible for me to use only one SSL_session
for every connection that which I accept. This will make it easier to
crack a session, right? Will it also make the connection overhead less?
If thi
hello,
has anyone successfully built the shared lib version of openssl 0.9.3a for
solaris 7 on intel? i've seen some things in the archive that were promising,
but nothing that has worked so far. i'm not even sure this is a problem with
the libcrypto.so right now, but that is the piece that is
I tried to compile OpenSSL under Win32 with the installation instruction
from mod_ssl 2.3.6 in Install.Win32. If you configure OpenSSL using "perl
Configure VC-WIN32 --prefix=D:\OpenSSL", it will produce an incorrect
makefile, which produces an error about incorrect escape sequences, as i
posted t
On Fri, 16 Jul 1999, Holger Reif wrote:
> There has been a discussion on this recently. The conclusion was
> it should be changed. I think it was even aggred on how to do
> this. But I think nobody took the task of actually implementing
> it. (Please correct me if I'm wrong!)
>
> AFAIR it was th
14 matches
Mail list logo