Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 180 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  53   Mon Jul 8 10:42:38 2002 Reply Stefan Rittstefan.ritt@psi.chBug fix  Re: exit status of elog
> The exit status of elog is always 1.  It should be zero for
> a successful submission.

Has been fixed in 2.0.4
  68950   Tue Apr 30 09:34:52 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: exclude access to a number of users in one logbook

You have a look here: elog:68936

Nikolas Patronis wrote:

How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?

 

  67400   Mon Dec 17 09:18:51 2012 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.0-1953Re: error: "HTML encoding not allowed"

julia wrote:

Hi all,

I'm absolutely new with ELOG and have only basic programming skills...

I'd like to use ELOG, so I have installed it in my computer to start playing with it (I installed version 2.7.0-1953 because with the latest one I got an error with the elogd.cfg file). I've been able to open the Demo logbook but wasn't able to submit a new entry into it. I get the following error:

"HTML encoding not allowed"

Could you please explain me how I could solve this problem?

I thank you in advance for your help.

Version 2.7.0 is very old and has knows problem. Better go with the current version and fix the problem with the elogd.cfg file. 

  1426   Wed Oct 5 13:07:51 2005 Reply Stefan Rittstefan.ritt@psi.chBug fixOtherV2.5.9-2Re: error when searching for POST

Guenter Nowak wrote:
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error


This bug has been fixed in the current CVS version.
  1153   Wed May 18 19:52:41 2005 Reply Stefan Rittstefan.ritt@psi.chBug report ?Re: error message from this forum

Heiko Scheit wrote:
Just after submitting the last message, the following error message was displayed:

Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom>


Sombody used an invalid formed email address, like user<at>domain<dot>com, on which the SMTP server complained. I would like to note here that the email addresses registered in this forum are not published in any way, so there is no risk to get spam from that (except the normal elog notifications, which can be turned off easily).
  67199   Wed Feb 15 17:13:08 2012 Reply Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinux2.90Re: error message "Command Config is not allowed" after registering

Mark Bergman wrote:

After registering, elog displays a page with the message:

     Error: Command "Config" is not allowed for user ""

However, the registration is successful. This causes confusion, and results in users registering multiple times.

 

In the elogd.conf file, I have the directive:

     Allow Config = bergman

 

Any suggestions?

 I loathe the idea of 'bumping' up one's own posting, but here I go...

 

Has anyone seen this issue, or have any solution? We've got people who register 8 or more times, since they see the "Error" message with each registration.

  67685   Wed Apr 2 19:17:31 2014 Reply Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinux2.90Re: error message "Command Config is not allowed" after registering

Mark Bergman wrote:

After registering, elog displays a page with the message:

     Error: Command "Config" is not allowed for user ""

However, the registration is successful. This causes confusion, and results in users registering multiple times.

 

In the elogd.conf file, I have the directive:

     Allow Config = bergman

 

Any suggestions?

 

Is anyone else seeing this? It's very confusing to new users.

 

  68419   Tue Sep 6 20:09:07 2016 Reply Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinux2.90Re: error message "Command Config is not allowed" after registering

 

Mark Bergman wrote:

After registering, elog displays a page with the message:

     Error: Command "Config" is not allowed for user ""

However, the registration is successful. This causes confusion, and results in users registering multiple times.

 

In the elogd.conf file, I have the directive:

     Allow Config = bergman

 

Any suggestions?

 

Well, 5 years after opening this issue, with no responses here, I finally got into the source code and fixed it.

The problem seems to be if eLog is configured to prohibit users (non-administrators) from the "Config" option...but on the initial self-registration, the code goes to the Config screen for the user anyway...resulting in the false error message.

So, I [badly] hacked eLog to fix that, add some debugging/log messages, and to correct a typo.

Attached is the patch against release 3.1.1-1. Try not to cringe too much at my code. :)

Attachment 1: elogd.c.patch
*** ./elogd.c	Tue Aug 23 21:27:39 2016
--- ../../elog-3.1.1.orig/src/elogd.c	Tue Aug  4 09:30:54 2015
***************
*** 80,84 ****
  int _verbose_level, _current_message_id;
  int _logging_level, _ssl_flag;
- BOOL just_registered = FALSE;	/* flag to supress erroneous error */
  
  LOGBOOK *lb_list = NULL;
--- 80,83 ----
***************
*** 13363,13369 ****
  
     if (new_user) {
-       write_logfile(lbs,"In save_user_config() with new_user==TRUE, setting just_registered=TRUE");
-       just_registered = TRUE;
- 
        node = mxml_find_node(lbs->pwd_xml_tree, "/list");
        if (!node) {
--- 13362,13365 ----
***************
*** 13432,13436 ****
        mxml_write_tree(file_name, lbs->pwd_xml_tree);
  
- 
     /* if requested, send notification email to user or admin user */
     if (new_user && !first_user && (self_register == 2 || self_register == 3 || self_register == 4)
--- 13428,13431 ----
***************
*** 13616,13619 ****
--- 13611,13615 ----
                    };
                 }
+ 
                 pl = strtok(NULL, " ,");
              }
***************
*** 26649,26666 ****
     /* save user info if "save" is pressed */
     if (strieq(command, loc("Save")) && isparam("new_user_name") && !isparam("config")) {
!       if (!save_user_config(lbs, getparam("new_user_name"), TRUE)) {
           return 0;
!       }
!       if ( just_registered ) {
!          write_logfile(lbs,"In do_self_register with just_registered==TRUE, resetting flag, calling show_login_page(NULL,\"\",0)");
!          just_registered = FALSE;
!          show_login_page(NULL, "", 0);
!       } else {
!          if (lbs)
!             sprintf(str, "../%s/", lbs->name_enc);
!          else
!             sprintf(str, ".");
!          redirect(lbs, str);
!       }
        return 0;
     }
--- 26645,26655 ----
     /* save user info if "save" is pressed */
     if (strieq(command, loc("Save")) && isparam("new_user_name") && !isparam("config")) {
!       if (!save_user_config(lbs, getparam("new_user_name"), TRUE))
           return 0;
!       if (lbs)
!          sprintf(str, "../%s/", lbs->name_enc);
!       else
!          sprintf(str, ".");
!       redirect(lbs, str);
        return 0;
     }
***************
*** 27355,27364 ****
        /* check if user has access to logbook */
        if (!check_login_user(lbs, getparam("uname"))) {
!       	sprintf(str, "check_login_user access failure: user \"%s\", logbook \"%s\"", uname, lbs->name);
!       	write_logfile(lbs, str);
!          show_error("User has no access to this logbook.");
!          strlcpy(str, loc("New user"), sizeof(str));
!          url_encode(str, sizeof(str));
!          rsprintf("


<b><center><a href=\"?cmd=%s\">%s</a></center></b></td></tr>", str, loc("Register as new user")); return; } --- 27344,27348 ---- /* check if user has access to logbook */ if (!check_login_user(lbs, getparam("uname"))) { ! show_error("Use has no access to this logbook"); return; } *************** *** 27728,27747 **** strencode2(str2, command, sizeof(str2)); strencode2(str3, full_name, sizeof(str3)); ! ! if (strieq(str2,"Config") && just_registered == TRUE ) { ! /* this is the only time to skip the error that "Config" is not an allowed command...as the Config was really ! called in order to complete the self-registration ! ! now, reset the flag */ ! write_logfile(lbs,"In interprete() with just_registered==TRUE, resetting flag, skipping error message that user is not allowed to run command \"Config\""); ! just_registered = FALSE; ! } else { ! sprintf(str, "Error: Command \"%s\" is not allowed for uname \"%s\", full name \"%s\"", str2, uname,str3); ! write_logfile(lbs, str); ! ! sprintf(str, loc("Error: Command \"<b>%s</b>\" is not allowed for login \"<b>%s</b>\", user \"<b>%s</b>\""), str2,uname,str3); ! show_error(str); ! return; ! } } --- 27712,27718 ---- strencode2(str2, command, sizeof(str2)); strencode2(str3, full_name, sizeof(str3)); ! sprintf(str, loc("Error: Command \"<b>%s</b>\" is not allowed for user \"<b>%s</b>\""), str2, str3); ! show_error(str); ! return; }
ELOG V3.1.5-3fb85fa6