Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 761 of 807  Not logged in ELOG logo
    icon2.gif   Re: Using Reply option, posted by Andreas Luedeke on Tue Jul 12 19:39:04 2016 

Preset on reply Author = $long_name
Cheers, Andreas

Jason S wrote:

Forgive me I'm not incredibly Elog savy yet.

A little backround about this log book -  I have our log set up as individual user names.  The log book is designed for entrys to be made when a process shutdown needs to be bypassed.  The operator will create an entry and submit it.  Then a supervisor will come in after and review/approve it.  I've removed the edit function,  but left the "Reply" option available for the supervisor to go into the same entry and check off the "Reviewed" attribute.  When the reviewed attribute is checked off, even with a different logged in author the next entry ID still shows the original author that put in the entry rather then the author who clicked reviewed.  If there a way to get around this?

[Process Bypass]
Comment = (Not in use right now, currently developing)
Attributes = Author, Date/Time of Bypass, Equipment Name, Device Tag, Supervisor Sign-off,
Moptions Supervisor Sign-off = Reviewed
List Menu commands = New, Find, Logout
Menu Commands = New, Find, Reply, Logout
Required Attributes = Date/Time of ByPass, Equipment Name, Device Tag
 

 

 

    icon3.gif   Re: Escape character [ or ] doesn't work within [url], posted by Andreas Luedeke on Mon Jul 18 23:37:22 2016 

The URL encoding of ']' as '%5D' appears to work:

[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]

Cheers, Andreas

Don wrote:

Here is the problem:

[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]

How can I escape [] inside url tag?

\[\] seems not working.

 

    icon2.gif   Re: string length limit in url tag, posted by Andreas Luedeke on Thu Jul 21 06:15:44 2016 
Several strings in ELOG are limited to 256 chars. It is likely the limit for URLs, too.
The magic number "256" appears 285 times in the elogd.c file.
It is probaly easier if you compress long URLs with goo.gl
Cheers, Andreas
Don wrote:

What is the string length limit in url tag and how to increase it?

For example,

[url=http://example.com?<text_string>]click here[/url]

When I provide very long <text_string>, it was truncated and showed partial link only.

 

    icon2.gif   Re: Sample of actual elog Config with URL in SSL, posted by Andreas Luedeke on Thu Aug 4 21:53:37 2016 

Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.

You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.

Cheers, Andreas

 

how do I compile elogd with USE_SSL=1?

Andreas Luedeke wrote:

You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".

And elogd must be compiled with USE_SSL=1, maybe that's your problem?

In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.

Cheers, Andreas

Dawang wrote:

HI Guys,

Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?

Thanks,

 

Raymund

 

 

 

    icon2.gif   Re: Sample of actual elog Config with URL in SSL, posted by Andreas Luedeke on Tue Aug 9 14:01:04 2016 

You need to download the source file package of ELOG and compile it. If you don't know what a Makefile is, then it is likely futile for you to attempt to compile ELOG.

Or in other words: you cannot use SSL.

Chris Smyth wrote:

By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?

I have added

port = 443

ssl = 1

Without sucess.

I then tried

port = 443

use_ssl = 1

still no sucess.

I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2)  reading all the documentation I cant seem to figure it out.

I also configured elogd to listen on port 443

Opened a CMD window and entered >elogd -p 443

Says listening on port 443 but still not working.

On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.

Andreas Luedeke wrote:

Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.

You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.

Cheers, Andreas

 

how do I compile elogd with USE_SSL=1?

Andreas Luedeke wrote:

You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".

And elogd must be compiled with USE_SSL=1, maybe that's your problem?

In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.

Cheers, Andreas

Dawang wrote:

HI Guys,

Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?

Thanks,

 

Raymund

 

 

 

 

 

    icon2.gif   Re: Sample of actual elog Config with URL in SSL, posted by Andreas Luedeke on Tue Aug 9 14:08:20 2016 

You've already named your solution: drop the very old ELOG version and download the new one. Obviously it was compiled with USE_SSL and you can use it right away.

Since you probably don't even have the source files of the old version, you'll have no chance to make it work with that. Just use ELOG 3.1.0.

Chris Smyth wrote:

By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?

I have added

port = 443

ssl = 1

Without sucess.

I then tried

port = 443

use_ssl = 1

still no sucess.

I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2)  reading all the documentation I cant seem to figure it out.

I also configured elogd to listen on port 443

Opened a CMD window and entered >elogd -p 443

Says listening on port 443 but still not working.

On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.

Andreas Luedeke wrote:

Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.

You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.

Cheers, Andreas

 

how do I compile elogd with USE_SSL=1?

Andreas Luedeke wrote:

You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".

And elogd must be compiled with USE_SSL=1, maybe that's your problem?

In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.

Cheers, Andreas

Dawang wrote:

HI Guys,

Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?

Thanks,

 

Raymund

 

 

 

 

 

    icon2.gif   Re: Quick Filter not searching on Enter, posted by Andreas Luedeke on Thu Aug 11 09:18:27 2016 

I've checked for this forum logbook, and pressing "enter" while having focus in the quickfilter text field does initiate the search. Does it work for you with this logbook?

Alan Grant wrote:

With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?

 

    icon2.gif   Re: elog client cmd line submission of attributes with spaces., posted by Andreas Luedeke on Sat Aug 20 12:17:10 2016 
If the "Start Time" attribute is of the type "datetime", then you cannot assign a date string to it.
Instead you'll have to assign the seconds of the epoch.
Try assigning a "0", that should be the 1st of January 1970.

I hope that helps,
Andreas

Darren Hollinrake wrote:
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"

ELOG V3.1.5-3fb85fa6