ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
2098
|
Tue Nov 28 12:48:47 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.6.3 | Version 2.6.3 released today |
Dear ELOG users,
ELOG version 2.6.3 has been released today. It contains all the bug fixes, security fixes and a few new features collected since the last release which was actually almost half a year ago. The changelog contains all the details.
Due to the security fixes it is recommended to upgrade from any version prior to 2.6.3. Please note that the location of all password and log files has been moved from the main elog directory to the logbook directory. This means that after upgrading you have to move your password file manually, otherwise you cannot log in any more. This modification was requested because some ELOG installations (especially ones with top groups) can now have a read-only main directory.
Stefan Ritt |
68070
|
Tue Aug 4 15:35:39 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 3.1.1 | Version 3.1.1 of elog has been released |
Version 3.1.1, released August 4th, 2015
-
Updated CKEditor to version 4.5.1
-
Implemented "Date/Time format <attribute> = ..."
-
Implemented "Use Email Subject Edit = ..."
-
Replaced "Back" by "Delete" button
-
Fixed many issues with Draft Messages
-
CSS file is now in *addition* to the default file elog.css
-
Added LDAP documentation
-
Added "Logout to URL = ..." option
-
Added description of Apacher server authentication
|
1137
|
Mon May 9 20:23:59 2005 |
| Steve Jones | steve.jones@freescale.com | Question | Linux | Other | 2.5.9 | Version of GCC to use? |
What is the recommended version of gcc to use with elog 2.5.9? I searched
the discussion database but found nothing pertaining to this.
Thanks |
68908
|
Sun Mar 10 01:07:53 2019 |
| Ederag | edera@gmx.fr | Bug report | Linux | 3.1.4 | Very long URLs in message list corrupt layout |
First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.
When there is a very long URL in a message in "plain" encoding,
and this message is displayed in a list of messages,
a very long scrollbar appears at the bottom (same "scroll width" as the URL)
and some tabs and and dropdowns (filters) are unreachable without scrolling.
This does not happen if
- the message is displayed in single message page
- the message has a ELCode encoding
The exact version used is
0b9f7ed0 Merge branch 'develop'
There are no relevant instructions in elog.css for .messagelist,
and I did not find any obvious fix in the source code. |
68637
|
Fri Jul 14 13:11:48 2017 |
| Daniel Sajdyk | daniel.sajdyk@gmail.com | Info | Windows | latest | Virus in latest elog? |
Hello.
Today I wanted to download latest elog version, and got information from Eset Endpoint Antyvirus, that downloaded file has trojan horse "Generic.GQWFFXB".
It this false positive alarm?
Daniel
|
Attachment 1: elog.png
|
|
69483
|
Thu Mar 3 08:26:40 2022 |
| Alessandro Petrolini | alessandro.petrolini@cern.ch | Question | Windows | 3.1.4-a04faf9f | Vulnerability? |
Hi, I have been using elog for years at CERN.
Now I installed in my local workstation at my home inistitue
and sysadmin reported the following vulnerabilities:
- Configuration File Disclosure (CVE-2019-3992)
- Password Hash Disclosure (CVE-2019-3993)
- Use After Free (CVE-2019-3994)
- NULL Pointer Dereference (CVE-2019-3995)
- Unintended Proxy (CVE-2019-3996)
Am I doing soimething wrong?
sysadmin will not allow me to use it until it is fixed....
Any help is welcome.
|
65933
|
Thu Jul 24 11:21:54 2008 |
| Franck C | franck.c95@free.fr | Question | Windows | | WINDOWS binaries with latest fixes. |
Hi,
When the WINDOWS binaries with the latest bug fixes will be available on the download page ?
Have a nice day |
614
|
Fri Jul 16 17:51:52 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | WISHLIST: Type <attribute> = user |
Something to add to the wishlist:
- Type <attribute> = user
This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line.
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames. |