Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 160 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  65647   Mon Nov 5 15:05:33 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: large attachment seems to hang elogd?

Konrad Klimaszewski wrote:
I don't know put it in the FAQ or something (under: "Why my posts with large attachments are submitted so slowly" Wink).


http://midas.psi.ch/elog/faq.html#18


Konrad Klimaszewski wrote:
Thanks for implementing ELCode for tables - love them Big grin


Have you tried tables in HTML form? Even better! Just switch the encoding from ELCode to HTML (starting from version 2.7.0).
  65653   Tue Nov 20 22:27:03 2007 Reply Jacky Lizli@phys.hawaii.eduQuestionLinux2.6.1Re: large attachment seems to hang elogd?
Hi,

I put in the option:

Email Format = 111

Attachment still comes in to the notification instead of the link. I am using elog-2.7.0-1. Any ideas? Thank you.



Stefan Ritt wrote:

Konrad Klimaszewski wrote:
I don't know put it in the FAQ or something (under: "Why my posts with large attachments are submitted so slowly" Wink).


http://midas.psi.ch/elog/faq.html#18


Konrad Klimaszewski wrote:
Thanks for implementing ELCode for tables - love them Big grin


Have you tried tables in HTML form? Even better! Just switch the encoding from ELCode to HTML (starting from version 2.7.0).
  65655   Thu Nov 22 14:16:51 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: large attachment seems to hang elogd?

Jacky Li wrote:
I put in the option:

Email Format = 111

Attachment still comes in to the notification instead of the link. I am using elog-2.7.0-1. Any ideas?


You will see the attachment name in the notification (see below), but the actual attachment is not contained in the email, thus making it very small.
  69534   Mon May 23 07:48:40 2022 Reply Fred Nerksfredn6969@live.comQuestionWindowscurrentRe: ladp Invalid user name or password!

 

Fred Nerks wrote:

Hi I am running elog on windows 2022 server and trying to use ldap for Auth.

No matter what i do I cannot get it to authenticate against the DC.

Invalid user name or password!

11-May-2022 17:09:15 [xxx.xxx.xxx.xxx] {TrainingHouse1} LOGIN user "xxxxx" (attempt)

Using an LDAP browser I can connect to the DC without issue so not firewall.

Not sure what I am doing wrong.

[global]
port = 5050
Page title = Elog Training
Entries per page = 25
Password file = password.pwd
List page title = Elog Training
Login page title = Elog Training
Show top groups = 0
Logbook tabs = 0
Menu commands = Back, New, Find, Download, Logout
List Menu commands = New, Find, Logout
Self register = 0
Max content length = 100000
Allow password change = 0
Enable attachments = 0
Show attachments = 0
Hide attachments = 1
List after submit = 1
Logout to main = 0
Allowed encoding = 5
Default encoding = 1
Welcome title = Elog Training LogBook.
## Welcome title = <font size=5 color=white>Elog Training LogBook </font><img src="elog.png">
Summary lines = 5
Summary line length = 100
Search all logbooks = 0
Refresh = 300
Login expiration = 0
Reply string = 
Suppress default = 2
Thread display = $category entered by $author on $Entry time
Thread icon = Icon
Preset on reply author = $long_name
All display limit = 300
Start page = ?last=31
Bottom text =
Bottom text login = <font size=5 color=Red><center></br>ELOG Training web site</center></font>

[ADTrainingHouse1]
Hidden = 0
Authentication = LDAP, File
LDAP server = ldap://xxxxxx.xxxxx.xxxx.xxxx.xxxx.au:389
LDAP userbase = OU=Users,OU=CP,DC=xxxx,DC=xxxx,DC=xxxx,DC=xxxx,DC=au
LDAP login attribute = uid
LDAP register = 0
Theme = default
Comment =Training House 1 LogBook
Preset Author = $long_name
Locked Attributes = Author
Attributes = Category, Codes, Residents Involved, Medical, Synopsis, Event Date, Author
Options Synopsis = Yes, No
MOptions Medical = Yes
MOptions Residents Involved = Pleaseadd, Test User
Extendable options = Residents Involved
Style Synopsis Yes = background-color:yellow
Style Medical Yes = background-color:green
Type Event Date = datetime
Preset Event Date = $datetime
Date format %A %B %d %Y %H:%M 
List Display = ID, Event Date, Category, Medical, Codes, Residents Involved, Synopsis, Date, Author
MOptions Category = Assault, Death, Fire, Illness, Inappropriate Sexualised Behaviour, Injury To Child, Injury To Staff, Property Damage, Self-Harm, Substance Misuse, Theft/Loss, Threat
MOptions Codes = MED, ACH, LEGAL, MPR, P/C, PSYCH, MFP, BEH, INC, CM, FAM, INFO, MVT, OBS, POLICE, PROG, ROU, VIS, S/O
Required Attributes = Author, Event Date, Codes
Style Codes MED = background-color:green
Page Title = DCP Elog Training
Reverse sort = 1
Quick filter = Date, Category, Codes, Medical,
Sort Attributes = Event Date
Logfile = traininghouse1.log
Logging level = 3
Bottom text =

Is anyone able to assist with what I am doing wrong is anyone successful used LDAP in windows elog

  67595   Fri Nov 1 14:14:03 2013 Reply Hal Proctorhproctor2@gmail.comQuestionLinux2.9.2-1Re: kerberos authentication NOT working

Fabio Sella wrote:

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

 
Detect language » Italian
 

 

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

 I have asked for same help, and no one has answered with a solution on implementing a kerberos .  I saw exactly what you were seeing. (did you try fully qualifying the domain within the username field for logon?  \\TEST.COM\username)

I still couldn't get it to work

  67597   Mon Nov 4 15:07:40 2013 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-1Re: kerberos authentication NOT working

Hal Proctor wrote:

Fabio Sella wrote:

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

 
Detect language » Italian
 

 

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

 I have asked for same help, and no one has answered with a solution on implementing a kerberos .  I saw exactly what you were seeing. (did you try fully qualifying the domain within the username field for logon?  \\TEST.COM\username)

I still couldn't get it to work

 Just my two cent:
- did you edit the Makefile to compile elogd with kerberos (USE_KRB5   = 1)?
- did you look into the elogd logfile for error messages at start-up or at login time?
I can only say that I got it working right away - that is the case when you learn least.
Maybe you should post your specific software versions: operating system (in my case Scientific Linux 5.1 (Boron)), Kerberos version (klist -V), etc.
 
English (auto-detected) » English
 
  67611   Wed Nov 13 16:26:32 2013 Reply Olaf Kastenolaf.kasten@deutschebahn.comQuestionLinux2.9.2-1Re: kerberos authentication NOT working

Andreas Luedeke wrote:

Hal Proctor wrote:

Fabio Sella wrote:

Hi guys,

we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:

Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml

 
Detect language » Italian
 

 

Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.

We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.

Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?

Thanks

 I have asked for same help, and no one has answered with a solution on implementing a kerberos .  I saw exactly what you were seeing. (did you try fully qualifying the domain within the username field for logon?  \\TEST.COM\username)

I still couldn't get it to work

 Just my two cent:
- did you edit the Makefile to compile elogd with kerberos (USE_KRB5   = 1)?
- did you look into the elogd logfile for error messages at start-up or at login time?
I can only say that I got it working right away - that is the case when you learn least.
Maybe you should post your specific software versions: operating system (in my case Scientific Linux 5.1 (Boron)), Kerberos version (klist -V), etc.
 
English (auto-detected) » English
 

 I'm having same issue. Kerberos is working on Apache on same ubuntu 12.04 server. I used the USE_KRB5 option for compiling elog.

Does anyone  have an idea to solve that problem? 

  67315   Mon Aug 20 22:11:21 2012 Reply Szu-Ching Pecknerspeckner@nd.eduBug reportLinux2.9.2Re: kerberos authentication

Szu-Ching Peckner wrote:

Hello, I have

authentication = kerberos

kerberos Realm = xxx

I ran tcpdump and know elogd server did attempt to contact kerberos server. I could run kinit username@realm_name, and klist shows my ticket fine. 

I receive "kerberos error 256: Decrypt integrity check failed. Please check your kerberos configuration" when I entered my password wrong purposely on login page.

I receive "Invalid user name or password!' when I entered my correct password. 

Please advise. 

 

 

I forgot to mention, I also have Password file line in elogd.cfg file. Because without password file line, I wouldn't get login screen. I know my test account is not in the main.pwd file. I believe elogd does go to kerberos server to compare password. I just don't get why I get invalid username and password when I entered correct password, while kerberos error (expected) when I enter wrong password.  

Authentication = Kerberos

Kerberos Realm = xxx

Password file = main.pwd

ELOG V3.1.5-3fb85fa6