Re: local usage on windows + Linux virtual machine , posted by Sara Vanini on Mon Jan 27 08:46:39 2020
|
Thanks John. I found the linux IP address with ifconfig, type it on my windows machine with the port number, but it doesn't work, the error is "website not found"... what else could I try?
Regards
Sara
| John wrote: |
|
Elog does not access the outside world by default. With the VM I suppose just access it via the Linux local ip address (and port).
| Sara Vanini wrote: |
|
Hello again,
I love to use elog, but I don't need any other accessing it for the moment. So, it is possible to run elog locally on my PC, and make it not accessible from outside?
Moreover, I installed elog on a linux virtual machine running with Virtual Box on Windows 10. Is it possible to open/edit my elog both from the linux VM and from the Windows system? without any accessibility from outside my PC?
Many many thanks
Sara
|
|
|
|
Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 31 15:39:17 2020
|
FYI i added ACL on /etc/shadow file to allow elog user for reading. Testing from elog login shell is OK.
Any suggestion ?
| Laurent Jean-Rigaud wrote: |
|
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
|
|
|
|
|
|
Running ELOG as daemon in Windows not working, posted by Duarte Alexandre Vicente Pais on Fri Jan 31 18:22:50 2020
|
Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other machine. I tried to search in this forum, but with no avail.
Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG?
Cheers,
Duarte |
|
Re: Running ELOG as daemon in Windows not working, posted by Stefan Ritt on Fri Jan 31 18:50:09 2020
|
Probably a problem with your Windows Firewall. You have to convice your OS to let you in.
Stefan
| Duarte Alexandre Vicente Pais wrote: |
|
Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other machine. I tried to search in this forum, but with no avail.
Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG?
Cheers,
Duarte
|
|
|
Re: Running ELOG as daemon in Windows not working, posted by Duarte Alexandre Vicente Pais on Fri Jan 31 19:26:51 2020
|
Do you know which settings in the firewall panel I should change (windows 10 machine)? I went over all the access rules and could not find anything corresponding to the ELOG.
Duarte
| Stefan Ritt wrote: |
|
Probably a problem with your Windows Firewall. You have to convice your OS to let you in.
Stefan
| Duarte Alexandre Vicente Pais wrote: |
|
Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other machine. I tried to search in this forum, but with no avail.
Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG?
Cheers,
Duarte
|
|
|
|
Re: Running ELOG as daemon in Windows not working, posted by Stefan Ritt on Fri Jan 31 19:34:26 2020
|
I'm not a Windows user so I don't know details. But I believe you have to make an exception in the firwall for the elogd.exe executable. You can certainly Google how to do that for any executable.
Stefan
| Duarte Alexandre Vicente Pais wrote: |
|
Do you know which settings in the firewall panel I should change (windows 10 machine)? I went over all the access rules and could not find anything corresponding to the ELOG.
Duarte
| Stefan Ritt wrote: |
|
Probably a problem with your Windows Firewall. You have to convice your OS to let you in.
Stefan
| Duarte Alexandre Vicente Pais wrote: |
|
Hi, I tried to set up an ELOG from a windows machine. Its functionalities work without any problem, but I cannot access at all this ELOG from any other machine. I tried to search in this forum, but with no avail.
Could someone perhaps tell me know how to fix this problem? Or did I miss something obvious in the configuration of the ELOG?
Cheers,
Duarte
|
|
|
|
|
ELOG reverts to demo configuration, posted by VUIIS SysAdmin on Thu Feb 20 16:54:32 2020
|
I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. Has something changed? Is there a new location for the logbooks and other files? Is there a change from the 32-bit to the 64-bit version that will cause this. I am running CentOS 7 fully patched and updated. Will there be a CentOS 8 compatible version? |
|
Re: ELOG reverts to demo configuration, posted by Andreas Luedeke on Fri Feb 21 19:11:12 2020
|
If you've upgraded from an elog 2.x version to an 3.x version, then all entries of a logbook will be moved into subfolder, one for each year.
If you then switch back to the 2.x version of elog, it'll not find any entries.
You can move them back to the folder for the logbook (one directory up) and they'll be found again after the next restart of elog.
Cheers, Andreas
| VUIIS SysAdmin wrote: |
|
I have been using elog for over 10 years. Suddenly my elog installation has changed (probably from a recent update. My /etc/elogd.cfg has changed to the original demo configuration. Even after changing it to my configuration from backup none of the entries for the logbooks apper even though the tabs for the logboos are ther all logbooks are empty. I have looced at the logbook files and the entries seem to be there but are not showing on the web interface. Has something changed? Is there a new location for the logbooks and other files? Is there a change from the 32-bit to the 64-bit version that will cause this. I am running CentOS 7 fully patched and updated. Will there be a CentOS 8 compatible version?
|
|
|