Steven J Sobol schrieb:
>
> On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
>
> > When a SSL connection is established, the server will only see the IP
> > address (or IP/Port address), therefore the https request is always
> > resolved to be for your "main" server.
>
> I have n
On Tue, 20 Jul 1999, Steven J Sobol wrote:
> On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
>
> > When a SSL connection is established, the server will only see the IP
> > address (or IP/Port address), therefore the https request is always
> > resolved to be for your "main" se
What is the correct way to set the ciphers you want to use?
Currently I'm doing this:
SSL_CTX_set_tmp_rsa_callback(ssl_ctx,tmp_rsa_cb)
where:
static RSA *tmp_rsa_cb(SSL *s, int export, int keylength)
{
static RSA *rsa_tmp=NULL;
if (rsa_tmp == NULL)
{
rsa_tmp=RSA_generate_key(keylengt
On Wed, Jul 21, 1999 at 09:27:09AM +1200, Juergen Rensen wrote:
> When a SSL connection is established, the server will only see the IP
> address (or IP/Port address), therefore the https request is always
> resolved to be for your "main" server.
I have no experience with named SSL virtual hos
Bodo Moeller wrote:
>
> /usr/lib/perl5 is a directory, not an executable (but why is /usr/lib
> in your PATH?). That is a known bug in Configure; to fix it, change
> Configure as follows:
>
> --- Configure 1999/06/09 23:29:23 1.102
> +++ Configure 1999/06/10 08:13:52 1.103
> @@ -753
morgan wrote:
>
> I set up some name based virtual hosts on a linux machine with apache.
> [..]
> The virtual host part
> works fine for all 3, however if I go to https://blah.company.com it
> serves up the document root pages for www.company.com instead!??!?!
IMHO you can't use name based virtu
When a SSL connection is established, the server will only see the IP
address (or IP/Port address), therefore the https request is always
resolved to be for your "main" server. You can either configure multiple IP
addresses or different IP address/Port combinations for multiple SSL sites
on th
For NetBSD, removing the -D_ANSI_SOURCE in the Configurate file fixed the
problem.
- Original Message -
From: Sarah Bateman <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 20, 1999 8:46 AM
Subject: Re: Problems building openssl 0.9.3a on Solaris 2.5.1 (and also
NetBSD 1.3.
Hello all. Two questions:
* Is there a group working on a SET
(Visa/Mastercard *sigh*) certificate
management solution?
* How do you all feel about Cleo?
Thanks!
Clark Evans
__
OpenSSL Project
I set up some name based virtual hosts on a linux machine with apache.
I want to get the virtual hosts to use the same certificate as the
"main" server (there is www.company.com as well as blah.company.com
and blahblah.company.com on the same machine) The virtual host part
works fine for all
Dear open-ssl experts,
Is there a way to create a certificate without PEM pass phrase?
By using the "CA.sh" script to create certificate, you will be prompt for
PEM phrase. It may be a good
idea, however, in the need for server re-boot (auto-boot) the server will pause
for user to enter password
hUnTeR <[EMAIL PROTECTED]>:
> I am trying to build openssl-0.9.3a on a RedHat 5.2 Linux 2.0.36 server
> and receiving a critical error, as follows:
>
> ~/temp/openssl-0.9.3a/ ./config --prefix=/usr/local --openssldir=/usr/local/openssl
[...]
> PERL =/usr/lib/perl5
[...]
> make: execvp:
KonectaNet <[EMAIL PROTECTED]>:
> I would love to have an answer for this one too
>> Has anyone had any success trying to compile
>> Net_SSLeay.pm V1.03 with openssl 0.9.3a.
>>
>> I have tried on HPUX 10.20 and Solaris 2.4 with pelr 5.005_02
>> and I get the same error message
Use a recent sn
James Webster wrote:
>
> Was there ever a resolution on this (I wasn't on the list when it was sent)? I'm
>seeing the same thing on i586-whatever-netbsd.
>
> Thanks,
> James
>
> > List: openssl-users
> > Subject: Re: Problems building openssl 0.9.3a on Solaris 2.5.1
> > From: [EMAIL
Stephen Henson wrote:
> Keith Johnston wrote:
> >
> > The encrypted format of the RSA private key looks like this:
> >
> > -BEGIN RSA PRIVATE KEY-
> > Proc-Type: 4,ENCRYPTED
> > DEK-Info: DES-EDE3-CBC,EBC485A7EC86234E
> >
[...]
> > -END RSA PRIVATE KEY-
> >
> > I'm trying to us
On Tue, Jul 20, 1999 at 02:36:54PM +0200, Bodo Moeller wrote:
[...]
> Programs that access that structure directly cannot reasonably expect
> binary compatability across library versions. Clean programs handle
> SSL_CTX's only as pointers. A problem is just that, in case the
> application is wr
Bodo Moeller wrote:
>
> On Tue, Jul 20, 1999 at 10:55:20AM +0100, Ben Laurie wrote:
> > Bodo Moeller:
>
> 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
On Tue, Jul 20, 1999 at 10:55:20AM +0100, Ben Laurie wrote:
> Bodo Moeller:
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
>>> li
On Tue, Jul 20, 1999 at 10:02:05AM +1000, Damien Miller wrote:
>>> Backward compatibility is an important issue. Think "dynamic
>>> library".
>> The funny thing here is that if we just add the parameters, then on
>> systems with "standard" calling convention old programs should run
>> without a
Hi Erik,
thanks for replying. I received your mail but not
via the list - it hasn't appeared there (yet) ...
Problem solved: As usual it was annoyingly
simple (and embarassing).
I was assuming that when I did a "make certificate"
the certificate in "/www/conf" would be altered,
but it wasn
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 compatibility is an importa
Richard Levitte - VMS Whacker wrote:
>
> 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 a
3moeller> > Backward compatibility is an important issue. Think "dynamic
3moeller> > library".
3moeller>
3moeller> The funny thing here is that if we just add the parameters,
3moeller> then on systems with "standard" calling convention old
3moeller> programs should run without any problems with
23 matches
Mail list logo
