Problem selecting ports, posted by Chris Warner on Fri Jan 13 03:21:32 2006
|
I had problems getting elog to run on port 8080 (or many others). I have it installed on Redhat Enterprise Linux rel 4. The only way I was able to get it working was using port 80. I would like to run it on a different port if possible but I'm not sure what is wrong.
Any Ideas |
Automatic Copy to , posted by Chris Warner on Fri Jan 13 13:16:25 2006
|
| Is it possible to configure elog to copy a new entry from 1 logbook to another? |
Re: Problem selecting ports, posted by Chris Warner on Tue Jan 17 13:59:58 2006
|
Nevermind. this was an iptables issue.
| Chris Warner wrote: | I had problems getting elog to run on port 8080 (or many others). I have it installed on Redhat Enterprise Linux rel 4. The only way I was able to get it working was using port 80. I would like to run it on a different port if possible but I'm not sure what is wrong.
Any Ideas |
|
|
Email based on not attribute value, posted by Chris Warner on Tue Jan 17 14:09:17 2006
|
Is it possible to send an email if an attribute is not equal to a specific value?
For instance, I have a server logbook that several people are able to write to. There is one person that is ultimately responsible for this server. I would like to generate an email any time that someone other than the System Administrator creates a new entry.
Thanks,
Chris Warner |
Buffer Overflow?, posted by Chris Warner on Wed Jan 18 17:20:45 2006
|
Users can access root level directories by using a modified URL. I saw on some security web sites that this was a problem in previous versions. Was it not fixed in 2.6?
To recreate enter http://yourhost.yourdomain.com/../../../../etc/passwd
view your password file in the browser.
If this was previously reported, is there a fix?
Chris Warner |
Re: Buffer Overflow?, posted by Chris Warner on Fri Jan 20 02:53:40 2006
|
| Stefan Ritt wrote: |
| Chris Warner wrote: | Users can access root level directories by using a modified URL. I saw on some security web sites that this was a problem in previous versions. Was it not fixed in 2.6?
To recreate enter http://yourhost.yourdomain.com/../../../../etc/passwd
view your password file in the browser.
If this was previously reported, is there a fix?
Chris Warner |
Thanks for telling me, I didn't know. I was able to reproduce your problem under certain conditions, and I just released version 2.6.1 to fix it. However it has nothing to do with an old buffer overflow (see elog:941).
I would strongly advise everybody to upgrade as soon as possible. |
Thanks for the quick response! |
|
email problems, posted by Chris Warner on Tue Feb 7 21:02:22 2006
|
When I select to get email notification on new logbook entries I receive this error when entering a new record.
Error sending Email via "xxx.xxx.xxx.xx": Syntax error, parameters in command "MAIL FROM: christopher_warner@xxx.gov SIZE=1985" unrecognized or missing
The user that sent the message was a test account that I set up. I entered the email address in the box provided and I am not sure what may be causing the difficulty.
Any thoughts as to what may be causing this? |
Re: email problems, posted by Chris Warner on Wed Feb 8 18:38:30 2006
|
The email address id correct. I am using an Elog Binary. I don't have the source code .
Chris Warner
| Stefan Ritt wrote: |
| Chris Warner wrote: | Error sending Email via "xxx.xxx.xxx.xx": Syntax error, parameters in command "MAIL FROM: christopher_warner@xxx.gov SIZE=1985" unrecognized or missing
|
There are two possible reasons:
1) The email address "christopher_warner@xxx.gov" is invalid. Some SMTP server immediately complain about invalid email addresses and refuse to send any mail then. In that case just supply an existing email address or remove that test account.
2) The SMTP server does not like the "SIZE=xxx" option. This comes from a single line in elogd.c:
snprintf(str, strsize - 1, "MAIL FROM: %s SIZE=%d\r\n", from, strlen(text));
you could just go there and remove the " SIZE=%d", so that the line looks like:
snprintf(str, strsize - 1, "MAIL FROM: %s\r\n", from);
to see if that makes any difference. |
|