Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   elog crashes when admin tries to register new users, posted by Heiko Scheit on Wed May 18 14:18:07 2005 
    icon4.gif   Re: elog crashes when admin tries to register new users, posted by Stefan Ritt on Sat Jun 4 12:25:57 2005 
       icon4.gif   Re: elog crashes when admin tries to register new users, posted by Heiko Scheit on Thu Jun 9 15:20:04 2005 
          icon2.gif   Re: elog crashes when admin tries to register new users, posted by Stefan Ritt on Fri Jun 17 22:33:29 2005 
             icon2.gif   Re: elog crashes when admin tries to register new users, posted by Heiko Scheit on Tue Jun 21 19:24:58 2005 
                icon2.gif   email flagged as spam, posted by Heiko Scheit on Tue Jun 21 19:38:06 2005 
                   icon2.gif   email flagged as spam, posted by Stefan Ritt on Fri Jun 24 21:15:14 2005 
                icon2.gif   Re: elog crashes when admin tries to register new users, posted by Stefan Ritt on Fri Jun 24 21:02:05 2005 
Message ID: 1189     Entry time: Thu Jun 9 15:20:04 2005     In reply to: 1174     Reply to this: 1198
Icon: Warning  Author: Heiko Scheit  Author Email: h.scheit@mpi-hd.mpg.de 
Category: Bug report  OS: Linux  ELOG Version: 2.5.9 
Subject: Re: elog crashes when admin tries to register new users 

Stefan Ritt wrote:

Heiko Scheit wrote:
When pasting the URL for the registration of new users (with 'Self register = 3') elog
crashes with segmentation fault. I don't have the time currently to give you more
debuging information but maybe you can have a look the same. It crashes after
the user is registered. The Email is sent, too.


I cannot reproduce this problem either. The only difference I see is that I use thunderbird as my email client, where I don't have to copy/paste the activation URL into my browser, but just click on it. If maybe the copy/paste operation adds an additional CR/LF or so, that could be a problem. Can you check again? A stack trace of the crashed elogd would help as well.


The following appended after the base (!) URL results in a segmentation fault
?cmd=Activate&new_user_name=test1&new_full_name=Test1

It works fine, if a specific logbook is given. So
http://my.ho.st/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is not OK, while
http://my.ho.st/myLogBook/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is OK.
ELOG V3.1.5-3fb85fa6