Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 566 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  1819   Fri May 5 07:58:53 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.1-1668Re: Date automatically generated by another one

Alex H wrote:
Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.

For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.

Can I do that with ELOG ?
Thanks for answer.


No, this is not implemented right now.
  1820   Fri May 5 09:01:04 2006 Reply Alex Halex@synergie-inf.comQuestionWindows2.6.1-1668Re: Date automatically generated by another one

Stefan Ritt wrote:

Alex H wrote:
Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.

For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.

Can I do that with ELOG ?
Thanks for answer.


No, this is not implemented right now.

OK! Thank for your response.
  1748   Sat Mar 4 06:08:29 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Crafted 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?
  1752   Mon Mar 6 14:04:12 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

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.
  1753   Mon Mar 6 17:35:52 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: 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.



Quote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.
  1755   Mon Mar 6 17:45:18 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.
  1756   Mon Mar 6 18:04:39 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Stefan Ritt wrote:

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.



Quote:
I was afraid to try Big grin . 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 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Stefan Ritt wrote:

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.



Quote:
I was afraid to try Big grin . 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?
ELOG V3.1.5-3fb85fa6