| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1267
|
Thu Jul 14 15:58:07 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Comment | All | | A new ELOG user wants to register on "127.0.0.1" |
A new ELOG user wants to register on "127.0.0.1"
the scenario is:
- elog on localhost
- stunnel on the external interface
I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ? |
|
1268
|
Thu Jul 14 17:29:42 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Comment | All | | Re: A new ELOG user wants to register on "127.0.0.1" |
| Emiliano Gabrielli wrote: | A new ELOG user wants to register on "127.0.0.1"
the scenario is:
- elog on localhost
- stunnel on the external interface
I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ? |
You can specify the interface to liste on with the "-n <interface>" parameter of elogd. |
|
1271
|
Thu Jul 14 19:16:06 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Comment | All | | Re: A new ELOG user wants to register on "127.0.0.1" |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | A new ELOG user wants to register on "127.0.0.1"
the scenario is:
- elog on localhost
- stunnel on the external interface
I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ? |
You can specify the interface to liste on with the "-n <interface>" parameter of elogd. |
I know 
the following is the configuration I'm telling about... and it raises the problem reported
albert@YYYYYYYYY:~$ ps axu | grep elog
elog 22348 1.0 1.9 23660 20408 ? Ss 11:32 4:54 /usr/sbin/elogd -f /var/run/elogd.pid -c /etc/elog.conf -d /var/lib/elog -s /usr/share/elog -p 8081 -n 127.0.0.1 -x -D
root 22353 0.0 0.2 45436 2276 ? Ss 11:32 0:17 /usr/sbin/stunnel -o /var/log/elog/elog_daemon.log -p /etc/ssl/certs/stunnel_XXXXXXX.pem -d XXXXXX.roma2.infn.it:8080 -r 127.0.0.1:8081
|
|
1302
|
Sat Jul 23 15:46:06 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | All | | Re: A new ELOG user wants to register on "127.0.0.1" |
Ok, I kind of misunderstood the "-n" parameter. It is the interface to listen to, which is not necessarily the host name as seen from outside. I changed that in the following way:
- if the URL option is present, the host name is taken from there
- if the URL option is not present, elog calls gethostname()/gethostbyname() to retrieve the local host name
the host name which comes from these two possibilities is used internally in all cases where it's needed, like email notifications. |
|
1403
|
Thu Sep 1 18:26:38 2005 |
| ralphb | elog@spampot.com | Comment | | | Re: something for the wishlist: 'Recent Changes' |
| Heiko Scheit wrote: | A 'Recent Changes'-link (option) that lists entries that were changed
recently, where 'recent' can be changed from 1,2,3...(some maximum)
days. |
Two possible solutions:
1. Use ELOG's RSS support (look for "RSS Title" in the config syntax help). I added an RSS icon to each entry with "Bottom Text=<a href="http://myserver:8080/mylogbook/elog.rdf"><img border=0 height="14" width="36" src="/Rssicon_3614.gif" alt="[RSS]"></a>
2. Add a new attribute "Revised" and config it as follows: "Locked attributes = Revised" and "Subst on Edit Revised = $date". It'll get updated each time the entry gets updated. Then all you just need to create a link to "http://yourserver:8080/yourlogbook/page?mode=summary&rsort=Revised"
Best regards, Ralph. |
|
1591
|
Fri Jan 13 02:37:10 2006 |
 | Chris Warner | christopher_warner@dcd.uscourts.gov | Comment | Linux | | Re: LDAP |
| Stefan Ritt wrote: |
| Carl Shirey wrote: | I know you want to make ELOG a stand alone program. But is there a way to still make a stand alone but have the option work with LDAP?
FYI
Elog works great we us it for our shift carryover and we have about 25 people useing it and I have heard no complants with it.
Thanks |
I added your vote to the "PAM" authentication on the wishlist, since PAM contains an LDAP module. |
Please Add my vote too. I think that would be great. |
|
1615
|
Fri Jan 20 02:53:40 2006 |
 | Chris Warner | christopher_warner@dcd.uscourts.gov | Comment | Linux | 2.6 | Re: Buffer Overflow? |
| 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! |
|
1732
|
Tue Feb 28 11:26:22 2006 |
| Alex H | alex@synergie-inf.com | Comment | Windows | 2.6.1-1668 | Re: MOptions problem ? |
> Hi Holger,
>
> > Which ELOG version do you use?
> I'am using the version V2.6.1-1653 of Elog
>
> > From which logbook are the screenshots? (I assume it's Liste - right?)
> Right :)!
>
> I've just seen that Stefan has build a V2.6.1-1663 version of ELOG.
> I try to install this new version and gave you answer as soon as possible :)!
Now I'am using the Elog V2.6.1-1668 and same probleme.
I think it's a data problem. I have edited my logbooks\Liste\050302a.log with an Hexadecimal editor and found one
carruage return juste before the |