obfuscate password in verbose logging, posted by Mark Bergman on Thu Apr 26 23:57:04 2012
|
I'm trying to debug an issue with elogd (2.9.1) and was reminded that using the "-v" option exposes
user passwords. This wasn't a huge problem for us in the past, but we're now using kerberos authentication,
meaning that the exposed username/password applies to lots of sensitive systems within our university.
|
|
ELOG crashes when editing threads, posted by Louis de Leseleuc on Fri Sep 14 17:59:44 2012
|
Hi,
I am experiencing repeated crashing of the elog daemon.
If I go into select mode while in threaded view, I can select an entire thread by selecting the top entry. |
Crash with long image names, posted by Josef Uher on Sun Sep 16 21:14:12 2012 
|
Hi All,
I found that elog crashes if I try to upload an image with long name. It actually uploads the file after the crash. It crashes also if in the full
view with attachments visible. If I shorten the name all is fine. |
|
Re: Importing XML, posted by Andreas Luedeke on Thu Oct 4 11:35:12 2012
|
David Chastain wrote:
[...] Basically, I am trying to take spreadsheet data, convert it into XML and upload it as |
|
ELOG crash related to Kerberos, SSL and Login users, posted by Andreas Luedeke on Mon Nov 26 15:57:49 2012
|
I'm using Kerberos and SSL and experience problems with individual setting of "Login user =" for different logbooks.
Sometimes (not every time, but most times) the server crashes under the following condition:
When I login at one logbook and then change to a logbook, that has a restricted "Login user" list with my login
|
|
Error 554 MailTransferAgentServer ESMTP not accepting messages, posted by Ron Beekman on Mon Dec 10 16:28:27 2012
|
Hello,
We use ELOG for many years and enjoy it's functions every day!
Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages |
|
elogd crashes with malloc() memory corruption, posted by Mark Bergman on Fri Mar 1 16:35:21 2013
|
I'm having an issue with ELog 2.9.2 revision 2455 where it crashes consistently with:
*** glibc detected *** /usr/local/sbin/elogd: malloc(): memory corruption: 0x0000000014977210 ***
(the address varies). The crash seems to be triggered by the attempt to email a log entry. The log entry itself is saved. If I open the existing |
|
Incomplete SSL proxy instructions, insecure result., posted by Konstantin Olchanski on Fri Mar 22 19:41:31 2013
|
The instructions for securing elogd using an SSL proxy are incomplete.
http://midas.psi.ch/elog/adminguide.html#secure
http://midas.psi.ch/elogs/contributions/11
|