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

[global]
SSL = 1
Port = 443
Authentication = Kerberos, File
Password file = passwd.txt
Login expiration = 8
Admin user = luedeke
Allow password change = 0
Self register = 0
Logfile = elog.log
Group Operation = TestA, TestB
URL = https://localhost

[TestA]
Guest Menu commands = List, New, Find, Login, Help
Guest List Menu commands =  New, Find, Login, Help
Comment = Test Log
Attributes      = Autor
Preset Autor = $long_name
Locked Attributes = Author

[TestB]
Guest Menu commands = List, Find, Login, Help
Guest List Menu commands =  Find, Login, Help
Comment = TestB
Attributes = Author
Admin user = flechsig
Login user = flechsig, spielmann
Preset Author = $long_name
Locked Attributes = Author