Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Drop attachments here..., posted by Xuan Wu on Wed Jun 23 03:48:22 2021 
    icon2.gif   Re: Drop attachments here..., posted by Sebastian Schenk on Mon Jun 28 14:53:44 2021 
       icon2.gif   Re: Drop attachments here..., posted by Xuan Wu on Mon Jun 28 18:41:31 2021 
          icon2.gif   Re: Drop attachments here..., posted by Sebastian Schenk on Tue Jun 29 15:21:06 2021 
             icon2.gif   Re: Drop attachments here..., posted by Sebastian Schenk on Tue Jun 29 20:13:36 2021 
                icon2.gif   Re: Drop attachments here..., posted by Stefan Ritt on Tue Jun 29 20:20:38 2021 
                   icon2.gif   Re: Drop attachments here..., posted by Sebastian Schenk on Wed Jun 30 13:50:08 2021 
                icon2.gif   Re: Drop attachments here..., posted by Xuan Wu on Wed Jun 30 04:38:21 2021 
Message ID: 69384     Entry time: Wed Jun 30 13:50:08 2021     In reply to: 69382
Icon: Reply  Author: Sebastian Schenk  Author Email: sebastian.schenk@physik.uni-halle.de 
Category: Question  OS: Linux  ELOG Version: 3.13 
Subject: Re: Drop attachments here... 

Thanks for the merge.
I found a more general solution, as there could be the posibility to have the author as "select" or "radio box" input in the form, where the fix breaks.
But I think in most of the cases the author is a preset input, if used with "restrict edit = 1", so the merged fix should be fine.
https://bitbucket.org/merrx/elog/commits/7aacfbcac43b1192e5271fa7b2c80f4825c94d23

Today we ran into this issue again, but this time the curpit was encoding...
The author name in the password file was differently encoded as the author name from the xhr request.
For this instance there was a umlaut in the name.

I haven't got a good solution for this at the moment.
The workaround is to check the encording in the password file and make it matching.
But as for automated logins / user generation e.g. via LDAP (in our case) one should be aware of this issue.

Stefan Ritt wrote:

Looks good, I merged the pull request.

 

ELOG V3.1.4-80633ba