| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
256
|
Fri Mar 21 16:24:05 2003 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Elog and SSL |
> I was wondering if you can help me understand the concept and if i am doing
> something wrong with securing Elog via SSL
>
> Basically im running elog on a redhat 8 box with stunnel already installed
> as part of OpenSSL, on the server i ran the command specified in the
> instructions
>
> stunnel -d 443 -r 172.16.24.108:81
>
> This command runs on the server, but when I access https://172.16.24.108/ i
> get a page cannot be displayed, ive also put the URL =
> https://172.16.24.108 entry in the elogd.cfg file
>
> HELP!!!!!!!
Can you access your server locally under http://172.16.24.108:81 ??? If not,
then you maybe specified the wrong port, so check elogd.cfg and the "-p" flag
when starting elogd. If you can access it, and cannot access it under
https://, then something must be wrong with your stunnel configuration. Maybe
you run already a secure server under port 443? User "netstat -a" to check
that. |
|
255
|
Thu Mar 20 21:07:09 2003 |
| djek | djek@nospam.invalid | Bug report | | | Re: Elog 2.3.3, problems of 2.3.2 solved |
> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> >
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
>
> If you installed from the RPM, elogd runs under the user "elog". If you have
> installed a previous version under a different user, it might be that elogd
> does not have read or write access to it. A
>
> "chown -R elog.elog /usr/local/elogdata"
>
> might help.
>
It did, a lot, guess I missed that one in the changelog.
Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked
As a test I changed subdir to it's relative path
restarted
It kept working
mmmm, I wonder where that twighlight tune comes from ... |
|
254
|
Thu Mar 20 21:07:09 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Elog 2.3.3, problems of 2.3.2 only partly solved |
> After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> as stylesheets, images or passwordfiles.
>
> Cannot open file /usr/local/elogdata/logbooks/djeks/password!
If you installed from the RPM, elogd runs under the user "elog". If you have
installed a previous version under a different user, it might be that elogd
does not have read or write access to it. A
"chown -R elog.elog /usr/local/elogdata"
might help.
- Stefan |
|
253
|
Thu Mar 20 21:07:09 2003 |
 | djek | djek@nospam.invalid | Bug report | | | Elog 2.3.3, problems of 2.3.2 only partly solved |
After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.
Cannot open file /usr/local/elogdata/logbooks/djeks/password!
oops? |
|
249
|
Sun Mar 16 19:15:16 2003 |
 | Recai Oktas | roktas@omu.edu.tr | Info | | | Elog and SSL |
> Basically im running elog on a redhat 8 box with stunnel already installed
> as part of OpenSSL, on the server i ran the command specified in the
> instructions
>
> stunnel -d 443 -r 172.16.24.108:81
I haven't tried `stunnel` with elog, but as far as I read from various
sources, stunnel requires you to create an SSL certificate. In attachment,
you'll find a sample case for stunnel and smtp (port 25) + pop3 (port 110).
Hope this helps.
Reference: http://www.tldp.org/linuxfocus/common/sart/index.html |
| Attachment 1: stunnel_with_smtp_pop3.txt
|
EZ Email Security With Stunnel
by Pat Parsons
This is a little crash course in how to setup email over SSL painlessly using
Stunnel. First you need to have installed a mail transfer agent to handle the
SMTP portion of the mail. Then you need to have installed either an IMAP server
or a POP3 server. Many distributions come with Stunnel, if yours does not you
can get it from http://www.stunnel.org. Stunnel requires that you have OpenSSL
or SSLeay installed first. This should come with your distribution. Generally
if you have SSH installed you also have a SSL library.
Get and install Stunnel. I am not going into detail on that because if you are
at this point you probably already know how to do so. Make a SSL certificate
for use with Stunnel. OpenSSL provides a makefile to do just that. In my
distribution it is located in /usr/share/ssl/certs . CD to that directory and
type make stunnel.pem to create the certificate that is named stunnel.pem. Now
you need to a few lines to your rc.local file to start Stunnel at bootup
(assuming you ever reboot that is) these lines are:
/usr/sbin/stunnel -d 995 -r 110
/usr/sbin/stunnel -d 465 -r 25
This will start stunnel listening on port 995 for POP3 and 465 for SMTP. Now
all you need to do is edit the options for your mail client and there you go.
No need to worry about cleartext email passwords. If you are too impatient to
wait for the next reboot you can type the commands given previously to start
Stunnel right away. There may be some problems with certificate validation for
some email clients. Make sure when asked by the makefile you get the server
name correct. If your email client will not let you add certificates you may
need to change or obtain a certificate from a certification authority. If you
cannot get the certificate vaidation worked out there is no way to ensure that
you are connecting to the correct machine. Have a nice day.
|
|
248
|
Fri Mar 14 10:30:25 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Problems with 2.3.2 |
> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> > port bindings, basically im running elog bound to port 81 and when i
> > install the new RPM it refuses to bind to this port, i tried port 8080
and
> > that worked fine
The bug has been fixed in V 2.3.3 which has been released today. |
|
247
|
Thu Mar 13 17:33:58 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Problems with 2.3.2 |
> Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> port bindings, basically im running elog bound to port 81 and when i
> install the new RPM it refuses to bind to this port, i tried port 8080 and
> that worked fine
>
> Any ideas ?
This is a bug I discovered myself just today, so we are working on it. I
expect this to be fixed by tomorrow or somewhen during this weekend.
- Stefan |
|
246
|
Thu Mar 13 17:30:16 2003 |
| nick | nick@nick.com | Bug report | | | Problems with 2.3.2 |
Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
port bindings, basically im running elog bound to port 81 and when i
install the new RPM it refuses to bind to this port, i tried port 8080 and
that worked fine
Any ideas ? |