Disappearing attachments, posted by Greg Siems on Wed Apr 2 05:39:45 2003
|
Let me start by saying that I really like ELOG-- it's a nice tool.
I'm trying out version 2.3.3. The problem that I'm having is with
attachments disappearing when I do the following:
1. create a new entry that contains one or more attachments.
2. verify that the new entry from step 1 saved correctly.
3. reply to the entry from step 1.
4. return to the entry from step 1 only to find the attachments gone.
The attachement files are still in the logbook directory, it's just that
they are no longer attached to the entry.
FWIW, I've attached the elog.config that I'm using...
Thanks,
Greg |
Re: Disappearing attachments, posted by Stefan Ritt on Wed Apr 2 10:15:22 2003
|
> Let me start by saying that I really like ELOG-- it's a nice tool.
>
> I'm trying out version 2.3.3. The problem that I'm having is with
> attachments disappearing when I do the following:
>
> 1. create a new entry that contains one or more attachments.
> 2. verify that the new entry from step 1 saved correctly.
> 3. reply to the entry from step 1.
> 4. return to the entry from step 1 only to find the attachments gone.
>
> The attachement files are still in the logbook directory, it's just that
> they are no longer attached to the entry.
This is a known problem and has been fixed in version 2.3.4, which has been
released today. To prove that it's working, I attached the current
elogd.cfg from this forum. |
Re: Disappearing attachments, posted by Justin Dieters on Sun Apr 13 14:32:52 2003
|
I am using 2.3.4 and I am still having this problem. If someone posts a
message with an attachment, and I then reply to that message, the attachment
gets 'deattached' from that message. However, the file is still in the
logbook directory, so it is possible to recover it, but it did cause a slight
panic the first time it happened :)
I see there is a 2.3.5 version now, but the changelog doesn't say anything
about this problem, so I have not tried it yet.
Is there a 'trick' to fix this problem?
EDIT: I noticed when I replyed to your message, your elog.cfg attachment is
no longer there. So it appears it's not fixed in 2.3.5 either..
> This is a known problem and has been fixed in version 2.3.4, which has been
> released today. To prove that it's working, I attached the current
> elogd.cfg from this forum. |
Re: Disappearing attachments, posted by Stefan Ritt on Mon Apr 14 11:04:52 2003
|
> I am using 2.3.4 and I am still having this problem. If someone posts a
> message with an attachment, and I then reply to that message, the attachment
> gets 'deattached' from that message. However, the file is still in the
> logbook directory, so it is possible to recover it, but it did cause a
slight
> panic the first time it happened :)
Uups, that is indeed a problem. I found that it was unrelated to the first
one, so it was there since quite some time now. I fixed it. It will come out
in 2.3.6 or can be obtained already now from CVS. It is trongly recommended
to upgrade all installations to avoid this problem. |
Re: Disappearing attachments, posted by Stefan Ritt on Mon Apr 14 11:05:17 2003
|
> > I am using 2.3.4 and I am still having this problem. If someone posts a
> > message with an attachment, and I then reply to that message, the
attachment
> > gets 'deattached' from that message. However, the file is still in the
> > logbook directory, so it is possible to recover it, but it did cause a
> slight
> > panic the first time it happened :)
>
> Uups, that is indeed a problem. I found that it was unrelated to the first
> one, so it was there since quite some time now. I fixed it. It will come
out
> in 2.3.6 or can be obtained already now from CVS. It is trongly recommended
> to upgrade all installations to avoid this problem.
Just as a test, I reply to my previous message... looks like it works. |
Re: Disappearing attachments, posted by Justin Dieters on Mon Apr 14 18:24:18 2003
|
EDIT: I downloaded the latest elogd.c from CVS, replaced the one from the
latest tar, and recompiled. Worked great!
Thanks for the prompt response, Stefan!
> > I am using 2.3.4 and I am still having this problem. If someone posts a
> > message with an attachment, and I then reply to that message, the attachment
> > gets 'deattached' from that message. However, the file is still in the
> > logbook directory, so it is possible to recover it, but it did cause a
> slight
> > panic the first time it happened :)
>
> Uups, that is indeed a problem. I found that it was unrelated to the first
> one, so it was there since quite some time now. I fixed it. It will come out
> in 2.3.6 or can be obtained already now from CVS. It is trongly recommended
> to upgrade all installations to avoid this problem. |
Bugs with 2.3.5, posted by nickc1 on Wed Apr 9 13:49:32 2003
|
Forgot password option generates an error message
Password file hashes are different causing migrated password files to fail
but only for certain users, try password 516135 hashed in 2.3.4 and compare
to version 2.3.5 they are different.
Summary page title = string doesnt work also it results in the default ELOG
DB Name
HELP |
Re: Bugs with 2.3.5, posted by Stefan Ritt on Wed Apr 9 13:58:59 2003
|
> Forgot password option generates an error message
Which error? Can you be more specific. I tried it myself with this forum and
it worked for me.
> Password file hashes are different causing migrated password files to fail
> but only for certain users, try password 516135 hashed in 2.3.4 and compare
> to version 2.3.5 they are different.
Yes indeed. Please see elog:273 for more details
> Summary page title = string doesnt work also it results in the default ELOG
> DB Name
Thanks, has just been fixed, new version under CVS.
- Stefan |
Re: Bugs with 2.3.5, posted by nickc1 on Wed Apr 9 15:50:38 2003
|
> > Forgot password option generates an error message
>
> Which error? Can you be more specific. I tried it myself with this forum
and
> it worked for me.
Error sending Email
Please use your browser's back button to go back
HTTP/1.1 200 Document follows Server: ELOG HTTP 2.3.5 Content-Type:
text/html;charset=iso-8859-1 Connection: Keep-Alive Keep-Alive: timeout=60,
max=10
User name "nickc" not registered
Please use your browser's back button to go back
Yet nickc is in the password file, it generates the same message for any
other users in there too.
>
> > Password file hashes are different causing migrated password files to
fail
> > but only for certain users, try password 516135 hashed in 2.3.4 and
compare
> > to version 2.3.5 they are different.
>
> Yes indeed. Please see elog:273 for more details
Is there a way to convert all the hashes from one system to another, the
problem ive got is my password files are quiet large and want upgrades of
this nature to go seemlessly without people complaining about it.
>
> > Summary page title = string doesnt work also it results in the default
ELOG
> > DB Name
>
> Thanks, has just been fixed, new version under CVS.
>
> - Stefan
Ta |
Re: Bugs with 2.3.5, posted by Stefan Ritt on Wed Apr 9 16:06:31 2003
|
> Error sending Email
> Please use your browser's back button to go back
This error is caused if elogd cannot contact your SMTP server for sending
email. Can you please check the "SMTP host" entry in the configuration file?
> Is there a way to convert all the hashes from one system to another, the
> problem ive got is my password files are quiet large and want upgrades of
> this nature to go seemlessly without people complaining about it.
Unfortunately not. The old system had a bug which deleted the last one or two
characters, if the password length was dividable by three. Since the
characters were deleted, there is no way to reconstruct the full password. I
apoligize for the inconveniences, I know that this can cause lot of trouble,
but therefore I implemented the "Forgot password?" functionality, so that
users can log in again. Alternatively, one can edit the password file, delete
all passwords, and ask the users to log in without password and change it
afterwards immediately. |
elogd under Apache, login screen always reappears, posted by Michael Doerner on Sat Apr 5 00:33:36 2003
|
Hi,
I am new to elog so please bear with me if this sounds like a stupid
question...
I would like to run elogd under Apache because I don't want to open another
port (eg. 8080) on the firewall for incoming http traffic. I followed the
special instructions for that sort of setup but the user logon screen always
comes up again, even after using a valid username/password.
I am testing on a Redhat 7.2 based distribution (called SME server) in a
test domain (tuxhome.co.nz).
"Apache modules mod_proxy.c and mod_alias.c are activated", Yes.
There seems to be a problem here with the Apache Redirect statement. When I
try with
Redirect permanent /elog http://www.tuxhome.co.nz/elog/
ProxyPass /elog/ http://www.tuxhome.co.nz:8080/
Mozilla responds "Redirection limit for this URL exceeded" and IE6 says
"cannot find server or DNS error" so I have commented out the redirect
statement for now.
I might misunderstand the required URL statement in elogd.cfg
"URL = http://your.proxy.host/subdir/" ?
which I understand it would have to be
URL = http://www.tuxhome.co.nz/elog/ for my above example?
Maybe someone could help me with an example that includes all 3 of the
statements together, the redirect + proxypass from httpd.conf plus the URL
from elogd.conf?
Thanks for any help.
Michael |
Re: elogd under Apache, login screen always reappears, posted by Stefan Ritt on Tue Apr 8 08:57:20 2003
|
> I would like to run elogd under Apache because I don't want to open another
> port (eg. 8080) on the firewall for incoming http traffic. I followed the
> special instructions for that sort of setup but the user logon screen always
> comes up again, even after using a valid username/password.
>
> I am testing on a Redhat 7.2 based distribution (called SME server) in a
> test domain (tuxhome.co.nz).
> "Apache modules mod_proxy.c and mod_alias.c are activated", Yes.
> There seems to be a problem here with the Apache Redirect statement. When I
> try with
> Redirect permanent /elog http://www.tuxhome.co.nz/elog/
> ProxyPass /elog/ http://www.tuxhome.co.nz:8080/
> Mozilla responds "Redirection limit for this URL exceeded" and IE6 says
> "cannot find server or DNS error" so I have commented out the redirect
> statement for now.
> I might misunderstand the required URL statement in elogd.cfg
> "URL = http://your.proxy.host/subdir/" ?
> which I understand it would have to be
> URL = http://www.tuxhome.co.nz/elog/ for my above example?
>
> Maybe someone could help me with an example that includes all 3 of the
> statements together, the redirect + proxypass from httpd.conf plus the URL
> from elogd.conf?
> Thanks for any help.
This Forum runs on "midas.psi.ch" under RH 7.1, Apache 1.3.22, port 8000, and
it contains in httpd.conf:
Redirect permanent /elogdemo http://midas.psi.ch/elogdemo/
ProxyPass /elogdemo/ http://midas.psi.ch:8000/
elogd.cfg contains:
URL = http://midas.psi.ch/elogdemo/
As you can see, it works fine with all browsers, so I have no clue what is
wrong in your case. You might want to look at your /var/log/httpd/access_log
and /var/log/httpd/error_log to see what's going on. If you run elogd
interactively with the "-v" flag, you see directly the communication between
elogd and the browser which also might help.
- Stefan |
Passwords might have changed for logbook "Forum", posted by Stefan Ritt on Mon Apr 7 23:00:48 2003
|
A problem (elog:272) with certain passwords has been fixed in version
2.3.5 of ELOG. This forum runs the updated version, which can cause login
problems. All users with a password length of 3,6,9,12,... characters
cannot login with their old password anymore. They have to click
on "Forgot password?" in the login screen to have the system create a new
password for them and send it to their registered email address. In case
no email address has been registered, one can send me directly an email
(stefan.ritt@psi.ch). After one receives the new password via
email, one can log in again and change the password to the old one, which
then gets registered correctly. I apologize for any inconvenience.
- Stefan |
Password Problem, posted by Byron on Fri Apr 4 00:53:00 2003
|
I noticed that when I put in a password such as <test1> a person can login
with the password <test2> or any other number at the end. Is the
encryption not able to tell the difference between numbers? The encrypted
passwords even look the same in the password file. Is this a bug? |
Re: Password Problem, posted by Stefan Ritt on Fri Apr 4 08:58:16 2003
|
> I noticed that when I put in a password such as <test1> a person can login
> with the password <test2> or any other number at the end. Is the
> encryption not able to tell the difference between numbers? The encrypted
> passwords even look the same in the password file. Is this a bug?
This is really strange. Encryption only works on ASCII characters and does
not distinguish between letters and digits. When I try to reporoduce that,
the system distinguishes well between "test1" and "test2". The first gives
encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the different "E"
and "I". So I have no clue right now what is wrong in your installation. If
running under Linux, you can compile elogd after adding "-DHAVE_CRYPT" and "-
lcrypt" to the Makefile to use the standard Linux crypt() function, but I
would rather like to understand what is wrong in your case.
- Stefan |
Re: Password Problem, posted by Byron on Fri Apr 4 19:49:32 2003
|
> > I noticed that when I put in a password such as <test1> a person can
login
> > with the password <test2> or any other number at the end. Is the
> > encryption not able to tell the difference between numbers? The
encrypted
> > passwords even look the same in the password file. Is this a bug?
>
> This is really strange. Encryption only works on ASCII characters and does
> not distinguish between letters and digits. When I try to reporoduce that,
> the system distinguishes well between "test1" and "test2". The first gives
> encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the
different "E"
> and "I". So I have no clue right now what is wrong in your installation. If
> running under Linux, you can compile elogd after adding "-DHAVE_CRYPT"
and "-
> lcrypt" to the Makefile to use the standard Linux crypt() function, but I
> would rather like to understand what is wrong in your case.
>
> - Stefan
Ok, try it with the passwords <hello1> and <hello2>. Then when you go to log
in, put in the password of <hello> with any single number after it and let me
know if the problem shows up for you because that is the password I was
using. When I look at it encrypted in the passwd file they look the same. I
also installed the latest version today which is newer than the one I was
using before and it still does it. I appreciate your time.
Byron |
Re: Password Problem, posted by Stefan Ritt on Mon Apr 7 22:50:17 2003
|
> Ok, try it with the passwords <hello1> and <hello2>. Then when you go to
log
> in, put in the password of <hello> with any single number after it and let
me
> know if the problem shows up for you because that is the password I was
> using. When I look at it encrypted in the passwd file they look the
same. I
> also installed the latest version today which is newer than the one I was
> using before and it still does it. I appreciate your time.
Ok, I finally found the problem: Whenever a password has a length which can
be divided by three (like 6 or 9), the last two characters are completely
ignored. This problem will be fixed in version 2.3.5. Is has to be noted
that all existing passwords with the mentioned length have to be re-entered
after the upgrade from 2.3.4 to 2.3.5. Since one cannot log in with the old
password on those cases, a "Forgot password?" links has been added to the
login screen, which can be used to create a new password and send it to the
registered email address. |
Login user problem, posted by Byron on Fri Apr 4 00:50:31 2003
|
When I use the <Login user => option to specify what users I want to be
able to login into the different logbooks it does not seem to work. Is
there something else you are supposed to do to restrict what logbooks users
can log into? |
Re: Login user problem, posted by Stefan Ritt on Fri Apr 4 09:01:11 2003
|
> When I use the <Login user => option to specify what users I want to be
> able to login into the different logbooks it does not seem to work. Is
> there something else you are supposed to do to restrict what logbooks users
> can log into?
First, you need version 2.3.4 or later, second, you need a "password file =
xxx" entry in your elogd.cfg to turn on user-level password access. If both
is true and you still don't succeed, send me your elogd.cfg.
- Stefan |
Re: Login user problem, posted by Byron on Fri Apr 4 19:46:56 2003
|
> > When I use the <Login user => option to specify what users I want to be
> > able to login into the different logbooks it does not seem to work. Is
> > there something else you are supposed to do to restrict what logbooks
users
> > can log into?
>
> First, you need version 2.3.4 or later, second, you need a "password file =
> xxx" entry in your elogd.cfg to turn on user-level password access. If both
> is true and you still don't succeed, send me your elogd.cfg.
>
> - Stefan
Ok, I installed the latest version and this is fixed. Thanx! |
Logbook Title bar , posted by nick on Wed Apr 2 16:36:18 2003
|
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 |
Re: Logbook Title bar , posted by Stefan Ritt on Wed Apr 2 21:45:18 2003
|
> 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. |
Re: Logbook Title bar , posted by nick on Thu Apr 3 09:40:45 2003
|
> > 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) |
Re: Logbook Title bar , posted by Stefan Ritt on Thu Apr 3 10:11:08 2003
|
> 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)
I added the option "Summary page title = xxx" in a similar way than the "Page
title". The new version is at
http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.64
It will be included in the release 2.3.5 of elog.
- Stefan |
Elog and SSL, posted by Recai Oktas on Sun Mar 16 19:15:16 2003
|
> 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 |
Re: Elog and SSL, posted by Stefan Ritt on Fri Mar 21 16:24:05 2003
|
> 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. |
Re: Elog and SSL, posted by nick on Mon Mar 31 12:44:33 2003
|
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. |
Re: Re: Elog and SSL, posted by Recai Oktas on Fri Mar 21 16:52:12 2003
|
Ooops, I destroyed the original post, now how can we fix this :) |