Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 658 of 808  Not logged in ELOG logo
    icon14.gif   Re: "Reply to" Author in this forum, posted by David Pilgram on Thu Nov 26 20:37:02 2009 
> > Hi Stefan,
> > 
> > This has happened twice on this forum now, starting from Mon 23rd November.
> > 
> > Someone submits an entry (Me, 66625, Bertram Metz 66628)
> > I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> > yourself.  My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> > 
> > Is this a bug, or some wierd affect of us forgetting to log out?
> > 
> > Regards,
> > 
> > David.
> 
> Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the
> 
> Re: Re: Re: ...
> 
> in the subject line. I changed this now completely so that we can have
> 
> Preset on reply Author = $full_name
> Preset on first reply Subject = Re: $Subject
> 
> which fixes both things. The modification is in revision 2271.

Thanks Stefan!
    icon2.gif   Re: "Preset on reply" not work?, posted by Stefan Ritt on Mon Jun 15 08:33:50 2015 

You have "Remove on reply" together with "Preset on reply Author". Since the first is executed later, you first preset the author name, then remove it again. Just discard the "Remove on reply" and you are fine.

Daniel Sajdyk wrote:

Hi all :)

I try to setup my first lobgook, and have some problem. 

I want that Author was preset by $long_name, and it can't change its name. That works correct. I also want, when other user click Reply, that he will be author of reply, but Author windows goes emtpy... No Author, or Reply User in that field. Is it correct?

Do you have any suggestions? 

Here is part of config I use:

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
Preset on reply Author = $long_name

 

Regards

Daniel.

 

    icon2.gif   Re: "Preset on reply" not work?, posted by Daniel Sajdyk on Mon Jun 15 09:16:00 2015 

Ok. Now it works :) Thank you :) I'm translating Elog into Polish. When I finish, can I send it to you?

Regards Daniel. 

Stefan Ritt wrote:

You have "Remove on reply" together with "Preset on reply Author". Since the first is executed later, you first preset the author name, then remove it again. Just discard the "Remove on reply" and you are fine.

Daniel Sajdyk wrote:

Hi all :)

I try to setup my first lobgook, and have some problem. 

I want that Author was preset by $long_name, and it can't change its name. That works correct. I also want, when other user click Reply, that he will be author of reply, but Author windows goes emtpy... No Author, or Reply User in that field. Is it correct?

Do you have any suggestions? 

Here is part of config I use:

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
Preset on reply Author = $long_name

 

Regards

Daniel.

 

 

    icon2.gif   Re: "No SMTP host defined in [global] section of configuration file" error, posted by Stefan Ritt on Wed Apr 14 13:03:37 2010 

Pedro Gil de Araújo Gordo wrote:

Hi

When I upload a message with a attachment (and also without an attachment) I get this message:

"No SMTP host defined in [global] section of configuration file"

However the file and the text have been uploaded. So why does it gives me this message, and how do I work this out?

Best Regards

Tirwit

This error comes if you have configured email notifications, and no SMTP host defined in the configuration file. Elog has to contact your SMTP server to send any email. Read the email notification paragraph in the documentation. 

    icon2.gif   Re: "No SMTP host defined in [global] section of configuration file", posted by Stefan Ritt on Wed Jan 18 10:25:20 2017 

These problems usually come when you are using a different configuration file that the one you think you are using. Note that you explicitly can tell elogd to use a specific configuation file with the "-c" flag. Also make sure to restart elogd after major changes.

Luca wrote:

Hi,

I started re-using after a month an elog on my linux machine and, without any apparent reason since I did not used the machine at all in the last month, every time I try to submit a post I get the following error

"No SMTP host defined in [global] section of configuration file".

The weird thing is that today I created a new logbook using the previous one as a template and, on the new one, I can post without problem (although the configuration is identical).

Do you know what could be causing this?

Thnaks

R

 

    icon2.gif   Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Tue Aug 4 13:29:23 2020 

Unfortunately I locallly don't have Webserver authentication, so I cannot check or debug. If you send me a diff that works for you, I'm happy to incorporate it.

Stefan

Jan Just Keijser wrote:

Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"  and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error pops up saying that their username (the admin one, not the new one) already exists. I found the following code:

int save_user_config(LOGBOOK * lbs, char *user, BOOL new_user)
{
   char file_name[256], str[256], *pl, user_enc[256], new_pwd[80], new_pwd2[80], smtp_host[256],
       email_addr[256], mail_from[256], mail_from_name[256], subject[256], mail_text[2000], str2[256],
       admin_user[80], url[256], error[2000], sid[32];
   int i, self_register, code, first_user;
   PMXML_NODE node, subnode, npwd; 

   /* if we outsourced the authentication, use external username */
   getcfg(lbs->name, "Authentication", str, sizeof(str));
   if (stristr(str, "Webserver")) {
      /* do not allow HTML in user name */
      strencode2(user_enc, http_user, sizeof(user_enc));
   } else {
      strencode2(user_enc, user, sizeof(user_enc));
   }

 

which seems to be the culprit:  the admin user is logged using his/her Webserver (http_user) credentials and this overrides anything that he/she might fill in.  If I remove the "Authentication" check then I can create a new user without problems.  So, how to fix this? should the "Authentication=Webserver" check be extended with a self/auto registration check?

 

 

    icon2.gif   Re: "New User" option does not work when Authentication=Webserver, posted by Jan Just Keijser on Wed Aug 18 09:05:51 2021 elog-webauth.patch

here's the patch that I use to enable  use creation and deletion in combination with Webserver authentication.

The idea behind the patch is that if the user logged in via  "http_user" is an elog admin, then {s}he is allowed to save a random user configuration, including creating or deleting a user.

Stefan Ritt wrote:

Unfortunately I locallly don't have Webserver authentication, so I cannot check or debug. If you send me a diff that works for you, I'm happy to incorporate it.

Stefan

Jan Just Keijser wrote:

Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"  and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error pops up saying that their username (the admin one, not the new one) already exists. I found the following code:

int save_user_config(LOGBOOK * lbs, char *user, BOOL new_user)
{
   char file_name[256], str[256], *pl, user_enc[256], new_pwd[80], new_pwd2[80], smtp_host[256],
       email_addr[256], mail_from[256], mail_from_name[256], subject[256], mail_text[2000], str2[256],
       admin_user[80], url[256], error[2000], sid[32];
   int i, self_register, code, first_user;
   PMXML_NODE node, subnode, npwd; 

   /* if we outsourced the authentication, use external username */
   getcfg(lbs->name, "Authentication", str, sizeof(str));
   if (stristr(str, "Webserver")) {
      /* do not allow HTML in user name */
      strencode2(user_enc, http_user, sizeof(user_enc));
   } else {
      strencode2(user_enc, user, sizeof(user_enc));
   }

 

which seems to be the culprit:  the admin user is logged using his/her Webserver (http_user) credentials and this overrides anything that he/she might fill in.  If I remove the "Authentication" check then I can create a new user without problems.  So, how to fix this? should the "Authentication=Webserver" check be extended with a self/auto registration check?

 

 

 

    icon2.gif   Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Thu Feb 10 17:32:42 2022 

Thanks for your patch, I committed it.

Stefan

ELOG V3.1.5-3fb85fa6