ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
219
|
Wed Feb 12 08:54:05 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Feature request | > > > Can you consider implementing the following additions to the
functionality
> > >
> > > 1) Subt on edit <attribute> = xyz
> > >
> > > This would be fantastic for implementing version control so you can see
> > who
> > > has edited a posted or a db entry.
> >
> > Can you give me an example of how you would use that?
>
> -----
>
> Lets say you are storing configuration information relating to a customers
> solution, you need the ability to track who has made what changes to the
> config information stored in the log book so you can backtrack who changed
> what and when, for example
>
> If you have a field name called Last Edited by this field is locked and not
> editable using the Lock attributes flag, but if you had Subt on edit
> everytime that entry is updated it places your login name into this field
and
> therefore stamps it to say you have edited it, as the field isnt free txt
it
> cant be spoofed as the $long_name comes from your login details.
Ok, I implemented "Subst on edit", it will be contained in Version 2.3.1
which is supposed to come out next week.
- Stefan |
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.
|
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. |
257
|
Fri Mar 21 16:52:12 2003 |
| Recai Oktas | roktas@omu.edu.tr | Info | | | Re: Re: Elog and SSL | Ooops, I destroyed the original post, now how can we fix this :) |
258
|
Mon Mar 31 12:44:33 2003 |
| nick | nick@nick.com | Info | | | Re: Elog and SSL | Im not running anything on port 443, one thing I did notice is that when
stunnel is run and setup, I can run a netstat and nothing is bound to those
ports, if I do a ps -ef | grep stunnel nothing is running, yet it accepts the
command initially ?
CONFUSED ????
> > 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. |
261
|
Wed Apr 2 16:36:18 2003 |
| nick | nick@nick.com | Info | | | Logbook Title bar | Is there a way to change the title entry for individual log books, and
forms ive completely rebranded our system but ut stil says ELOG ENTRIES on
the summary screen |
262
|
Wed Apr 2 21:45:18 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | | Re: Logbook Title bar | > Is there a way to change the title entry for individual log books, and
> forms ive completely rebranded our system but ut stil says ELOG ENTRIES on
> the summary screen
I changed the default title recently to "ELOG - <logbook>" where <logbook>
is the name of the current logbook. For the individual messages, the
title "ELOG" can be changed with the elogd.cfg option "Page title". This
title can even contain attributes from the logook entry like:
Page title = ELOG - $subject
where $subject gets replaced by the subject of the logbook entry. |
263
|
Thu Apr 3 09:40:45 2003 |
| nick | nick@nick.com | Info | | | Re: Logbook Title bar | > > Is there a way to change the title entry for individual log books, and
> > forms ive completely rebranded our system but ut stil says ELOG ENTRIES
on
> > the summary screen
>
> I changed the default title recently to "ELOG - <logbook>" where <logbook>
> is the name of the current logbook. For the individual messages, the
> title "ELOG" can be changed with the elogd.cfg option "Page title". This
> title can even contain attributes from the logook entry like:
>
> Page title = ELOG - $subject
>
> where $subject gets replaced by the subject of the logbook entry.
I have those attributes already working for example
[global]
Page title = Customer Relational Management System < this sets the selection
page ok
[Config DB]
Page Title = ABC123 - $Customer Name < this sets the individual log book
entries title
I need something to set the title of the page when on the summary page for
the logbook, as it just says ELOG - Config DB (this isnt set anywhere) |
|