Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 710 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6458 Entries 
Goto page Previous  1, 2, 3 ... 709, 710, 711 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  67709   Fri Oct 24 12:51:00 2014 Warning Stefan Rittstefan.ritt@psi.chBug fixAllALLPOODLE vulnerability

IMPORTANT SECURITY ANNOUNCEMENT

Recently the POODLE vulnerability has been announced: http://en.wikipedia.org/wiki/POODLE 

ELOG is prone to this vulnerability if it runs directly the SSL protocol and can be accessed from the internet. If ELOG runs behind an Apache proxy, and the Apache server has been correctly configured (disabled the SSLv23 protocols), ELOG is safe as well.

To fix this vulnerability, ELOG needs to be recompiled after the attached patch has been applied. This prohibits ELOG to fallback to the insecure SSLv2 & v3 protocols and only use the safe TLSv1 protocol.

If you do not know how to recompile ELOG, please do not run ELOG directly accessible from the internet until the next binary release has been published.

/Stefan Ritt

Attachment 1: elogd.patch 
diff --git a/src/elogd.c b/src/elogd.c
index fac34f8..13c619f 100755
--- a/src/elogd.c
+++ b/src/elogd.c
@@ -2342,7 +2342,7 @@ int ssl_connect(int sock, SSL ** ssl_con)
    SSL_library_init();
    SSL_load_error_strings();
 
-   meth = (SSL_METHOD *) SSLv23_method();
+   meth = (SSL_METHOD *) TLSv1_method();
    ctx = SSL_CTX_new(meth);
 
    *ssl_con = SSL_new(ctx);
@@ -28902,7 +28902,7 @@ SSL_CTX *init_ssl(void)
    SSL_library_init();
    SSL_load_error_strings();
 
-   meth = (SSL_METHOD *) SSLv23_method();
+   meth = (SSL_METHOD *) TLSv1_method();
    ctx = SSL_CTX_new(meth);
 
    if (getcfg("global", "SSL Passphrase", pwd, sizeof(pwd))) {
  67752   Fri Jan 16 13:41:18 2015 Entry Eoin Butlereoin.butler@cern.chRequestAll-Configure default time range in 'Find'

Hello,

We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks in advance!

  67753   Fri Jan 16 14:29:58 2015 Reply Stefan Rittstefan.ritt@psi.chRequestAll-Re: Configure default time range in 'Find'

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

Eoin Butler wrote:

Hello,

We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks in advance!

 

  67754   Mon Jan 19 11:09:31 2015 Reply Eoin Butlereoin.butler@cern.chRequestAll-Re: Configure default time range in 'Find'

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
  67755   Mon Jan 19 17:17:32 2015 Idea David PilgramDavid.Pilgram@epost.org.ukRequestAll-Re: Configure default time range in 'Find'

Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom.  This gives a default of searching the last day, and one has to think and select the period of time to search back on.

I did this on my 2.9.2-2475 version, recompiled and it works.  Two lines of code changed and even my cr*ppy coding was up to the task.  I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality.  Back up everything first, though!

Eoin Butler wrote:

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

 

  67756   Tue Jan 20 00:58:58 2015 Warning David PilgramDavid.Pilgram@epost.org.ukRequestAll-Re: Configure default time range in 'Find'

It has just occurred to me that you may also have to check the non-English files, (./resorces/eloglang_xxxx) as this change introduces a new term "All time" that would need translation into the other lexicons.

 

By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly.  I trust that is what you're after, Eoin.  I'll keep my change to the coding, but that's personal choice.

David.

David Pilgram wrote:

Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom.  This gives a default of searching the last day, and one has to think and select the period of time to search back on.

I did this on my 2.9.2-2475 version, recompiled and it works.  Two lines of code changed and even my cr*ppy coding was up to the task.  I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality.  Back up everything first, though!

Eoin Butler wrote:

Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".

Stefan Ritt wrote:

Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.

 

 

  67757   Wed Jan 21 02:15:12 2015 Question devjoshi868b@gmail.comQuestionAll3.3filter with or operation/TIME DURATION CALCULATION

1.I HAVE A ELOG BOOK WITH TWO ATTRIBUTE 'FROM' &'TO'. I WANT TO USE A FILTER WHICH WILL SEARCH FOR A VALUE  IN BOTH ATTRIBUTE .KINDLY HELP ME.

2. HOW TO CALCULATE THE TIME DURATION  AUTOMATICALLY BASED ON TWO ATTRIBUTES 'START TIME' AND 'STOP TIME' .

  67758   Thu Jan 22 08:35:23 2015 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionAll3.3Re: filter with or operation/TIME DURATION CALCULATION

 

dev wrote:

1.I HAVE A ELOG BOOK WITH TWO ATTRIBUTE 'FROM' &'TO'. I WANT TO USE A FILTER WHICH WILL SEARCH FOR A VALUE  IN BOTH ATTRIBUTE .KINDLY HELP ME.

2. HOW TO CALCULATE THE TIME DURATION  AUTOMATICALLY BASED ON TWO ATTRIBUTES 'START TIME' AND 'STOP TIME' .

1a. If you go to the "Find" form, you can add filters on several attribute. The URL of the result page can be bookmarked: this is your filter.

1b. If you define quick filters on FROM and TO, then you can enter filters on both.

2. If you start elogd with the -x option, then you can execute scripts in the "subst" and "subst on edit" commands. Within those shell scripts you can use $START TIME and $STOP TIME to calculate the attributes value. Look for the "Subst" command in the documentation.

Goto page Previous  1, 2, 3 ... 709, 710, 711 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6