ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66435
|
Mon Jul 6 17:20:36 2009 |
| Mike | mike@raghuexim.com | Bug report | Linux | 2.7.6-2207 | Page Expired, Duplicate Entries & Thumbnail Woes? | Have a few issues here. The big one is that I have some users of our elog books
that are in India, while the server is in USA. When they click on thumbnail images
then press their browser back-button they get a page expired message and are
unable to see what they were looking at before unless they go back to the main
page. Is this an elog problem or something with Apache?
Also when these users in India write messages sometimes we end up with
duplicate messages seconds apart. I'm not sure if they are pressing the submit
button repeatedly or pressing their browser back button. I've suggested they
try not to do that.
Last issue, is there a way to make thumbnail images open in a new window
by default rather then the same window? This would help fix the first issue at
least. Is there some setting to fix the page expiration/time-out issues?
Regards,
Mike |
67554
|
Fri Aug 30 13:27:56 2013 |
| Nicolas FRANCOIS | nicolas.francois@free.fr | Question | Linux | 2.9.2 | Packaging ELOG for Debian | Hi.
I'd like to package ELOG for the new Debian. I'm a complete beginner in
this matter, but I spent some time configuring it for my desktop.
Could you help me do this (links to package maintainance, Elog tips,
security, former package maintainer...) ?
Thanks for any help.
--
Nicolas FRANCOIS | /\
http://nicolas.francois.free.fr | |__|
X--/\\
We are the Micro$oft. _\_V
Resistance is futile.
You will be assimilated. darthvader penguin
|
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 |
69527
|
Fri May 6 21:12:11 2022 |
| Konstantin Olchanski | olchansk@triumf.ca | Info | Linux | all | PDF preview special steps to enable | Ubuntu LTS 20.04 and others have elog PDF preview disabled by default. To enable,
please follow these steps, see https://daq00.triumf.ca/DaqWiki/index.php/Ubuntu#Enable_elog_PDF_preview
Enable elog PDF preview
see https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion
xemacs -nw /etc/ImageMagick-6/policy.xml
remove this section at the end:
<!-- disable ghostscript format types -->
<policy domain="coder" rights="none" pattern="PS" />
<policy domain="coder" rights="none" pattern="PS2" />
<policy domain="coder" rights="none" pattern="PS3" />
<policy domain="coder" rights="none" pattern="EPS" />
<policy domain="coder" rights="none" pattern="PDF" />
<policy domain="coder" rights="none" pattern="XPS" />
K.O. |
69055
|
Tue Nov 5 21:42:50 2019 |
| David Wallis | wallis@aps.anl.gov | Question | Linux | V3.1.4-ba84827 | PAM authentication question | I'm testing the PAM authentication feature, and have a couple questions, a suggestion, and a comment.
First the comment... it was pretty easy to get working, and is exactly what we need here, so thanks! Our PAM stack here is designed to allow logins with Active Directory, LDAP, or local accounts, so the PAM option preserves all of that.
The suggestion: In order to make it work, I had to add a symbolic link in /etc/pam.d:
elogd -> system-auth
That might be considered for addition to the documentation (this was on Red Hat Enterprise Linux 7.7)
The questions:
- The docs indicate that "Self register" must be set to >= 1, but in the code (elogd.c, line 26453), if the PAM module is enabled, Self register is overriden to 0. The result is that no "register as new user" link is displayed on the login screen. Is that the intent?
- Related... can PAM and File authentication both be enabled? We have some logbooks that are used by both internal people (with an A/D account) and outside collaborators that get local elog accounts. This works with LDAP + File, can it work with PAM?
Thanks in advance! |
2067
|
Thu Nov 9 23:52:26 2006 |
| An Thai | thaithan@gmx.de | Info | Windows | V2.6.2-175 | Outlook, Outlook Express and Free Webmail have problem with <br /> | If users reply an entry, the notification email cannot be displayed correctly in Outlook, Outlook Express and Webmail.
I look at the source code and see <br />. It could be the reason. |
66000
|
Mon Oct 13 15:24:29 2008 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.5-2130 | Options selections wipes locked date entry | I have two logbooks running, one for current accounts and one for non-active ones. The idea is to move an entry from one logbook to the other once an account becomes non-active. Both logbooks share some attributes (e.g. the name of the account, its creation date, ...), but both also have some uniqe attributes.
While I was playing with this set-up, I ran into a problem:
- Move an existing entry from current to non-active.
- "Type" and "Status" have options. "Created" and "Archived" are in date format.
- "Created" and "Type" are supposed to be locked in non-active. This works.
- "Archived" and "Status" are empty, as they do not exist in current. This also works.
- Depending on the "Type", only certain of the additional attributes are shown on edit. This works as well.
- I would also like "Status" to have some influence on how certain other attributes are preset and/or shown. This is where the problem starts...
- Edit the entry in current.
- As expected, "Created" and "Type" are shown as locked.
- As soon as I change the selector for "State", the whole edit mask is redrawn - and the date shown in "Created" is deleted.
I've been experimenting with this quite a while and as far as can see the following applies:
- Only date format attributes are affected
- Only locked attributes seem to be deleted completely
- If I have a date attribute that is not locked and I set it partially in the edit mask (e.g. only select the month or enter a year), it is also deleted
- If I have a date attribute that is not locked and I set it completely in the edit mask (i.e. day, month and year), it is not deleted
During the experiments I came up with a stripped down version of the non-active logbook configuration, which does show the bug. It only contains Type, Created, Status, Archived. To make an entry to experiment, you'll have to comment out the "Locked attributes" line, make a new entry (with "Created" date), the uncomment that line.
I hope my description isn't too confusing - please don't hesitate to ask if anything is unclear. I'd be much obliged if you saw a chance to fix this at some point...
Best regards,
Thomas |
679
|
Tue Aug 31 20:29:20 2004 |
| Patricio Castro | pato.castro@terra.cl | Question | Linux | 2.5.3 | Options Items limits | Hello friends,
Exist some form to increase limits of items (100) in the Options List
Thanks for any help |
|