John, thanks for your reply. The first time I installed stunnel, and older
version a year or so ago, I compiled from sources etc.. However, this time
i took the easy way out and downloaded from redhat the rpms for both openssl
9.5a and stunnel 3.8-4. I have been thinking that I just do not have the
pem's etc in the right directory that stunnel is looking for. I have tried
using a server.pem, server.crt, swat.pem in /etc/ssl/certs /var/ssl/certs
(which is where I think older version had them) and in /usr/share/ssl/certs
which is where doing a stunnel -h says the default directory is. All to no
avail.
Nothing is showing up in the syslogs at all for stunnel. When using the
Opera browser 4.2 connecting to swat it just says "connection closed by
remote server" . In reading the stunnel docs, I have also tried getting the
c_hash of stunnel.pem, swat.pem and linking those, still to no avail. Any
other ideas?
Richard Curtis
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 01, 2000 5:00 am
To: [EMAIL PROTECTED]
Subject: RE: after install of mod-ssl, stunnel broken
You don't mention if you changed your version of Openssl in installing
mod-ssl, which I suspect you did. If so, that can stop stunnel working as it
is usually linked against a specific version of either SSLeay (is anyone
actually using that anymore?) or Openssl.
I had this problem for a while till I recompiled stunnel against the source
tree of the same version of Openssl. Check your syslog for a definitive
answer as stunnel should be logging any failures there.
I use stunnel for SWAT and mod_ssl on the same machines without any
problems.
-
John Airey
Internet Systems Support Officer, ITCSD, Royal National Institute for the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED]
-----Original Message-----
From: RCURTIS [mailto:[EMAIL PROTECTED]]
Sent: 01 November 2000 01:45
To: '[EMAIL PROTECTED]'
Subject: after install of mod-ssl, stunnel broken
I have been using stunnel on an apache 1.3 webserver to connect to the web
interface of SAMBA called SWAT.� After install of mod-ssl, I cannot connect
via https: to SWAT i.e.� https://xxx.xxx.xxx.xxx:901
<https://xxx.xxx.xxx.xxx:901> ���� If connecting to swat outside stunnel,
all works fine.� Any ideas as to what the mod-ssl install changed or how to
make it so that I can continue to use stunnel to connect while at the same
time using mod-ssl on the web server?� Any help appreciated ..�� Thanks!
�
Richard Curtis
[EMAIL PROTECTED]
�
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
