Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 380 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 379, 380, 381 ... 806, 807, 808   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  69275   Thu Dec 3 09:57:20 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows | Mac OSX | All | Other3.1.3Re: length of condition names

You can easily use multi-character conditionals, up to 256 chars.

Harry Martin wrote:

The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions.  I don't see any update/change to that rule anywhere in the docs.

I have been using multi-character condition names successfully.   I find these are easier to use since they can be more descriptive of each condition.   It works, but I am concerned I may be doing something that might not be supported going forward.   (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)

Thank you, again, for this fine (and, may I add, fun?) tool.  I'm having a good time with it!

 

  69276   Thu Dec 3 09:58:44 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.3Re: Options <...> vs ROptions <...>

For conditional attributes, you have to use Options, not ROptions. Maybe I will implement that one day, but only if I will have plenty of time...

Harry Martin wrote:

Same problem here, in version 3.1.3.   It would be very nice if this worked.

Wolfgang Bayer wrote:

According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

 

 

  69281   Tue Dec 15 15:19:25 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: Is there a way to upload a file in custom input?

When you submit a "normal" elog entry, you can click on "Choose file" to add an attachment. On a mobile device, you will then be asked to select a photo from your library or take one with your camera. You can do the same on a custom form. You have to extract the code from the normal submissoin form and program it on your custom page. It needs however some work and might not be straight forward.

Stefan

Satyajit Jena wrote:

Hi,

I am trying to implement a Custom input forms by following this  https://elog.psi.ch/elogs/Contributions/49. Is there a way to also insert an image or files to it? I want to take a snap from the iPad and want that to go as an attachment or attach a file(s) into the form. Is there a way to do that?

Your suggestions are highly appreciated.

Regards,

sjena

 

 

  69288   Fri Jan 8 13:47:14 2021 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.3Re: Path disclosure on unfound file

Ok, I fixed the code in the current commit (395e101add19f0fe8a11a25d0822e511f34d94d1). The path gets stripped, and we see a

prinnydood wrote:

I can confirm this issue exists on version 3.1.3, which I have installed elog on Debian 10.

The issue also exists on version 3.14 (1.20190113git283534d97d5a.el7), which I tested on an AmazonLinux EC2 instance.

This is what I found:

1. if I leave out the extension at the end of the URL for a non-existent page, it gives me the red error box. So far so good... Example: /gibberish

2. if I include any random extension at the end of the URL for a non-existent page, it gives me the red error box. So far so good... Example: /gibberish.php or /gibberish.htm or /gibberish.asdfasd

3. if I include any .html extension specifically at the end of the URL for a non-existent page, elog exposes the path /usr/share/elog/themes/default/gibberish.html. This is a bug... Example: /gibberish.html exposes the path, and likewise, /.gibberish.html ( "dot" + gibberish) exposes the path

4. if I include a valid, existent .html file which is located in the directory /usr/share/elog/themes/default/, and call it, elog exposes the html document. Example: I created an html file called gibberish.html (containing <html><body><p>Hello world</p></body></html>) in my system's /usr/share/elog/themes/default/ directory. After navigating back to the /gibberish.html URL, I was presented with the HTML file.

Turning on -v (verbose mode), the response by elogd when accessing these are: "GET /elog/gibberish.html HTTP/1.0 Returned 605 bytes" (displays "Hello world" html file), and "GET /elog/gibberish.asdfasd HTTP/1.0 Returned 605 bytes" (displays red error box).

=====

My guess: the program seems to be caring about the files ONLY if they have html file extension. Please see the screenshots below.

====

What are the security implications? Not much, I think. From what I can tell, exposing the "/usr/share/themes/elog" path, and also exposing the elog version when the file does not exist. Hope this reply helps anyone else with the same question.

(I am sure the error exposing the version can be removed by editing the source code--this is probably beyond my capabilities at this point).

 

  69290   Fri Jan 8 15:35:35 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.2Re: Parsing log files

Well, you could put the old options back to the config file, do the export, then remove them again.

But have a look at the Elog database files ZZMMDDa.log in your logbook directory, they are pure ASCII files, which are relatively simple to parse.

Hi John. The problem with using the Find-->Export method is that some of the Attributes for the older data are no longer shown on that screen because the Config file has since changed. That's why I'm contemplating somehow parsing the log files directly instead.

 

  69294   Thu Jan 14 14:05:19 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: elog slowness

Have you tried to restart the elogd server? The CLOSE_WAIT could be dangling network connections, which were not properly closed by the browser.

Giuseppe Cucinotta wrote:

We run elog on a server to provide a logbook for our laboratory. We noticed that elog is very slow on loading pages: browser pages spend a lot of time in charging (actually one can speed the procedure refreshing the page but it is quite annoying).

I checked the server load with top and it doesn't show any abnormal CPU or memory usage. Then I ran lsof and I noticed that there are more than 200 entries related to the same elog PID and labelled with CLOSE_WAIT.

My questions are: can the slowness of my logbook be due to the presence of all these CLOSE_WAIT entries (which seems if I understood well wait for a response)? If it's the case, how can I solve this issue?

Thanks

 

  69296   Tue Feb 2 07:43:49 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.4Re: Different Top Groups or Groups have the same logbook name

Unfortunately you have to name these top groups differently, because they are internally used for the database name.

MATT TERRON wrote:

I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'?

 

  69298   Tue Feb 2 08:25:46 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows3.1.4Re: Different Top Groups or Groups have the same logbook name

That's correct.

Stefan Ritt wrote:

Unfortunately you have to name these top groups differently, because they are internally used for the database name.

MATT TERRON wrote:

I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1 Maintenance Log' all the way to 'Department_X Maintenance Log'?

 

 

Goto page Previous  1, 2, 3 ... 379, 380, 381 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6