| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67294
|
Sun Jul 1 19:55:38 2012 |
 | Per Eriksson | pelle@sm4xiu.eu | Info | Linux | Any | Re: Compiling Elog for QNAP NAS x86 |
| Per Eriksson wrote: |
|
| Per Eriksson wrote: |
|
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per
|
I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)
Per
|
I managed to package Elog v2.92 build 2462 into and QNAP installer QPKG package.
This is for x86 based QNAP NAS only.
Note: You must have adduser package installed prior to installation.
Login to the NAS with SSH and type:
apt-get update
apt-get install adduser
BR,
Per |
| Attachment 1: Elog_2.9.2_2462.qpkg
|
|
67551
|
Wed Jul 24 02:19:17 2013 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | All | ALL | ELOG moved to GIT |
The ELOG repository has been moved from Subversion to GIT. While the old repository will be visible for some time, all new development is done on the GIT repository. To download the repository, do a
git clone https://bitbucket.org/ritt/elog.git
git clone https://bitbucket.org/tmidas/mxml.git
or access it online at https://bitbucket.org/ritt/elog/
/Stefan |
|
67709
|
Fri Oct 24 12:51:00 2014 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | ALL | POODLE 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))) {
|
|
854
|
Sun Dec 19 16:55:03 2004 |
 | Heiko Scheit | h.scheit@mpi-hd.mpg.de | | Linux | ? | forum entries not displayed in correct order |
I just submitted a reply to elog:847 (the reply is elog:853).
Normally the thead containing the reply should now be listed as
the top thread. Instead only the original message of the thread
(elog:820) is listed but the remaining messages in the thread are not
listed. It seems the problem is that for elog:820 the 'reply to this'
header is missing. And elog:820 and elog:824 are the same messages
except that for elog:824 the subject is missing. Actually ALL attributes
for elog:824 are missing.
I guess you could fix things up if you:
- add 'reply to this: 823' to elog:820
- remove entry elog:824 |
|
1152
|
Wed May 18 14:20:23 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | | ? | error message from this forum |
Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
|
1153
|
Wed May 18 19:52:41 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | ? | Re: error message from this forum |
| Heiko Scheit wrote: | Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
Sombody used an invalid formed email address, like user<at>domain<dot>com, on which the SMTP server complained. I would like to note here that the email addresses registered in this forum are not published in any way, so there is no risk to get spam from that (except the normal elog notifications, which can be turned off easily). |
|
66537
|
Tue Sep 8 14:55:41 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Other | Other | ? | Re: Elog stopped working |
| Gillian Sabberton wrote: |
|
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem... |
|
66538
|
Tue Sep 8 14:59:30 2009 |
| Gillian Sabberton | elog@gks.thamespower.com | Other | Other | ? | Re: Elog stopped working |
| Stefan Ritt wrote: |
|
| Gillian Sabberton wrote: |
|
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
You shoudl start elogd interactively in a DOS box to see if there is any error. Maybe disk full or a network problem...
|
It is running on a linux box, we have started in it in a telnet session, and no errors appear, as I am new to e-log is there an error log anywhere. |