Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 47 of 806  Not logged in ELOG logo
icon5.gif   elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Fri Aug 19 19:39:50 2016 
I was setting of a local test copy of my logbooks on my Windows 7 PC to begin testing automation of submissions without spamming the live logbooks. While trying to make entries from the command line I get an error that I am missing a required attribute. I have multiple attributes that have spaces in them an the verbose output indicates that the space in the name is being changed to an underscore. Is this the expected behavior or a bug when submitting to the elog client in Windows?

Command being entered:

Quote:
C:\Program Files (x86)\ELOG>elog -h 127.0.0.1 -p 443 -s -l "Oceana Logbook" -u j
ohn.smith john.smith -v -n 0 -a Platform=LSOT -a "Start Time"="Fri, 19 Aug 2016
12:58:01 -0500" -a "Author=John Smith" -a "Device=2H111-1" -a "Action Type"=Mai
ntenance -a "Maint Type"=Unscheduled -a "System=Device" -a "Downtime=No" -a "Man
Hours"=1.0 -a MAF="" -a "Lost Time"="" -m "testing"

You can see where I have multiple attributes with spaces. Below you see where the name shows an underscore instead of a space.


Quote:
Successfully connected to host 127.0.0.1, port 443
Request sent to host:
POST /Oceana+Logbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------22C602B76
C41
Host: 127.0.0.1:443
User-Agent: ELOG
Content-Length: 1790


Content sent to host:
---------------------------22C602B76C41
Content-Disposition: form-data; name="cmd"

Submit
---------------------------22C602B76C41
Content-Disposition: form-data; name="unm"

john.smith
---------------------------22C602B76C41
Content-Disposition: form-data; name="upwd"

JUl77l/.kXYBzfoOZpsy.URRZEZpg2SHZNZIum6Rh/5
---------------------------22C602B76C41
Content-Disposition: form-data; name="exp"

Oceana Logbook
---------------------------22C602B76C41
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------22C602B76C41
Content-Disposition: form-data; name="Platform"

LSOT
---------------------------22C602B76C41
Content-Disposition: form-data; name="Start_Time"

Fri, 19 Aug 2016 12:58:01 -0500
---------------------------22C602B76C41
Content-Disposition: form-data; name="Author"

Bruce Slack
---------------------------22C602B76C41
Content-Disposition: form-data; name="Device"

2H111-1
---------------------------22C602B76C41
Content-Disposition: form-data; name="Action_Type"

Maintenance
---------------------------22C602B76C41
Content-Disposition: form-data; name="Maint_Type"

Unscheduled
---------------------------22C602B76C41
Content-Disposition: form-data; name="System"

Device
---------------------------22C602B76C41
Content-Disposition: form-data; name="Downtime"

No
---------------------------22C602B76C41
Content-Disposition: form-data; name="Man_Hours"

1.0
---------------------------22C602B76C41
Content-Disposition: form-data; name="MAF"


---------------------------22C602B76C41
Content-Disposition: form-data; name="Lost_Time"


---------------------------22C602B76C41
Content-Disposition: form-data; name="Text"

testing 123
---------------------------22C602B76C41

Response received:
HTTP/1.1 404 Not Found
Server: ELOG HTTP 3.1.1-3f311c5
Content-Type: text/html;charset=ISO-8859-1
Connection: Close

<!DOCTYPE html>
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG error</title>
<link rel="stylesheet" type="text/css" href="elog.css">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding="1" cellspacing="0"<tr><td class
="errormsg"><i>Error: Attribute <b>Start Time</b> not supplied.</i><p>
Please go back and enter the <b>Start Time</b> field.
</td></tr>
<tr><td class="errormsg"><script language="javascript" type="text/javascript">
document.write("<button type=button onClick=history.back()>Back</button>");
</script>
<noscript>
Please use your browser's back button to go back
</noscript>
</td></tr>
</table>
</center></body></html>

Error: Missing required attribute "Start Time"

icon4.gif   elog client can set arbitrary values to locked attributes, posted by David Potterveld on Mon Nov 10 16:56:08 2008 

When submitting entries via the elog client, I find that I can set arbitrary values for attributes that are supposedly "preset" and "locked".

As an example, I have in my elogd.cfg file:

[global]

...

Group Operations = Accelerator

Top group ATLAS = Operations

...

[global ATLAS]

Attributes = Experiment, Author, Author Email, Category, Subject
Required Attributes = Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
Extendable Options = Category

Preset Experiment =
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Experiment, Author, Author Email

...

[Accelerator]
Attributes = Author, Author Email, Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other

...

This works as intended with a web client (firefox). The Author and Author Email attributes are preset and unchangeable.

However, if I use the elog client, as in:

elog -v -h my.apache-proxy.server -d elog -l Accelerator -p 443 -s -u johndoe xxxxx -a Category=LN -a Subject=Test -a Author=IDoNotExist -n 1 -m entry.txt 
(johndoe is an existing user)

 
The entry is created with "IDoNotExist" as the Author name, instead of the correct name for the user johndoe,
and the Author Email attribute is blank.

Is there a way to enforce preset and locked attributes in the elogd server? (As a client could connect
with any arbitrary software, not just elog.)



icon5.gif   elog client binary with webserver authentication, posted by Devin Bougie on Wed May 11 02:59:53 2016 
Is it possible to submit entries using the elog client binary when the server is configured with webserver authentication (when the server requires the X-Forwarded-User header)?  One option would be if the server could support both webserver and kerberos (or even file) authentication, but neither 
"Authentication = Webserver, Kerberos" nor "Authentication = Webserver, File" seem to work.

In addition to using the elog binary to talk to the elog server directly, we've unsuccessfully tried using curl to post data to the apache server url (URL in elogd.cfg).  We can read entries using curl, but haven't yet been able to submit entries.

Any help would be greatly appreciated.

Many thanks,
Devin
icon5.gif   elog client authentication and attachment comment, posted by Yoshio Imai on Thu Apr 6 20:24:06 2006 
Hi again!

I have two questions, one concerning authentication methods for the elog client. Until revision 1642, it was possible to submit entries to a password-protected logbook using the elog client without supplying authentication information. With revision 1671 this is no longer possible. In principle this is good. However, many of our run control programs use the elog client (via rsh to the elog server computer) to submit automatic entries, which fails now. In order for this mechanism to work again, we would have to change the command-line call in the sources, including now the password in clear text. Since this can be considered a security issue, we would like to avoid it if at all possible. I guess my request would go in the direction of PAM support, but would it be possible to revert to the old behaviour as an option? (If you tell me where in the code to look, we could probably also comment out the respective lines ourselves so that you don't have extra work...)

The second remark is about attachment comments. When editing a logbook entry, the attachment upload buttons appear again, but without the comment. Shouldn't it be there, too?

Thanks,

Yoshio
icon4.gif   elog c++ and LDAP, posted by Laurent Jean-Rigaud on Wed Feb 16 22:24:18 2022 

Hi Stefan,

I've seen that ELOG is build now with gcc-c++ now, so i tried to check rpmbuild script with all options. It seems that ldap api is different with c++ (quick search : https://www.openldap.org/lists/openldap-software/200706/msg00177.html) and elogd can not been build anymore with ldap support. :-(

# make
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -DHAVE_PAM -c -o mxml.o mxml/mxml.cxx
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -DHAVE_PAM -w -c -o crypt.o src/crypt.cxx
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -DHAVE_PAM -c -o strlcpy.o mxml/strlcpy.cxx
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -DHAVE_PAM -o elog src/elog.cxx mxml.o crypt.o strlcpy.o -lssl -lkrb5 -lldap -llber -lpam -llber
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -DHAVE_PAM -w -c -o auth.o src/auth.cxx
src/auth.cxx: In function ‘int auth_verify_password_ldap(LOGBOOK*, const char*, const char*, char*, int)’:
src/auth.cxx:283:60: erreur: ‘ldap_simple_bind_s’ was not declared in this scope
    bind = ldap_simple_bind_s(ldap_ld, ldap_bindDN, password);
                                                            ^
src/auth.cxx:290:26: erreur: ‘ldap_unbind’ was not declared in this scope
       ldap_unbind(ldap_ld);
                          ^
src/auth.cxx:295:23: erreur: ‘ldap_unbind’ was not declared in this scope
    ldap_unbind(ldap_ld);
                       ^
src/auth.cxx: In function ‘int ldap_adduser_file(LOGBOOK*, const char*, const char*, char*, int)’:
src/auth.cxx:323:60: erreur: ‘ldap_simple_bind_s’ was not declared in this scope
    bind = ldap_simple_bind_s(ldap_ld, ldap_bindDN, password);
                                                            ^
src/auth.cxx:330:26: erreur: ‘ldap_unbind’ was not declared in this scope
       ldap_unbind(ldap_ld);
                          ^
src/auth.cxx:358:26: erreur: ‘ldap_unbind’ was not declared in this scope
       ldap_unbind(ldap_ld);
                          ^
src/auth.cxx:369:62: erreur: ‘ldap_get_values’ was not declared in this scope
          if((values = ldap_get_values(ldap_ld,entry,attribute)) != NULL ) {
                                                              ^
src/auth.cxx:378:35: erreur: ‘ldap_value_free’ was not declared in this scope
             ldap_value_free(values);
                                   ^
src/auth.cxx:386:23: erreur: ‘ldap_unbind’ was not declared in this scope
    ldap_unbind(ldap_ld);
                       ^
src/auth.cxx: In function ‘int elog_conv(int, const pam_message**, pam_response**, void*)’:
src/auth.cxx:451:59: erreur: invalid conversion from ‘void*’ to ‘pam_response*’ [-fpermissive]
    if((*resp = calloc(num_msg, sizeof(struct pam_response))) == NULL)
                                                           ^
src/auth.cxx:456:33: erreur: invalid conversion from ‘void*’ to ‘const char*’ [-fpermissive]
    if(!(resptok = strdup(my_data))) {
                                 ^
In file included from src/elogd.h:46:0,
                 from src/auth.cxx:30:
/usr/include/string.h:172:14: erreur:   initializing argument 1 of ‘char* strdup(const char*)’ [-fpermissive]
 extern char *strdup (const char *__s)
              ^
src/auth.cxx: In function ‘int auth_verify_password(LOGBOOK*, const char*, const char*, char*, int)’:
src/auth.cxx:593:73: erreur: invalid conversion from ‘const char*’ to ‘char*’ [-fpermissive]
          if (get_user_line(lbs, user, NULL, NULL, NULL, NULL, NULL, NULL) == 2) {
                                                                         ^
In file included from src/auth.cxx:30:0:
src/elogd.h:282:5: erreur:   initializing argument 2 of ‘int get_user_line(LOGBOOK*, char*, char*, char*, char*, BOOL*, time_t*, int*)’ [-fpermissive]
 int get_user_line(LOGBOOK * lbs, char *user, char *password, char *full_name, char *email,
     ^
make: *** [auth.o] Erreur 1
 

Regards,

Laurent

icon5.gif   elog as a service in windows not detect Imagemagick, posted by Diego Obradors Campos on Mon Dec 13 20:59:07 2010 

I have installed elog 2.8 in a windows pc with the installer from the distribution, it installs elog as a windows service, which is started automatically when windows starts.

It is done as:

"C:\Archivos de programa\ELOG\elogd.exe" -D -c "C:\Archivos de programa\ELOG\elogd.cfg"

Moreover Imagemagick and GhostScript are in the path:

Version: ImageMagick 6.6.4-6 2010-09-21 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2010 ImageMagick Studio LLC
Features: OpenMP 

However the indexing loogbooks are only working  fine when elog is started interactively.  Is there any posiblity to start elog as a service and use thumbnails for quick preview?

Thank you in advance!

 

icon5.gif   elog allows me to create user "blahblah ", posted by Dimitrios Tsirigkas on Fri Feb 3 18:15:47 2006 
Hi,

I noticed that when I register a username that contains whitespaces (eg "boing "), elog allows me to create the user of that name and updates the password file accordingly. It doesn't log me in, but it gives me no error message either. I also found that if I repeat the process it adds yet another entry in the password file, by the same name "boing ". Is that a bug or is there something wrong with my configuration?

Cheers,
Dimitris
icon4.gif   elog 2.8.0 as daemon crashes when editing selected threaded list, posted by Mark Bergman on Tue Sep 14 01:15:22 2010 

I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed" to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, and then edit it, to change the status field for all posts in the thread to "closed".

Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.

However, if eLog is run with "-v" in place of "-D", it does not crash.

 

Environment:

        CentOS 5.4

        eLog 2.8.0 built Aug  5 2010, 12:24:11

 

ELOG V3.1.5-3fb85fa6