Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 732 of 796  Not logged in ELOG logo
icon8.gif   User passwords not configurable with loacl passwordfile, posted by KaterKarlo99 on Tue Feb 27 15:11:23 2018 
Hi!

Tryed windows an linux version. On booth the "Register new User" dialog is not displaying a password line.
so what password is used for the new user? Further the user can't change his password, because he didn't know the old one.
    icon2.gif   Re: User passwords not configurable with loacl passwordfile, posted by Stefan Ritt on Tue Feb 27 15:32:30 2018 
Have you configures user-level access via


password file = anyfile.pwd

Can your elogd server write to that file?

If yes, can you please post your config file?
    icon2.gif   Re: User passwords not configurable with loacl passwordfile, posted by KaterKarlo98 on Wed Feb 28 11:38:23 2018 
Hi Stefan,

thanks for the quick reply.

Yes, i've configured user-level access. Here is my cfg:
    icon2.gif   Re: User passwords not configurable with loacl passwordfile, posted by KaterKarlo99 on Mon Mar 5 14:10:52 2018 
I'm afraid that there is something wrong because each user will be written with the same (hashed) password to the local password file,
irrespective of the given password within the "new User dialog".

So for instance, every user in my password file lokks like this:
    icon2.gif   Re: User passwords not configurable with loacl passwordfile, posted by Stefan Ritt on Mon Mar 5 14:29:26 2018 
What happens when you don't use Kerberos authentication?




KaterKarlo99
wrote:



I'm afraid that there is something wrong because each user will be written
    icon2.gif   Re: User passwords not configurable with loacl passwordfile, posted by KaterKarlo99 on Mon Mar 5 14:44:58 2018 
Yeah!!

That did it! I remove the line "Kerberos authentication" and now it works!

Thanks!
    icon2.gif   Re: Problem with special character "č", posted by Stefan Ritt on Tue Mar 6 15:08:23 2018 
Actually unicode characters are converted by your browser into HTML code (such as &#268) where 268 decimal = 10C hex. elog just writes to file what
it gets from the browser. When an existing elog entry gets shown by the browser, the code is translated back to the character. Why do you care what is
written to the log file? If you use scripts or so to parse your log files, you have to adapt them to correctly decode HTML encoded characters. This is
    icon2.gif   Re: Problem with special character "č", posted by Matej Sedej on Tue Mar 6 15:29:38 2018 
Hello Stefan,

thank you for the reply. The explanation does not solve my problem though. 

1) Could you elaborate, why the body text field CORRECTLY writes the character while the
ELOG V3.1.5-2eba886