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
name not in it. It created the following GDB output:

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0x916b768, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:19793
19793         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;

Expected behaviour would be to show me the login page with the error message:
"you don't have access to this logbook".
This message is never shown for the attached configuration file.
If I remove the "Guest" commands for logbook "TestB" then elogd behaves properly.

For the moment I've just disabled "Login user" settings.

Regards
Andreas

Firstly, as with some of the others recently, I am a complete newb when it comes to linux, Though I refuse to let that stop me and really want to get this working.

Pretty much I have a situation where I have been asked to install ELOG, though I am unable to use port 25 at all and also need to use GMAIL for the SMTP server?
It is also my undertanding from the documentation that ELOG only sends mail via port 25

So, I have setup iptables to forward everything from port 25 and a GMAIL IP address used in ELOG's global config for the SMTP, to a stunnel that redirects everything to GMAIL on port 465.
While getting that right took me almost two days, and that was with tons of help and more than half of it being spoon fed to me (though I have learnt SO SO MUCH from just that).
I am still unable to get ELOG to send emails, even if does now seem to connect

Below is a copy of the log from last night (I have spent most of the day trying to sort it out further, but I get the same error)

So I guess my question is, Is it possible to use GMAIL, with ELOG, based on my current conditions, and does anyone have any idea what I can do to go on from here, as I doubt I am the first one to head down this road?
 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

10-Apr-2012 21:45:19 [Chris@1.2.3.4] {logbookA} Email from <chris@server.com> to chris@server.com, SMTP host 173.194.67.108:
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 220 mx.google.com ESMTP XXXXXXXX.XX^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA}
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} EHLO SERVER.COM^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-mx.google.com at your service, [152.106.18.2]^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-SIZE 35882577^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-8BITMIME^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-AUTH LOGIN PLAIN XOAUTH^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250 ENHANCEDSTATUSCODES^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} AUTH LOGIN^M
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Username:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} username@gmail.com
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Password:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} MYXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} 501 5.5.2 Cannot Decode response fl2sm792152wib.2

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Right now I am pretty stuck, and any advice would be greatly appreciated on how to move forward.

Thanks in Advance
 

Hi Stefan,
could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
number?
That would be 13 characters.

Cheers
Andreas

This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.

Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

When I try to set

Protect Selection page = 1

in the config file elog crashes. Attached is my config file.

elog 2.7.5 built Apr  8 2009, 16:52:07 revision 130

Dear All 

i have this problem since i tried  to install ELOG latest version while make Authetnetication Kerberos ELOG stop runing any idea or help please

Hello everybody.

I am sure that some of you (just like me) experimented already with themes 
and especially now with .CSS in order to give ELOG a different "look" 
and "feel". 

I was wondering if we could maybe share examples of such adapted 
ELOG's .CSS files (or themes). Maybe you can take a screen shot of your 
favorite ELOG "face" (no sensitive data, of course) and post it here as an 
attachement. Or is everybody using only the original look that Stefan 
delivers as default?

Let's share some inspiration. I'll post mine as soon as finished the re-
look.

Tomas

An ELOG vulnerability has been reported, thanks to Asif Akbar of Trend Micro Security Researchworking with Trend Micro's Zero Day Initiative:

https://www.zerodayinitiative.com/advisories/ZDI-20-252/

The issue has been fixed in the current release 3.1.4-033e292 and in the RPM http://elog.psi.ch/elog/download/RPMS/elog-latest.x86_64.rpm

Best,
Stefan