ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69009
|
Tue Aug 20 11:37:03 2019 |
| Lech | subs@lwp.email | Question | Linux | 3.1.3 | Re: Drag and drop does not work in 3.1.3? | Can I find the config of the demo elog somewhere, so I could try it locally?
Stefan Ritt wrote: |
The Drag & Drop was implemented already in 3.0.0 (see https://elog.psi.ch/elog/download/ChangeLog). So no idea why it's not working for you.
Stefan
Lech wrote: |
Hello,
I can paste images into text (which resulted in the text_size too long error message), however, I can't drop them on my elog. However, I can do it on the demo version. Was the drag and drop into text already supported in version 3.1.3 and I am just missing some configuration option, or do I need to find a repository with a more recent version of elog?
Thanks!
|
|
|
69011
|
Tue Aug 20 13:28:53 2019 |
| Lech | subs@lwp.email | Question | Linux | 3.1.3 | Re: Drag and drop does not work in 3.1.3? | Thank you. Locally doesn't work for some reason... I'll try to investigate.
Btw. do you plan to properly accept pasting of images? Pasting a screenshot saves a lot of time when making logs.
Stefan Ritt wrote: |
It's the config from the distribution. A copy is below.
Stefan
[global]
port = 8080
[demo]
Theme = default
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject, Pinned
Options Pinned = boolean
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Last default = 31
Lech wrote: |
Can I find the config of the demo elog somewhere, so I could try it locally?
Stefan Ritt wrote: |
The Drag & Drop was implemented already in 3.0.0 (see https://elog.psi.ch/elog/download/ChangeLog). So no idea why it's not working for you.
Stefan
Lech wrote: |
Hello,
I can paste images into text (which resulted in the text_size too long error message), however, I can't drop them on my elog. However, I can do it on the demo version. Was the drag and drop into text already supported in version 3.1.3 and I am just missing some configuration option, or do I need to find a repository with a more recent version of elog?
Thanks!
|
|
|
|
|
69014
|
Wed Aug 21 02:21:57 2019 |
| Lech | subs@lwp.email | Question | Linux | 3.1.3 | Re: Drag and drop does not work in 3.1.3? | From what I've read in a past post, it is hitting the max content length because pasting, unlike dropping, is not properly supported and it is possible that images get converted to text in some way and occupy a lot of "content length". So what I mean is that the pasted image is handled the same way as the dropped image.
Btw. adjusting the Max content length, according to the message, requires recompilation of the program, so it is not only a matter of configuration.
Andreas Luedeke wrote: |
> Btw. do you plan to properly accept pasting of images?
I would claim it is already properly supported. If you hit a size limit you can configure your ELOG to adjust the limit (Max content length ).
Or did I misunderstand your question?
Lech wrote: |
Thank you. Locally doesn't work for some reason... I'll try to investigate.
Btw. do you plan to properly accept pasting of images? Pasting a screenshot saves a lot of time when making logs.
Stefan Ritt wrote: |
It's the config from the distribution. A copy is below.
Stefan
[global]
port = 8080
[demo]
Theme = default
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject, Pinned
Options Pinned = boolean
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Last default = 31
Lech wrote: |
Can I find the config of the demo elog somewhere, so I could try it locally?
Stefan Ritt wrote: |
The Drag & Drop was implemented already in 3.0.0 (see https://elog.psi.ch/elog/download/ChangeLog). So no idea why it's not working for you.
Stefan
Lech wrote: |
Hello,
I can paste images into text (which resulted in the text_size too long error message), however, I can't drop them on my elog. However, I can do it on the demo version. Was the drag and drop into text already supported in version 3.1.3 and I am just missing some configuration option, or do I need to find a repository with a more recent version of elog?
Thanks!
|
|
|
|
|
|
|
69015
|
Wed Aug 21 07:00:17 2019 |
| Lech | subs@lwp.email | Question | Linux | 3.1.3 | Re: Drag and drop does not work in 3.1.3? | I've discovered, that if I switch my local elog to SSL, dropping of images starts to work (as expected). However... pasting stops. If I select "paste" popup, I got the message about my browser security settings not allowing to paste, and that I can paste in the popup window. In Firefox I can actually paste in the popup window (image appears there), but after clicking OK nothing appears in the editing window. In Chrome and Opera nothing appears even in the popup window. I played with FF security settings, enabling pasting for elog sites (both local and the demo on this site) as advised in many places on the internet, but it doesn't help. This may be a CKInter issue, although interesting that it works without SSL (and not properly, resulting in too big text being stored)
Lech wrote: |
From what I've read in a past post, it is hitting the max content length because pasting, unlike dropping, is not properly supported and it is possible that images get converted to text in some way and occupy a lot of "content length". So what I mean is that the pasted image is handled the same way as the dropped image.
Btw. adjusting the Max content length, according to the message, requires recompilation of the program, so it is not only a matter of configuration.
Andreas Luedeke wrote: |
> Btw. do you plan to properly accept pasting of images?
I would claim it is already properly supported. If you hit a size limit you can configure your ELOG to adjust the limit (Max content length ).
Or did I misunderstand your question?
Lech wrote: |
Thank you. Locally doesn't work for some reason... I'll try to investigate.
Btw. do you plan to properly accept pasting of images? Pasting a screenshot saves a lot of time when making logs.
Stefan Ritt wrote: |
It's the config from the distribution. A copy is below.
Stefan
[global]
port = 8080
[demo]
Theme = default
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject, Pinned
Options Pinned = boolean
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Last default = 31
Lech wrote: |
Can I find the config of the demo elog somewhere, so I could try it locally?
Stefan Ritt wrote: |
The Drag & Drop was implemented already in 3.0.0 (see https://elog.psi.ch/elog/download/ChangeLog). So no idea why it's not working for you.
Stefan
Lech wrote: |
Hello,
I can paste images into text (which resulted in the text_size too long error message), however, I can't drop them on my elog. However, I can do it on the demo version. Was the drag and drop into text already supported in version 3.1.3 and I am just missing some configuration option, or do I need to find a repository with a more recent version of elog?
Thanks!
|
|
|
|
|
|
|
|
900
|
Wed Feb 2 10:37:48 2005 |
| Laurent S. Nadolski | nadolski@synchrotron-soleil.fr | Bug report | Linux | Windows | V2.5.6-1 | Conditional attributes does not work in French | Hi,
I am very much interested in using elog as a shift logbook for SOLEIL
accelerators.
I tested most of the options. Every thing works well except the conditional
attributs when French language is selected. In this case, I lost the
selected list option in the Field Equipement.
Here a simple exemple for testing.
NB: tests were done using the last and before last elog version.
I switched the language from English to French in Global options
Attributes = Accelerateur, Equipement
Options Accelerateur= Linac{1}, LT1{2}
{1}Options Equipement= cannon, section1
{2}ROptions Equipement= Alimentation, Diagnostics
I guess this is a simple bug since this problem does not exist for other
languages.
Best Regards,
Laurent Nadolski |
1253
|
Mon Jul 11 11:16:59 2005 |
| Laurent S. Nadolski | nadolski@synchrotron-soleil.fr | Bug report | Linux | 2.6 and be | icon comment not display using firefox | Hi,
I found out the following bug.
Icon comment are not displayed when browsing with firefox. But it works fine with IE.
A goo test page is this very elog entry.
If you move your mouse on a icon nothing will be displayed using Firefox.
In the following example, I noticed, that the tooltip Icon is displayed instead (whenever existing).
This means, it displays info (for all icons if several) and not "showbug" on icon1.gif
Attributes = Icone
IOptions Icone = icon1.gif
Tooltip Icone = info
Icon comment icon1.gif = showbug
Thanks for your help,
Laurent. |
69091
|
Fri Jan 24 17:33:14 2020 |
| Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | V3.1.4-283534d | Re: PAM authentication question | Hi,
First, thanks to ELOG tool !
I'm trying to swicth a ELOG 3.1.2 server with local passwd DB to GIT version builded with SSL/PAM/LDAP options. I reuse the buildrpm script which generates correctly RPM files.
After installing on EL6 x86_64 server, i update the elogd.conf file according to GIT version doc :
- Authentication = PAM
- Password file = /usr/local/elog/elog_users.pam (new file as i want to keep the old local DB)
- Self register = 3
I add a link for pam module :
$ ll /etc/pam.d/elogd
lrwxrwxrwx 1 root root 11 Jan 24 16:23 /etc/pam.d/elogd -> system-auth
elogd starts well
elogd 3.1.4 built Jan 24 2020, 07:34:02 revision 283534d
Config file : /usr/local/elog/elogd.cfg
Resource dir : /usr/local/elog/
Logbook dir : /usr/local/elog/logbooks/
Falling back to default group "elog"
Falling back to default user "elog"
CKeditor detected
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "convert -version" > /tmp/elog_okY7qv 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/bin/convert -version" > /tmp/elog_xBge3f 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/local/bin/convert -version" > /tmp/elog_GfKWF0 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/opt/local/bin/convert -version" > /tmp/elog_uZtajL 2>&1
ImageMagick NOT detected. Image scaling will not work.
Indexing logbook "logbook1" in "/usr/local/elog/logbooks/logbook1/" ... ok
Indexing logbook "logbook2" in "/usr/local/elog/logbooks/logbook2/" ... ok
Server listening on port 8080 ...
When i try to connect, ELOG login window shows "Invalid user name or password!" .
The logfile (level 9) shows :
24-Jan-2020 16:36:28 [IP] POST /logbook1/ HTTP/1.1
24-Jan-2020 16:36:28 [IP] {MCO} LOGIN user "toto" (attempt)
24-Jan-2020 16:36:28 [IP] {MCO} [PAM] Starting authentication for user toto
24-Jan-2020 16:36:29 [IP] {MCO} [PAM] Authentication not successful for user toto
The problem appears for all Linux users as well.
Does i miss something ?
Thanks for help.
Laurent
David Wallis wrote: |
Hi Christoph,
Thanks for looking into this, if you can enable PAM + File, our users would be very happy!
The pam.d issue is probably related to CentOS/Red Hat, since our PAM expert warned me that it might be necessary.
Jan Christoph Terasa wrote: |
David Wallis wrote: |
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!
|
David, thank you for reporting on your findings regarding the PAM feature. I will look into the points you mentioned:
0. On my machines (Debian testing and stable) I did not have to add anything to /etc/pam.d, but apparently Debian just uses implicit defaults then, and REHL might insist on using excplicit settings. Adding a hint in the documentation is certainly useful, thank your for the suggestion. Maybe elog should provide a pam.d config file (which can be installed/adapted by package maintainers for various OSes).
1.+2. If I remember correctly, I intentionally disabled registration when using the PAM backend, because users will register using their passwd/LDAP/NIS users, and new users can only be regustered using the appropriate tools for the authentication mechanism used. This might not be correctly reflected in the docs, I will check that. In the light of question 2., I can also re-investigate that policy, so that logins will check against both the elog user database and PAM. Self-registering can then be enabled again, and new registrees will go to the elog database. I will try to bringthe code in line with how LDAP works.
regards,
Christoph
|
|
|
69093
|
Fri Jan 24 18:22:52 2020 |
| Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | V3.1.4-283534d | Re: PAM authentication question | Hi,
Before le pam module link, yes.
After adding it, I wait some seconds before new login window popups with password error message.
Jan Christoph Terasa wrote: |
Hi Laurent,
does the ELOG server show the window immediately before even showing the login mask?
Christoph
Laurent Jean-Rigaud wrote: |
Hi,
First, thanks to ELOG tool !
I'm trying to swicth a ELOG 3.1.2 server with local passwd DB to GIT version builded with SSL/PAM/LDAP options. I reuse the buildrpm script which generates correctly RPM files.
After installing on EL6 x86_64 server, i update the elogd.conf file according to GIT version doc :
- Authentication = PAM
- Password file = /usr/local/elog/elog_users.pam (new file as i want to keep the old local DB)
- Self register = 3
I add a link for pam module :
$ ll /etc/pam.d/elogd
lrwxrwxrwx 1 root root 11 Jan 24 16:23 /etc/pam.d/elogd -> system-auth
elogd starts well
elogd 3.1.4 built Jan 24 2020, 07:34:02 revision 283534d
Config file : /usr/local/elog/elogd.cfg
Resource dir : /usr/local/elog/
Logbook dir : /usr/local/elog/logbooks/
Falling back to default group "elog"
Falling back to default user "elog"
CKeditor detected
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "convert -version" > /tmp/elog_okY7qv 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/bin/convert -version" > /tmp/elog_xBge3f 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/local/bin/convert -version" > /tmp/elog_GfKWF0 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/opt/local/bin/convert -version" > /tmp/elog_uZtajL 2>&1
ImageMagick NOT detected. Image scaling will not work.
Indexing logbook "logbook1" in "/usr/local/elog/logbooks/logbook1/" ... ok
Indexing logbook "logbook2" in "/usr/local/elog/logbooks/logbook2/" ... ok
Server listening on port 8080 ...
When i try to connect, ELOG login window shows "Invalid user name or password!" .
The logfile (level 9) shows :
24-Jan-2020 16:36:28 [IP] POST /logbook1/ HTTP/1.1
24-Jan-2020 16:36:28 [IP] {MCO} LOGIN user "toto" (attempt)
24-Jan-2020 16:36:28 [IP] {MCO} [PAM] Starting authentication for user toto
24-Jan-2020 16:36:29 [IP] {MCO} [PAM] Authentication not successful for user toto
The problem appears for all Linux users as well.
Does i miss something ?
Thanks for help.
Laurent
David Wallis wrote: |
Hi Christoph,
Thanks for looking into this, if you can enable PAM + File, our users would be very happy!
The pam.d issue is probably related to CentOS/Red Hat, since our PAM expert warned me that it might be necessary.
Jan Christoph Terasa wrote: |
David Wallis wrote: |
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!
|
David, thank you for reporting on your findings regarding the PAM feature. I will look into the points you mentioned:
0. On my machines (Debian testing and stable) I did not have to add anything to /etc/pam.d, but apparently Debian just uses implicit defaults then, and REHL might insist on using excplicit settings. Adding a hint in the documentation is certainly useful, thank your for the suggestion. Maybe elog should provide a pam.d config file (which can be installed/adapted by package maintainers for various OSes).
1.+2. If I remember correctly, I intentionally disabled registration when using the PAM backend, because users will register using their passwd/LDAP/NIS users, and new users can only be regustered using the appropriate tools for the authentication mechanism used. This might not be correctly reflected in the docs, I will check that. In the light of question 2., I can also re-investigate that policy, so that logins will check against both the elog user database and PAM. Self-registering can then be enabled again, and new registrees will go to the elog database. I will try to bringthe code in line with how LDAP works.
regards,
Christoph
|
|
|
|
|
|