| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1748
|
Sat Mar 4 06:08:29 2006 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Crafted URL causes elog to coredump |
While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
|
1753
|
Mon Mar 6 17:35:52 2006 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
| Stefan Ritt wrote: |
| Steve Jones wrote: | While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write
http://midas.psi.ch/elogs/elog/Forum
it does not crash. |
|
|
1754
|
Mon Mar 6 17:43:11 2006 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Re: Allow $attributes in "Comment = " option |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution. |
| Quote: | | Ok, just a thought. Thanks |
|
|
1756
|
Mon Mar 6 18:04:39 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
| Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
| Quote: | I was afraid to try  . Ok, then the issue *might* be rev 1660 or perhaps the fact that compiled under Solaris it does this. Any suggestions on how to find out? |
|
|
1757
|
Mon Mar 6 18:06:32 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
| Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
| Quote: | | I was afraid to try . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out? |
|
|
1758
|
Mon Mar 6 18:36:34 2006 |
 | Steve Jones | steve.jones@freescale.com | Question | All | 2.5.9 | [RESOLVED] eLog Version number as eLog attribute? |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
| Steve Jones wrote: | When a footer is used (via Bottom text = <filename>) eLog no longer displays the eLog version number at the bottom. Is it possible to somehow expose the version/revision as an eLog attribute or have the version still display even when a replacement footer is specified?
Thanks! |
I added that feature, but will not be able to commit it before the next weekend. |
| Quote: | | Not a problem! Thanks |
|
| Steve Jones wrote: | | Works as requested!! |
|
|
1759
|
Mon Mar 6 18:54:32 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | [UPDATE] Re: Crafted URL causes elog to coredump |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
| Quote: | | I was afraid to try . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out? |
|
| Steve Jones wrote: | Ok, here is what I found:
- Now running rev 1671
- Specifying a non-existent logbook with plain URL of elog server: OK, error is caught and reported
- Specifying a non-existent logbook *under* a logbook name: Ok, error is caught.
- Specifying a non-existent logbook under a "Top Group" of the form "This+Is+Top+Group+One" results in no error, elogd crash. Example URLs:
- Results in a program crash under Solaris. Top Groups were not defined under elog 2.5.3.
|
|
|
1762
|
Wed Mar 8 18:05:54 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | [UPDATE2] Re: Crafted URL causes elog to coredump |
| Steve Jones wrote: |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
No, the above link just works fine, just click it. |
| Quote: | | I was afraid to try . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out? |
|
| Steve Jones wrote: | Ok, here is what I found:
- Now running rev 1671
- Specifying a non-existent logbook with plain URL of elog server: OK, error is caught and reported
- Specifying a non-existent logbook *under* a logbook name: Ok, error is caught.
- Specifying a non-existent logbook under a "Top Group" of the form "This+Is+Top+Group+One" results in no error, elogd crash. Example URLs:
- Results in a program crash under Solaris. Top Groups were not defined under elog 2.5.3.
|
|
| Steve Jones wrote: | Well, more data. When I have Top Groups defined and I go to create a new logbook via the eLog interface, the interface creates a URL of the form:http://elog-test.company.com/EngineeringComputeChangeLogs/Test2/?cmd=Config
This causes eLog to crash -- so I am at a complete loss. I tried shortening the length of the top group name. It all seems to come back to the inclusion of the name of a logbook that doesn't exist yet?) although I confirmed that the eLog config file *is* updated and the logbook directory *is* created. So now I am trying to figure out how to debug this thing. Stefan, any clues?
|
|